A potential fix for the Aircraft visibility problems?

[GF_Mastiff]

Originally Posted by SlipBall

So David you were unable to track the dot in my file?...not sure what system you have but these are my settings, not sure if a factor.

So why are you pointing the Nvidia panel for user porfile to Steam . exe?

It should be pointed to the IL2, Launcher.exe..... That controls your game not steam, Steam is a user interface for gaming social program not for games exe.

[SlipBall]

Originally Posted by GF_Mastiff

So why are you pointing the Nvidia panel for user porfile to Steam . exe?

It should be pointed to the IL2, Launcher.exe..... That controls your game not steam, Steam is a user interface for gaming social program not for games exe.

Originally Posted by SlipBall

Yea but those are my Global settings as well, launcher is in there too I just didn't bother to use the drop down...thanks

[SQB]

Currently having a lot of success with these modifications to the conf.ini file in the steam folders (NOT USER/MY DOCUMENTS!!):

ShowMeshLOD=8 (was 0, 1 gives poor fps)
VisibilityDistance=0 (turned down from original)

Contrast is set to 1.4 and gamma to 0.6 through a custom colour/shade modifier (though CCC or Nvidia control panel will do the same job) .

(I have a bright, 8bit monitor).

The game looks quite nice on these settings, keep in mind contrast and gamma are exponential differences in my program.

[Stublerone]

Just haven't read all posts, but what about resolution? Native resolution? A non native resolution could also draw wrong. It could be that aa draws it out of sight and it could be, that your monitors hardware is scaling like a nap!

My first aim in games is to always run it in native resolution to avoid bad scaling. Just my quick post to that topic

[David198502]

Originally Posted by SQB

Currently having a lot of success with these modifications to the conf.ini file in the steam folders (NOT USER/MY DOCUMENTS!!):

ShowMeshLOD=8 (was 0, 1 gives poor fps)
VisibilityDistance=0 (turned down from original)

Contrast is set to 1.4 and gamma to 0.6 through a custom colour/shade modifier (though CCC or Nvidia control panel will do the same job) .

(I have a bright, 8bit monitor).

The game looks quite nice on these settings, keep in mind contrast and gamma are exponential differences in my program.

mh thats interesting and definitely worth a try, as i get really poor fps with meshshowlod=1!
i remember i also tried to put other values than 1 into meshshowlod line....but i think i gave up before i entered 8....

why do you adjusted your conf.ini in your steam folder and not in the 1c one?

EDIT: ok i just tried it....if i put meshshowlod=8 into th steam conf.ini,...there is no change in visibility, and planes still disappear
if i adjust the 1c conf.ini,.....then the planes dont disappear anymore, and fps seem to be as good as with meshshowlod=0,....but then i have no cockpit visible anymore, and can see partly through the remaining textures of my plane...

but the game doesnt accept meshshowlod=8, cause when i quit the game, and opened the conf.ini, it was reset to meshshowlod=6

[notafinger!]

I am skeptical that any of these conf.ini changes make a difference unless somebody can post proof. Make a mission in the FMB with planes at different distances and see what is visible with the conf.ini changes. I did this before when people were claiming VisibilityDistance=4 or 5 made a difference and I can tell you from testing the game does not recognize a value above 3.

Making changes to the conf.ini in the Steam folder doesn't make sense as that is a template for creating new conf.ini's in the 1C SoftClub folder. That is certainly not the conf.ini the program is using at start up.

These sound like placebos and the reason you think you are spotting contacts better is because there are twice as many people playing now as ever before.

[David198502]

yeah notafinger,....im also pretty confident, that adjusting the conf.ini in the steam directory doesnt have any effect at all, as its only the backup...adjusting the conf.ini in the 1c softclub folder and the MeshShowLod line does indeed have an effect though...

for me:
Meshshowlod=0 fluid performance, but contacts totally disappear in midrange
=1 half the framerate,stutters, but contacts stay visible
everything above 1 leads to disappearing parts of your own plane....the higher the value, the more parts of your plane disappear...

the highest value accepted by the game seems to be meshshowlod=6
as it will reset itself automatically as soon as you enter anything above 6

the annoying thing though is, that with all those values above 1 the other planes stay visible and dont disappear, while the performance is still fluid...but unfortunately its not of use, as you own plane isnt visible....

[IvanK]

Well I changed meshSowlod=8 in the Steam side of the house, went in and flew then checked after exit and it was still set =8. I have Steam cloud turned off though. So it wont always reset itself.

[notafinger!]

I can confirm what David said. Any changes to conf.ini in Steam folder has no effect. Meshshowlod=8 in 1C SoftClub conf.ini will revert to Meshshowlod=6 and results in no cockpit and 3d externals that look like they are from an early 90's DOS game.

Originally Posted by IvanK

Well I changed meshSowlod=8 in the Steam side of the house, went in and flew then checked after exit and it was still set =8. I have Steam cloud turned off though. So it wont always reset itself.

You can put whatever you want in the conf.ini stored in Steam\steamapps\common\il-2 sturmovik cliffs of dover. The game does not use that file. As a test you can delete it completely and the game will still launch and run just fine. The only conf.ini file that matters is stored in ~\Documents\1C SoftClub\il-2 sturmovik cliffs of dover. Change Meshshowlod= in that file and you will see what it actually does to your game.

[David198502]

and the disappearing problem is a specific spitfire problem they introduced with a patch...
at least for me, all the other planes stay visible...but the spit disappears completely..

i cant believe that this really annoying bug made it into the last update of clod......gosh im angry