Special Aircraft Service
Battlefield - Airborne - Tactical (BAT) => BAT Tech Help => Topic started by: JG51_Ruski on April 24, 2019, 09:50:49 AM
-
,,Is there a guide for nvidia inspector for optimizing my Geforce1050 for IL-2 ?? I saw something a few days ago but can't seem to find it now..did a search but no luck.. Thank you for any help
-
I'm sorry English is not my language but, but maybe it might interest you, even if it's Spanish.
page 1 and 10 of the post.
@edit by Admin: Link removed because the content is completely misleading.
-
There is no such thing like a general optimization for Nvidia Inspector and IL-2 1946 which is valid for everyone in the same way.
99.9% of players are best off if they keep safe distance from "optimization tools" like Nvidia Inspector and just use correct settings for the Nvidia Control Panel.
If you ever happen to use Nvidia Inspector, then you should do so only in order to achieve one very specific goal which is out of reach for the normal Control Panel Settings.
Capping FPS for instance.
But that's really very special edge cases.
And even then it's impossible to say "yeah, this will work for everyone" because you'd first have to clarify which version and development branch of Nvidia Inspector we're talking about at all, and then the possible, valid and useful settings very much depend on the GPU being used.
The "recommendations" in the post CDS025_DOGO linked before (sorry for removing it, but read on...) for instance were completely invalid for a 1000 series GPU and overall 75% of it was just plain bullshit, not optimizing anything, but instead effectively f*cking up your GPU settings.
Start optimizing your Nvidia Control Panel settings and if issues remain, name them so we can see how to sort them out.
These would be valid Nvidia Control Panel settings to start with:
DSR Factors = Off
Anisotropic filtering = 16x
Antialiasing - FXAA = Off
Antialiasing - Setting = 8x
Antialiasing - Gamma correction = On
Antialiasing - Mode = Override any Application Setting
Antialiasing - Transparency = Multisample
Preferred Refresh rate = Highest Available
CUDA - GPUs = All
Triple buffering = Off (This depends, you might want to set it to "on" if you experience tearing or micro-stutters if using a monitor without G-Sync)
Power management mode = Prefer Maximum Performance
Optimize for compute performance = Off
Maximum pre-rendered frames = 3
Monitor-technology = G-SYNC (only if available)
Multi-Frame Sampled AA (MFAA) = Off
OpenGL-rendering GPU = Auto
Shadercache = On
Texture filtering - Anisotropic sample optimization = Off
Texture filtering - Negative LOD bias = Clamp
Texture filtering - Quality = Quality
Texture filtering - Trilinear Optimization = On
Threaded optimization = Auto
Vertical sync = Fast (try other modes if you aren't satisfied...)
Pre-rendered VR-Frames = 1
]cheers[
Mike
-
Thanks Mike, and sorry I thought you could be helping.
I will apply the parameters that you publish.
Greetings. :)
-
Thanks for the advice Mike but to be honest I'm pleased with the level of detail I have and frame rates are acceptable only issue I see is it bogs down considerably when in areas with heavy smoke as in the Black death Track,,But I think the old adage if it isn't broke don't fix it,,I think mucking about with the Nvidia inspector is something I'd best leave alone my air encounters run well so I'll keep things as they are
-
it bogs down considerably when in areas with heavy smoke as in the Black death Track
That's CPU related.
It happens because of the quite ineffective, unoptimized effects code in IL-2 core.
Nothing much you can do about but to buy another CPU with more "bang" on single threads: https://www.cpubenchmark.net/singleThread.html
]cheers[
Mike