How to Run in SLI Mode without flicker!!! [FIX]

Post » Fri Dec 31, 2010 1:24 pm

What do you lose when you remove post processing? Or does deleting that change nothing graphically?

You don't lose anything, the post processing for SLI uses a special system. By removing the code it just tells crysis to do post processing the way it wants to. If you put it in there you are trying to force the wrong type of post processing.
User avatar
Juan Suarez
 
Posts: 3395
Joined: Sun Nov 25, 2007 4:09 am

Post » Fri Dec 31, 2010 4:43 am

Well it worked. Thank you very much for taking your time to help everyone. 100+ FPS with no flickering.
User avatar
Trevi
 
Posts: 3404
Joined: Fri Apr 06, 2007 8:26 pm

Post » Fri Dec 31, 2010 3:47 pm

Waw, thanks a lot JranZu, it works perfectly on my system !!!
I was swearing this fu**ing SLI will never worked !!!

Perfect quick effccient solution, good job !


So i'm going back to the game !! thanks a lot.


Precision on my system:
AMD 965 + SLI GTX460GLH (gainward) w/drivers 266.77, Win7x64
User avatar
Jhenna lee Lizama
 
Posts: 3344
Joined: Wed Jun 06, 2007 5:39 am

Post » Fri Dec 31, 2010 4:25 am

and it works at 60fps constantly !!!

Precsion:I'm playing on HDTV 1920x1080, vsync enabled.


Well, let's have a hard playing night !!!
User avatar
James Smart
 
Posts: 3362
Joined: Sun Nov 04, 2007 7:49 pm

Post » Fri Dec 31, 2010 3:26 am

What are the equivalent postprocessing settings for Crossfire? It's got to be the same conflict that you identified with SLI (major props btw, for figuring out the problem before Crytek, EA, Nvidia, or AMD...). There's a lot more fine-grained graphics settings in the actual profile xml for Catalyst, but I don't really have the time to go through and try to figure out which option corresponds to the Nvidia one you've found.
User avatar
Ebony Lawson
 
Posts: 3504
Joined: Fri Feb 16, 2007 11:00 am

Post » Fri Dec 31, 2010 3:59 am

Thanks for this, the flickering has gone and I get a full 60fps :)
User avatar
cassy
 
Posts: 3368
Joined: Mon Mar 05, 2007 12:57 am

Post » Fri Dec 31, 2010 5:33 am

the easy way to fix sli is get the latest beta drivers from nvidia that have those crysis 2 beta sli drivers in it ,


then get those latest sli profiles from nvidia, that also have the sli config from the crysis 2 beta and that works also for the retail full game, im having sli working here without any problems,

for ati users i dont know, not a ati fan, so mabey someone else have a fix for that, but for nvidia do what i posted, and you be running sli without any problems.
User avatar
Sophie Morrell
 
Posts: 3364
Joined: Sat Aug 12, 2006 11:13 am

Post » Fri Dec 31, 2010 3:56 pm

How do you "comment out" something?
User avatar
chinadoll
 
Posts: 3401
Joined: Tue Aug 22, 2006 5:09 am

Post » Fri Dec 31, 2010 1:17 am

What are the equivalent postprocessing settings for Crossfire? It's got to be the same conflict that you identified with SLI (major props btw, for figuring out the problem before Crytek, EA, Nvidia, or AMD...). There's a lot more fine-grained graphics settings in the actual profile xml for Catalyst, but I don't really have the time to go through and try to figure out which option corresponds to the Nvidia one you've found.
My fix is not card specific, so it should (in theory) work for Crossfire as well. However it could be a combination of the config tweek & the Nivida SLI update that is making it work. I don't want to break my system again to find out, I already did that once.

Anyway, I don't know a lot about AMDs graphics settings but I would try setting things up like I outlined and then go through and try going through any Crossfire settings/options that you may have.

Good luck, if you find a fix for crossfire please post on here & send me a message so I can update the main post (and give you credit of course).


--------------------------------------------------------

How do you "comment out" something?
Just add a ; in front of the line... that's: ;

edit: fixed typo

User avatar
Philip Lyon
 
Posts: 3297
Joined: Tue Aug 14, 2007 6:08 am

Post » Fri Dec 31, 2010 2:45 am


Anyway, I don't know a lot about AMDs graphics settings but I would try setting things up like I outlined and then go through and try going through any Crossfire settings/options that you may have.

Good luck, if you find a fix for crossfire please post on here & send me a message so I can update the main post (and give you credit of course).

Definitely will do. I'm not sure I'll have any time to play with it tonight, or any time before tomorrow night... And hopefully there will be some official fix by then (crossing my fingers, but not holding my breath...). But definitely I would like to play the game I paid for with the hardware I upgraded for it, so if no one else has fixed it in the meantime, I'll do my best to figure it out when I'm able to spend more than 10 minutes at my gaming computer.


