Advice for VGA & ingame settings [NVidia]
-
for blurryness make sure to disable FSXAA or whatever its called, just use plain AA and AF.
-
Nice read, makes me blur
Iām new with Nvidia, GTX960 and appreciate any help like this threat very much.
Any advice on which driver and the best way to install things?
TIA -
Hyper threading and multi core is used by BMS because BMS is a multi threaded application, if you go to task-manager you will be able to see that BMS utilizing all the cores to SOME level. The fact that BMS isnāt utilizing all cores to FULL load is because of the code wasnāt designed for muti-core and converting it to take full advantage of the processing power of modern CPUs, is a long way.
You do realize that multi-core and hyperthread support are two completely autonomous things? Support for multicore doesnāt mean automatic hyperthread support.
Triple buffering isnāt related to VSync only, but it is true that VSync is a good candidate to take advantage of it because triple buffering can improve FPS by not waiting for the monitor between frames (which Vsync is actually forcing) because the HW can write to the 3rd back buffer while the 1st is the currently presented and the 2nd isnāt available cause of VSync.
Thatās also why Triple buffering is suitable for people that extracting displays to more monitors than 1, it allows the HW to write faster by decreasing wait times when coming to write to back buffers.
Triple buffering is good for such purposes but it does cost more VRAM, so if one has low-memory cards, he maybe better not use it because the swapping of VRAM may be more costly than the double-buffering wait times.
Basicaly, you said the same things as I did here.
for blurryness make sure to disable FSXAA or whatever its called, just use plain AA and AF.
FXAA is unsupported by all games save for the last say 2 years. It basically renders the frames in much higher resolution then downscales them to the preset one.
-
You do realize that multi-core and hyperthread support are two completely autonomous things? Support for multicore doesnāt mean automatic hyperthread support.
Yes I do know the difference, multi-core is physical and HT is logical, and software needs to be aware of HT in order to use it. Since our OS is HT aware, Iām sure there is a way to address HT via APIs and apparently multi-core and HT are addressed as 1 entity specifically regarding the Nvidia driver settingsā¦
Basicaly, you said the same things as I did here.
No, you CONCLUDED that only Vsync users should use triple buffering, but that isnāt true because it can help also with display extraction (where FPS loss can be even more critical because usually there is some loss for the display extraction itself).
-
I set the graphical setting outside the BMS as I try to fight shimmering in my pit as much as possible. On my old rig/relativelly low res theese settings provide best visual results vs fps/fluid rendering. Normal weather + TGP ON around 40fps, in the weather 30fps. With 2x SGS AA important thing is set Texture Filtering Quality to High Performarce, otherwise fps would tank a LOT more in the weather/vertices vissible situations etc. If you find the fps hit too much, set Transparency supersampling to 2x superampling, then my fps are always about 40, bit cockpit is shimmering on some gauges. Hope it can help to somebody.
-
- Just get Nvidia Inspector and forget that the default driver profile UI exists
Would you be so kind to post a screenshot of your inspector/BMS settings?
-
I set the graphical setting outside the BMS as I try to fight shimmering in my pit as much as possible. On my old rig/relativelly low res theese settings provide best visual results vs fps/fluid rendering. Normal weather + TGP ON around 40fps, in the weather 30fps. With 2x SGS AA important thing is set Texture Filtering Quality to High Performarce, otherwise fps would tank a LOT more in the weather/vertices vissible situations etc. If you find the fps hit too much, set Transparency supersampling to 2x superampling, then my fps are always about 40, bit cockpit is shimmering on some gauges. Hope it can help to somebody.
Does mipmapping and linear map filtering have any positive effect to any VGA? I tried to use on wit both NVida and ATI card and for both caused texture issuse as in 1st post but in much more serious scale.
-
-
- Extension limit is OpenGL stuff ONLY!!!
- Threaded optimization is Intel or AMD Hyperthreading related. This shouldnāt be used with OpenGL apps, which Falcon 4 isnāt, Iām mentioning it just for reference sake.
I didnt get the recommendation. Do you advise to switch it on or off?
You say Falcon BMS is not an OpenGL. So do I need to turn threaded optimization on and extension limit to off?
On my machine this setup gives 1 fps higher result (than vise versa):
extension limit On
Threaded optimization off -
I didnt get the recommendation. Do you advise to switch it on or off?
You say Falcon BMS is not an OpenGL. So do I need to turn threaded optimization on and extension limit to off?
On my machine this setup gives 1 fps higher result (than vise versa):
extension limit On
Threaded optimization offThreaded optimization can be (by my discussion with I-Hawk) either Auto or On, Extension limit is on only for OpenGL applications. Falcon 4 is DirectX, so it stays off.
Iāll post my NVidia Inspector settings a bit later, my PCās RAM died last week so I couldnāt do it until now.
-
The BMS/NvidiaInspector setup for my GTX570 (driver version 355.82 on Win10 x64):
1. In BMS:
- Multisampling Off
- Anisotropic Filtering Off
- Mipmapping On
- Linear Mipmapping On
- Texel Bias On
- HDR sliders to the left (personal preference!)
2. In NvidiaInspector:
Note: IIRC, you need to create a new profile for Falcon BMS.
Anti-Aliasing Mode: Override
Anti-Aliasing Seting: 8xQAnisotropic Filtering Mode: User-Defined
Anisotropic Filtering Setting: 16xNegative LOD Bias: Clamp
Texture Filtering: High QualityMulti-Display Acceleration: Single Display Performance Mode (only one monitor here)
Power Management Mode: Prefer Maximum Performance(The rest is default.)
Looks totally okay to me. I think disabling HDR helps with higher anti-aliasing settings as well. No notable slowdowns over the FLOT or in the circuit.
-
I noticed BMS multisampling quality is better then with Nvidiaās standard cp. (More edges)
How does quality compare multisampling BMS vs Nvinspectorās ? -
My own settings. Mind you, my PC isnāt the best in the world, so I donāt have everything set up as such. The only NVidia Inspector settings Iād change would be the AA set to 4xS and the transparency AA Multisampling turned off and set at 2x supersampling (ideally, transparency AA should always be equal or half of the main AA setting - and ignore the sparse grid supersample stuff, with F4ās engine itās pretty much pointless overkill).
-
I set the graphical setting outside the BMS as I try to fight shimmering in my pit as much as possible. On my old rig/relativelly low res theese settings provide best visual results vs fps/fluid rendering. Normal weather + TGP ON around 40fps, in the weather 30fps. With 2x SGS AA important thing is set Texture Filtering Quality to High Performarce, otherwise fps would tank a LOT more in the weather/vertices vissible situations etc. If you find the fps hit too much, set Transparency supersampling to 2x superampling, then my fps are always about 40, bit cockpit is shimmering on some gauges. Hope it can help to somebody.
Further update of the test on my old system - turning off cloud reflection on water adds further 5fps if water is visible. With regards to the forum āautogen trees do not cause fps hitā statement - try it in Training mission 8 - TFR. In the weather with the sensors screens on, trees DO cause a fps hit, so I think that default recommended setting is a good compromise.
-
http://i864.photobucket.com/albums/ab204/molnibalage/BMS4-33/2015-11-01_012039.jpg~original
Generally from this wiev everythings looks fine but if you check runways and texuresā¦http://i864.photobucket.com/albums/ab204/molnibalage/BMS4-33/2015-11-01_012050.jpg~original
http://i864.photobucket.com/albums/ab204/molnibalage/BMS4-33/2015-11-01_012029.jpg~original
What should I set on Nvidia control panel and ingame not see to black lines in texutres and blurry textures?
Molni, you can try experiment with Negative LOD Bias value - set Lod Bias(DX) to Allow and try Negative LOD Bias -2.0. That should force to load higher resolution texture further away and reduce blurry texture on the runway. If you see shimmering on textures during flight (for example on city textures), try to reduce it a little (-1.5 or -1)
-
My own settings. Mind you, my PC isnāt the best in the world, so I donāt have everything set up as such. The only NVidia Inspector settings Iād change would be the AA set to 4xS and the transparency AA Multisampling turned off and set at 2x supersampling (ideally, transparency AA should always be equal or half of the main AA setting - and ignore the sparse grid supersample stuff, with F4ās engine itās pretty much pointless overkill).
Thanks Adonis! I build my settings based on your initial advises. Having more or less the same qualty picture (with V-sync, so no tearing), but 60 FPS standing on the runway Kunsan with empty TE and clear skies. With TGP on it drops to 45-47 FPS.
My specs is the following: GTX770 2Gb RAM and Intel Core I5-3570 boosted to 4120 MHz with 16Gb DDR3 RAM on 686.6 MHz
Falcon UI settings pretty much the same, but object quality, grass and trees are default. And Inspector+Configurator screenshot is attached.P.S. If I just copy your Inspector settings its 3-5 FPS lower than mine.