Having frame rate issues? Try this! (NVIDIA users w/SLI) | Forums

[T4KShadow]

I've been playing Gold edition since the first day of the beta and have had to put up with constant frame rate drops. Although it was never severe enough to prevent me from playing, it was certainly deterring.

Anyway thanks to andressergio for raising this.

First thing you need to do is download NVIDIA inspector, if you do not already have it. You can Download it here. You'll need an extractor to unzip the files such as WinRAR.

Run the .exe after it has been extracted and you'll see the following:



In this window click the small settings button on the left-hand side next to "driver version". This will then bring up another window, as shown below:



Now just copy the Bold settings in the screenshot above. When you've done that just launch Trials Evo again and see if it worked! (You might find the intro dissapeared, but just wait it out).

[iStriide]

Still plays the same for me.

[WakeXT]

I'm not entirely sure what those settings should achieve?


First of all you're setting it for the global profile, which means EVERY profile which doesn't specify otherwise will use those values - not a good idea for the SLI- and LOD-settings imho.

Setting AF to "User defined/Off" and "16x" in the general profile is ok, I do that too since I generally always use this driver forced AF instead of the in-game AF-setting (which stays off) - had some games where ingame AF was considerably worse or a few cases where it only went up to 8x.
Same with optimizations off (which means more image quality actually) and Texture filtering quality to "High", which is good for all games anyway.
Most other settings however should be changed in the game's profile, so I'd recommend creating one for "X:\uplay\tege\datapack\trialsfmx.exe".


Moving on:
Why set the LOD Bias to "-1.5" if you don't(or rather can't) use 8xSGSSAA (for which it is normally set at that value) for example in Trials since forcing that mode via Inspector doesn't work in DX10/11 modes because compatibility bits aren't working in those APIs.
There is also no ingame-MSAA in Trials (afaik only FXAA or something similar is available) to enhance via Inspector to SGSSAA (which works in DX10/11 if you got Fermi or Kepler).
Working MSAA either forced or enhanced is a prerequisite for SGSSAA.
Additionally if you DO set SGSSAA, since 310.33 the driver automatically adjusts LOD.

Which brings me to the next setting, Negative LOD Bias "Allow" - which only should be active if you want to manually tinker with the Bias instead of using auto adjust, which in some games' profile can make a difference because of the asymmetric sample pattern(it was recommended to use less like -0.875 instead of the mathematically correct -1.000 for 4xSGSSAA as an example, before auto adjust was introduced) or just personal taste.
Should leave it at "Clamp" and "0.000", all those 2 settings do is mess with texture (AF) detail in all games (and in case you do use SGSSAA auto adjust does its job mostly fine).


Also why would different SLI-settings help with the 540M which is a Single-GPU I assume?
Besides that, SFR performance scaling isn't that great (less micro-stutters tho), but I guess it's better than nothing until Nvidia releases a proper AFR profile for SLI-Users.


Any elaboration is appreciated.

[rlmergeuser]

Lol, I just knew this would happen. I posted this Inspector profile over at Guru3D a couple days ago, as a way to fix issues with people who use SLI, and now it has made its way over here with no attribution to me, and with incorrect information... This won't really fix anything for you if you're not running SLI.

I also posted about this fix in the SLI issue thread that already existed here. Just without the picture that time.

@Wake: I had set a negative LOD bias in my profile because I was playing around with compatibility bits to see if I could get MSAA/SGSSAA to work, but couldn't. And I just left the AF settings on, since I have more than enough power to render far off distance textures in their highest resolution. Screw LOD, haha.

[WakeXT]

As I mentioned, I too prefer forcing AF in the driver instead of ingame, along with disabling the optimizations(which are just trading quality for performance) and setting texture filtering-quality to high.
Nowadays those settings aren't expensive in terms of performance loss anyway.

[rlmergeuser]

As I mentioned, I too prefer forcing AF in the driver instead of ingame, along with disabling the optimizations(which are just trading quality for performance) and setting texture filtering-quality to high.
Nowadays those settings aren't expensive in terms of performance loss anyway.

Yeah, when set to High Quality, those optimizations are disabled anyways btw! So you don't really need to bother disabling them if they are enabled.

[rlmergeuser]

I'm not entirely sure what those settings should achieve?


First of all you're setting it for the global profile, which means EVERY profile which doesn't specify otherwise will use those values - not a good idea for the SLI- and LOD-settings imho.

Setting AF to "User defined/Off" and "16x" in the general profile is ok, I do that too since I generally always use this driver forced AF instead of the in-game AF-setting (which stays off) - had some games where ingame AF was considerably worse or a few cases where it only went up to 8x.
Same with optimizations off (which means more image quality actually) and Texture filtering quality to "High", which is good for all games anyway.
Most other settings however should be changed in the game's profile, so I'd recommend creating one for "X:\uplay\tege\datapack\trialsfmx.exe".


Moving on:
Why set the LOD Bias to "-1.5" if you don't(or rather can't) use 8xSGSSAA (for which it is normally set at that value) for example in Trials since forcing that mode via Inspector doesn't work in DX10/11 modes because compatibility bits aren't working in those APIs.
There is also no ingame-MSAA in Trials (afaik only FXAA or something similar is available) to enhance via Inspector to SGSSAA (which works in DX10/11 if you got Fermi or Kepler).
Working MSAA either forced or enhanced is a prerequisite for SGSSAA.
Additionally if you DO set SGSSAA, since 310.33 the driver automatically adjusts LOD.

Which brings me to the next setting, Negative LOD Bias "Allow" - which only should be active if you want to manually tinker with the Bias instead of using auto adjust, which in some games' profile can make a difference because of the asymmetric sample pattern(it was recommended to use less like -0.875 instead of the mathematically correct -1.000 for 4xSGSSAA as an example, before auto adjust was introduced) or just personal taste.
Should leave it at "Clamp" and "0.000", all those 2 settings do is mess with texture (AF) detail in all games (and in case you do use SGSSAA auto adjust does its job mostly fine).


Also why would different SLI-settings help with the 540M which is a Single-GPU I assume?
Besides that, SFR performance scaling isn't that great (less micro-stutters tho), but I guess it's better than nothing until Nvidia releases a proper AFR profile for SLI-Users.


Any elaboration is appreciated.

Wow, I have no knowledge about this, and it seems you definitely do. Is it possible for you to maybe take a second to see what I should do to get the best Trialsexperience?



Have a i7 2600 3.4 quadcore

[rlmergeuser]

thanks but didn't help anything

[rlmergeuser]

thanks but didn't help anything

Again, not for single GPU users. Read the thread bro.

[rlmergeuser]

thanks but didn't help anything

Again, not for single GPU users. Read the thread bro.

Having frame rate issues? Try this! (NVIDIA users)
doesn't say anywhere this is for SLI users only./. farout there are some really stupid people in this world