I was going to start troubleshooting it last night, but the first thing I tried - installing AMD's 11.4 preview drivers - caused me to waste all my time undoing it. Supposedly some people have had success with it, but I couldn't even get it to recognize both video cards, and the one time it seemed to, it wouldn't let me even see the game rendering options. Soooo the one piece of advice I can add at this point is to stay away from the 11.4 preview, at least for multi-gpu users.
User avatar
michael flanigan
 
Posts: 3449
Joined: Thu Jun 14, 2007 2:33 pm

Post » Fri Dec 31, 2010 3:08 am

This worked for me. Thanks

-fuzz
User avatar
Emma Copeland
 
Posts: 3383
Joined: Sat Jul 01, 2006 12:37 am

Post » Fri Dec 31, 2010 10:15 am

Worked on Crossfire also, 2xHD5770. I cannot thank you enough for this fix, you just saved me!

Crytek really need to get there act together the fact it takes the community to fix there bugs is a shame.

+1 for hiring this man
User avatar
Dan Endacott
 
Posts: 3419
Joined: Fri Jul 06, 2007 9:12 am

Post » Fri Dec 31, 2010 6:56 am

Quick update. This works fine in Single Player!

However in Multiplayer its a no go, the flickering and all kinds of crazy **** is happening... any clue?

Edit: I suppose this is because in Multiplayer it is not letting you use some of the commands from the autoexec/system
User avatar
Daniel Lozano
 
Posts: 3452
Joined: Fri Aug 24, 2007 7:42 am

Post » Fri Dec 31, 2010 12:59 am

Worked on Crossfire also, 2xHD5770. I cannot thank you enough for this fix, you just saved me!

Crytek really need to get there act together the fact it takes the community to fix there bugs is a shame.

+1 for hiring this man
What drivers are you on?
User avatar
Sebrina Johnstone
 
Posts: 3456
Joined: Sat Jun 24, 2006 12:58 pm

Post » Fri Dec 31, 2010 8:32 am

Worked on Crossfire also, 2xHD5770. I cannot thank you enough for this fix, you just saved me!

Crytek really need to get there act together the fact it takes the community to fix there bugs is a shame.

+1 for hiring this man
What drivers are you on?

11.4 Preview, remember this only worked in Single Player for me. Not Multiplayer and I copied everything exact from the OP post
User avatar
Donald Richards
 
Posts: 3378
Joined: Sat Jun 30, 2007 3:59 am

Post » Fri Dec 31, 2010 4:04 am

However in Multiplayer its a no go, the flickering and all kinds of crazy **** is happening... any clue?

