noooo why?
Only because the navy paid some professional officer to study an argument important as contact seeing and camouflaging and he produced a classified file on that?

Surely he studied more that argument with a plethora of complex instruments and interviews:roll:

I just started flying IL2-COD (been on IL2-46) online at 1440 resolution. Being
I fly a lot of 46, the spotting of a/c in COD was immediately noticeable. First
I measured the range to target with the gunsight to make sure the a/c were
properly scaled, and they were fine. Next I started to look for threads such as
this one and the other called "Target Visibility". Both threads are excellent.

Im one of those that refuse to back down my desktop or in game resolution to
get a bigger and sooner first pixel sighting. I can't stand sims on lower res.
So I was wondering, if anyone has done any in depth investigation on the
effects of the anti-aliasing and filtering settings as a function of visibility and
range?

Here we want to get rid of the jaggies and have smoothed and dithered a/c
graphics to make it look real, but are these same features also reducing our
long distance a/c profile visibility? Does it have an effect on the switching
between pixel and LOD switching? Just some thoughts.

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?

:rolleyes:

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.

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

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.

S!

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

Anyone got a link to the face-plant picture?

Tamat.. that was my point! KeBrAnTo was poo pooing the NAVY's study when he said.. 'Well if the NAVY said it must be true than'

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?