Page 1 of 3

[Temp Solution] Nvidia SLI

Posted: 31 Aug 2011, 16:11
by Shadowdane
The EVGA Patch I originally posted just doesn't work very well, so I removed the main post... click here to see my updated fix! :3

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 31 Aug 2011, 16:23
by kalimerre
Nice news thanks for informations!
I moved in Support forum and i stick it.

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 02 Sep 2011, 15:45
by Cznielsen
So....

How do you use it?


I tried installing it but nothing happens.

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 14 Sep 2011, 12:32
by CrazyCoder
This SLI profile indeed enables the second GPU, however it's completely pointless since the load on each GPU is 50% and overall FPS doesn't improve (I even lost 1fps on my config with SLI profile). Disabling this profile fully loads single GPU.

So, we still need a proper SLI support, otherwise I get only 40fps when running all on maximum settings with 2560x1600 resolution.

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 14 Sep 2011, 12:43
by metoxys
CrazyCoder wrote:So, we still need a proper SLI support, otherwise I get only 40fps when running all on maximum settings with 2560x1600 resolution.
40 fps is good, man!

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 14 Sep 2011, 12:47
by CrazyCoder
metoxys wrote:40 fps is good, man!
It's not bad, however with vsync enabled average FPS drops to 30. I'd prefer 60 fps with vsync enabled, which should be possible with SLI.

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 14 Sep 2011, 12:57
by metoxys
CrazyCoder wrote:
metoxys wrote:40 fps is good, man!
It's not bad, however with vsync enabled average FPS drops to 30. I'd prefer 60 fps with vsync enabled, which should be possible with SLI.
Disable vsync, man!

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 14 Sep 2011, 13:09
by CrazyCoder
I have it disabled at the moment and get 40fps, however I'd prefer it enabled to avoid tearing.

Re: EVGA releases Nvidia SLI patch for TM2: Canyon

Posted: 16 Sep 2011, 15:24
by Shadowdane
Yah this SLI Patch doesn't work anymore, it worked on beta and ran great. But now with the final release it runs like crap again. Lots of stuttering and huge dips in framerate.

See my post here.

Re: [Solution] Nvidia SLI

Posted: 17 Sep 2011, 21:33
by Shadowdane
I found a fix!!! I was messing with the SLI profile settings for TM2: Canyon all morning and found settings which make it run great!! Nvidia should use these profile settings officially it runs flawlessly! :D
The profile setting which I've listed below gets rid of all the stuttering & framerate drops which happened with No Profile or the EVGA profile. I included a benchmark showing performance for Single GPU, SLI (No Profile) & SLI (Custom Profile).

You'll first want to load the latest Nvidia Driver, I'm using the 285.27 Beta.
285.27 Beta - WinVista/7 32-Bit
285.27 Beta - WinVista/7 64-Bit
285.27 Beta - WinXP 32-Bit
285.27 Beta - WinXP 64-Bit

This profile changes requires editing the SLI Profile settings with Nvidia Inspector.

If you haven't used Nvidia Inspector before, here is a quick run-down.
1. Open Nvidia Inspector
2. Click the Wrench Icon (See Pic 1) - This opens the Game Profile Editor
3. Create a new profile for Trackmania 2 (See Pic 2) - Click the Yellow Star Button on the Toolbar
4. Add maniaplanet.exe & maniaplanetlauncher.exe to the Profile (See Pic 2) - Click the App+ Button on the Toolbar
5. Now you'll modify the profile to match the settings listed below (See Pic 2)

Nvidia Inspector Profile Settings
SLI Compatiblity Bits: 0x00500045 (You'll need to copy/paste this - It won't be in the drop down list)
# of GPUs to use on SLI Rendering: SLI_GPU_COUNT_FOUR
Nvidia Predefined SLI Mode: SLI_PREDEFINED_MODE_FORCE_AFR2

Nvidia Inspector Pics
Pic 1: http://shadowdane.com/public/trackmania2/ni_1.png
Pic 2: http://shadowdane.com/public/trackmania2/ni_2.png

Benchmark Graph
http://shadowdane.com/public/trackmania ... chmark.png

Sorry about the lengthy solution here... but this will have to do until Nvidia officially fixes this.