Contact sight problem.. really something to patch!!

[Insuber]

Originally Posted by ElAurens

I'm sure that if the study was done by the Royal Navy, or the Kreigsmarine, or the Regia Marina then you wouldn't be rolling your eyes, would you?

Tamat was rolling eyes on the guy (troll) who ridiculized the US Navy research found by Tamat himself, you should read the whole thread.

[ElAurens]

Originally Posted by Insuber

Tamat was rolling eyes on the guy (troll) who ridiculized the US Navy research found by Tamat himself, you should read the whole thread.

If that's the case then I offer apologies. It just did not read that way to me, and the thread has dragged on for 2 months, so it's hard to keep it all in perspective.

Scusa mi Tamat.

[GF_Mastiff]

I found on my set up to place the as setting and such
to 4x and now I see very wellOh and application controlled.

[EZ1]

I just checked my conf.ini and the "MeshShowLod=1" parameter is in the [core] section. Someone mentioned earlier that it is in the [Net] section. I believe [core] is the correct section.

[Flanker35M]

S!

Mastiff, did you mean Anisotropic Filtering to 4x and FSAA to Application controlled?

[AV8R_]

OK great, so there are AA, Filtering and LOD switching workarounds...

So in summary, there are these two:

• Anisotropic Filtering to 4x and FSAA to Application controlled
• conf.ini and the "MeshShowLod=1" parameter is in the [core] section.

I wonder if these both to be used together, or only one at a time, and on older systems if its better to use only the AA and Filtering strategy. Being that the
MeshShowLod method is frame rate costly.

Has anyone make any frame rate and screen shot comparisons for these?

[Flanker35M]

S!

I use only the AF at 4x and AA at Application Controlled, the LOD setting in conf.ini has too big hit on FPS and causes stuttering.

[HR_Naglfar]

Originally Posted by AV8R_

OK great, so there are AA, Filtering and LOD
So in summary, there are these two:

• Anisotropic Filtering to 4x and FSAA to Application controlled
• conf.ini and the "MeshShowLod=1" parameter is in the [core] section.

I wonder if these both to be used together, or only one at a time, and on older systems if its better to use only the AA and Filtering strategy. Being that the
MeshShowLod method is frame rate costly.

They are two different fixes for two different problems.

If you have problems sighting contacts, but the contacts are there and it's just that they are very difficult to see, may be changing your graphic conf can improve that.

But there are a LOD problem that some people have and some doesn't. Approx between 800 and 2000m the contacts are simply invisible. If you have this problem then MeshShowLod=1 fix that. If you are lucky and don't have this problem then there's no need of changing anything in the conf.ini.

I don't know the exact cost in FPS, I play in a very old PC and already have very low FPS (and by low I mean 10-15fps) without MeshShowLod=1. But I use it anyway because without it I don't see anything between 800m and 2000m near me.

[AV8R_]

Thanks for the expansion on the application of these workarounds.
Does the development/beta teams know about this trouble that we don't seem
to suffer as much with on IL-46 as we do in COD? (I assume yes, but had to
ask to be complete). If not where do we put in a bug/enhancement request?

Now at the expense of asking a dumb question...
How do you know that the a/c blanks out between 800 and 2000m, like how do
you know something is missing if you can't see it? Was it flying straight at
you the whole time?

I was thinking about a mechanism that might help us with these kinds of a/c
spotting issues. WHy not make a hybrid between padlock and lock on?
So if you look at a position in space, you can hit a spot&lock key function so
that if there was an a/c (within an acceptable visual range of a pilot with 20/20
vision, say at 3km head on per that Navy chart for a fighter sized object)
that it will lock on and zoom in at the bogey for say 3 seconds. This would
emulate squinting and seeing the plane (no matter the pixel and resolution)
setting for a short time. Thus its not a fully automagic padlock, and its not a
box or icon text either. But just allows a short time to see the object better.

Another way to visualize this would be like how we can put our fingers on the
text on an iPhone or iPad and a small zoom in magnifying glass comes up.
The pilot really has to be looking in the right spot in the first place to evoke the
use of the squint2magnify/spot&lock feature. So its not some magical radar padlock.

THis could be an optional feature for the hardest of core players, or have a time
and range selection variable (within an acceptable range). The size of the
space to be magnified could be limited to a few rads, again selectable and
enabled by the host and INI file or GUI. Even the time between being able
to use it can have a timeout so its not overly abused. Kind of like a setup
and hold spec for a edge sensitive flip flop spec. (but I digress, sorry).

Just some out of the box thinking here.