Just jumped into my first MP game (it's been a busy weekend), and no flicker for me.

You are probably right about MP not loading the autoexec.cfg... But I think it still loads the system.cfg

Make sure you put the r_MultiGPU=1 in the system.cfg file as well, let me know if that works.
User avatar
Lakyn Ellery
 
Posts: 3447
Joined: Sat Jan 27, 2007 1:02 pm

Post » Fri Dec 31, 2010 3:44 am

It looks like there is a glitch in the processing of SLI where you graphics cards are trying to run SLI mode & Crysis 2 is trying to run SLI mode and for some reason they are conflicting...

By default Crysis 2 has this line (r_MultiGPU = 2) in the settings when you have 2 graphics cards for SLI mode.

Now when I saw r_MultiGPU the first time I assumed it was an off/on command or 0/1 -- I think this is actually how it is suppose to be but someone over at Crysis messed up & this gets set to the number of cards you have (2-way, 3-way, Quad).

if you set:

r_MultiGPU = 1

then SLI mode works fine, if you have GPU monitors you will see that both GPUs are being used, there are also some other tweeks I am using to minimize the stress on my graphics cards.

You need to place the r_MultiGPU = 1 in both the system.cfg files & the autoexec.cfg file for it to work 100% of the time, if you leave it out of the system.cfg the multiplayer doesn't work; if you leave it out of autoexec.cfg then it only works about 1/2 the time. I don't know why this is, but it's what I have found.

Here is my autoexec.cfg file:

Code:
sys_spec_shading=4
sys_spec_gameeffects=4
sys_spec_objectdetail=4
sys_spec_particles=4
sys_spec_physics=4
sys_spec_shadows=4
sys_spec_sound=4
sys_spec_texture=4
sys_spec_water=4

; This has to be commented out for SLI mode!!!
;sys_spec_postprocessing=2

r_UseEdgeAA=3
r_TexMaxAnisotropy=16
r_PostMSAA=0
r_ColorGrading=1
r_SSAO=1
r_HDRBloomMul=0
r_HDRBrightLevel=1
r_FSAA=1

r_motionblur=2
g_radialBlur=1

e_shadows=1

g_skipIntro=1
g_enableInitialLoginScreen=0

cl_fov=90
pl_movement.power_sprint_targetFov=85

i_mouse_accel=0
i_mouse_accel_max=100
i_mouse_smooth=1

cl_zoomToggle=1
cl_crouchtoggle=1

r_VSync=1

r_MultiGPU=1
sys_MaxFPS = 60

and my system.cfg

Code:
; crysis2

sys_game_folder=GameCrysis2
sys_dll_game=CryGameCrysis2.dll
sys_user_folder=Crysis2

r_ShaderCompilerServer=192.168.14.180;192.168.14.181

log_IncludeTime = 1
sys_languages = "english,french,spanish,german,turkish,russian,polish,italian,czech,japanese,chineseT"

log_verbosity = 0

sys_PakLogInvalidFileAccess=0
sys_float_exceptions=0

g_language = English

; Needed to fix SLI flicker bug
r_MultiGPU = 1

; With out this set to 60 both my cards run at 98%
; With this set to 60 my cards run at about 60% power
sys_MaxFPS = 60


Hopefully this helps everyone out, and maybe the Crysis programmers too.

edit (3/27/10): updated cfg files & placed notes about needing to be in both the system.cfg & autoexec.cfg.


I did all of this, down to the letter. It does not work with ati 5970. Flickering still an issue.
User avatar
Minako
 
Posts: 3379
Joined: Sun Mar 18, 2007 9:50 pm

Post » Fri Dec 31, 2010 3:21 pm

I did all of this, down to the letter. It does not work with ati 5970. Flickering still an issue.

Yeah, it only seems to work with some people with the AMD cards. I don't use AMD or Crossfire, so I can't trouble shoot it. I would guess that you are using a different driver version, or crossfire profile, than the people who have gotten it to work for Crossfire.

Hopefully they will have a fix out for Crossfire soon.


edit: It looks like those who have gotten it to work with Crossfire are using the 11.4 Preview drivers & it only works in Single Player (or maybe not, see below)

User avatar
James Baldwin
 
Posts: 3366
Joined: Tue Jun 05, 2007 11:11 am

Post » Fri Dec 31, 2010 5:04 am

Actually I take it back :(

There is still flickering issues in my game. Where I was upto in the game I couldn't notice it as much, what I did with yours seemed to remove the "Scan" lines. But as soon as I got to a day time level, the problem came back.

Only way to fix it for XFX is to run the game with bioshock profile from RadeonPRO however you do lose performance. The only other option is to use the 1.0 .exe

However this means no multiplayer :)
User avatar
kelly thomson
 
Posts: 3380
Joined: Thu Jun 22, 2006 12:18 pm

Post » Fri Dec 31, 2010 2:01 pm

That svcks Osmodo... Hopefully they will have a fix out for everyone soon.
User avatar
Nikki Hype
 
Posts: 3429
Joined: Mon Jan 01, 2007 12:38 pm

Post » Fri Dec 31, 2010 8:21 am

Best profile I have seen when using RadeonPro is FEAR profile on XFX. Kinda shame though because FPS isnt all its cracked upto be...

:(
User avatar
Lucky Girl
 
Posts: 3486
Joined: Wed Jun 06, 2007 4:14 pm

Post » Fri Dec 31, 2010 12:33 pm

I did all of this, down to the letter. It does not work with ati 5970. Flickering still an issue.

Yeah, it only seems to work with some people with the AMD cards. I don't use AMD or Crossfire, so I can't trouble shoot it. I would guess that you are using a different driver version, or crossfire profile, than the people who have gotten it to work for Crossfire.

Hopefully they will have a fix out for Crossfire soon.


edit: It looks like those who have gotten it to work with Crossfire are using the 11.4 Preview drivers & it only works in Single Player (or maybe not, see below)

I'm using 11.4, those fixes do not work with 5800/5900 series cards in crossfire.

The only fix I needed to apply was changing the crysis.exe to Bioshock. Fixed all the problems, even with post processing on extreme, with bloom, no issues at all with crossfire with a 5970.
User avatar
Emily Shackleton
 
Posts: 3535
Joined: Sun Feb 11, 2007 12:36 am

Post » Fri Dec 31, 2010 9:25 am

The only fix I needed to apply was changing the crysis.exe to Bioshock. Fixed all the problems, even with post processing on extreme, with bloom, no issues at all with crossfire with a 5970.

Did you still need to add the r_MultiGPU=1?

Just wondering so I can update the main thread, thanks!
User avatar
Sabrina Schwarz
 
Posts: 3538
Joined: Fri Jul 14, 2006 10:02 am

Post » Fri Dec 31, 2010 6:47 am

Best profile I have seen when using RadeonPro is FEAR profile on XFX. Kinda shame though because FPS isnt all its cracked upto be...

:(

FEAR or FEAR 2? I renamed the .exe to Bioshock, no flickering but the fps kinda svcks for CFX 6870s
User avatar
His Bella
 
Posts: 3428
Joined: Wed Apr 25, 2007 5:57 am

Post » Fri Dec 31, 2010 4:07 am

Thanks, it worked.
User avatar
Elle H
 
Posts: 3407
Joined: Sun Aug 06, 2006 3:15 am

PreviousNext

Return to Crysis