Far Cry 3 and GTX 690

[Chalky Emultion]

hi,

I'm experiencing lag in Far Cry 3 with a GTX 690, 16 GB DDR3 and a Core i7-3770K...

Anti Alias set to 2x minimize the lag, but if I set it to 8x, the game keep lagging (45-50fps). Also i noticed that it use only 1 GPU of the GTX 690: GPU 1 is loaded 97%, GPU 2 is loaded 5% and have desktop clocks...

Why Far Cry 3 isn't actually using SLI? I have 310.64 beta drivers...

 

[stormy13]

https://forums.geforce.com/default/topic/524582/far-cry-3-sli-not-working-310-64/?offset=27

 

[Chalky Emultion]

Thank you man

So the solutions are 2... or i make a custom profile for Far Cry 3 -DX11 or i play in DX9....

 

[AstaLaVista]

I am going to go ou on a limb and say that this is another great Console port to PC brought to you by the Geniuses of Ubisoft, hence, the why it won't work with the newest cards out there... you gotta love DX9

I am sure that you have downloaded any of the new title updates? By now there should be at leat 1 patch or revision. Knowing UBI, you will be better off not patching from game but downloading it and then installing the patch.

Perhaps it would be better if you don't run on Beta Drivers and roll back to the previous one? How about Audio drivers? have you also updated those?

Going to the UBI forums for FC3 might yield other options... I am sure there will be plenty of responses there as well.

Good Luck.

 

[Chalky Emultion]

drivers are all updated... motherboard, sound and video...

I installed new beta drivers because they should increase performance by 40% in GTX 680 GPUs..

 

[stormy13]

Perhaps it would be better if you don't run on Beta Drivers

Except that the latest Nvidia beta driver is the first one with FC3 support. Unfortunately for SLI users it looks like Nvidia borked the SLI profile for the game.

 

[Chalky Emultion]

I hope Nvidia will fix it as soon as possible... DX11 is really better than DX9...

 

[smarteyeball]

If you follow the instructions here and Use NV Inspector to add the dx11.exe location and to also adjust the AA and enable FXAA. it works.

My 670's are both in use and I can run the game DX11 maxxed with FXAA, X8 CSAA, HBAO + vysnc and maintain a smooth and steady 60FPS for the majority of the time. (it even runs smooth with HDAO which is optimized for AMD only)

There's also an .xml file you can edit to enable DX11 multi-threading.

 

[Chalky Emultion]

If you follow the instructions here and Use NV Inspector to add the dx11.exe location and to also adjust the AA and enable FXAA. it works.

My 670's are both in use and I can run the game DX11 maxxed with FXAA, X8 CSAA, HBAO + vysnc and maintain a smooth and steady 60FPS for the majority of the time. (it even runs smooth with HDAO which is optimized for AMD only)

There's also an .xml file you can edit to enable DX11 multi-threading.

thank you

Also I'm experiencing a bad shadow issue...
Shadows "flash" when I'm moving, making the game unplayable for eyes... Any solution for it?

 

[smarteyeball]

SSAO seems to play a part in that. It's not as bad under HBAO with the other tweaks enabled.

For now, I don't know how to eliminate it completely.

 

[Solarstarshines]

I am going to go ou on a limb and say that this is another great Console port to PC brought to you by the Geniuses of Ubisoft, hence, the why it won't work with the newest cards out there... you gotta love DX9

I am sure that you have downloaded any of the new title updates? By now there should be at leat 1 patch or revision. Knowing UBI, you will be better off not patching from game but downloading it and then installing the patch.

Perhaps it would be better if you don't run on Beta Drivers and roll back to the previous one? How about Audio drivers? have you also updated those?

Going to the UBI forums for FC3 might yield other options... I am sure there will be plenty of responses there as well.

Good Luck.

This has been a Ongoing issue with most of UBI's title I had to use a mod on I am Alive to use a 360 controler but the button configuration makes it unplayable and you can't change it

Im sure the cries have been heard but they need to stop halfassing PC games because they think more money is in consoles

 

[AstaLaVista]

I seriously doubt if UBIsoft has even heard the cries or even if they really care since they have been doing half assed games for PC since about 2002 when they first come out with their glorious Ghost Recon War Fighters, at least this was a pc game and not a port, they used a 1960's engine :. Then, they really showed us how bad they could port a game with Rainbow Six Vegas.

I thought they had murdered the two best FPS franchises but I was wrong... they really did a number with FC2 and now this one... and I am not even counting other games like AC or Conviction because it was a genre I never played but I read about those as well

Anyways, I am glad that there are people that have work arounds for these issues but it bugs me that UBI takes advantage of these same facts to continue producing crapped out games.

 

[Solarstarshines]

Funny you mention this the only games i remember working right off the bat was Rayman 3 Great escape and the Prince of Persia's i was able to play all the way through no issues

 

[swordsx48]

all i have to say is you are one rich person to have the gtx 690

 

[Chalky Emultion]

all i have to say is you are one rich person to have the gtx 690

no, I'm not rich, my father builded me a new system for my birthday since i was using a old pc with a Pentium 4, DDR RAM and AGP since 2005.

Anyway, I solved all my problems and now the game rocks

Thank you all... I'll add some rep this afternoon

 

[smarteyeball]

Anyway, I solved all my problems and now the game rocks

For others, would you mind sharing how you fixed it?

 

[Chalky Emultion]

Anyway, I solved all my problems and now the game rocks

For others, would you mind sharing how you fixed it?

I simply follow the guide you posted to me and now the game is working at full speed with 8x AA and HBAO, using both GTX 690's GPUs.
I reccomend to don't use Vsync because it makes the game lag a lot...

Shadows problem has been solved simply restarting the game. Now it seems to be permanently fixed.