For the textures it really needs to be the dimensions of the back buffer I think... what we pass to the shaders is probably up to us to define, but the back buffer dimensions is probably going to be the most useful (the active render target dimensions is also useful in some situations, but that's something we probably only want to provide on demand since it may change per draw).
On the other hand I'm not entirely familiar with how gaming works on multi monitor setups like surround so I may be wrong... I'm also not sure how it works in windowed mode, but given 3D doesn't work in DX11 windowed mode we can probably ignore that.
For the textures it really needs to be the dimensions of the back buffer I think... what we pass to the shaders is probably up to us to define, but the back buffer dimensions is probably going to be the most useful (the active render target dimensions is also useful in some situations, but that's something we probably only want to provide on demand since it may change per draw).
On the other hand I'm not entirely familiar with how gaming works on multi monitor setups like surround so I may be wrong... I'm also not sure how it works in windowed mode, but given 3D doesn't work in DX11 windowed mode we can probably ignore that.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
[quote="DarkStarSword"][quote="mistersvin"]rebooting didnt help, this level is complely broken in the left eye. Did u play this mission urself ? did anyone else ?[/quote]Yeah, I played all the Shangri-La missions in 3D and never saw anything like this.
Can you send me your save file and let me know which visit to Shangri-La that was on (first, second, etc)?
There was one point the 3D broke for me in one eye (some things moved to back to where they would be in 2D, but only in one eye), but it wasn't anything like those screenshots and restarting the game fixed it.
I suspect this is some kind of issue with the driver, but to be sure can you try an earlier version of the fix - 0.4 was right after I visited Shangri-La for the first time and this issue was definitely not present for me then:
https://s3.amazonaws.com/DarkStarSword/3Dfix-Far+Cry+4-alpha-0.4-2015-03-10.zip
https://s3.amazonaws.com/DarkStarSword/3Dfix-Far+Cry+4-alpha-0.5-2015-03-11.zip
https://s3.amazonaws.com/DarkStarSword/3Dfix-Far+Cry+4-alpha-0.6-2015-03-14.zip
https://s3.amazonaws.com/DarkStarSword/3Dfix-Far+Cry+4-alpha-0.7-2015-03-14.zip
It's probably also trying without the fix installed at all.
A few other things you might try:
- Changing to a different AA setting (off or one of the MSAA/TXAA variants)
- Switching between SLI and single GPU
- Switching the profile from Max Payne 3 to Far Cry 4 with StereoFlagsDX10 = 0x00004000
- Rolling back to an earlier driver (I'm on 344.75)[/quote]
I got into shangri la again - now it's ok, it seems the very first mission is messed up
mistersvin said:rebooting didnt help, this level is complely broken in the left eye. Did u play this mission urself ? did anyone else ?
Yeah, I played all the Shangri-La missions in 3D and never saw anything like this.
Can you send me your save file and let me know which visit to Shangri-La that was on (first, second, etc)?
There was one point the 3D broke for me in one eye (some things moved to back to where they would be in 2D, but only in one eye), but it wasn't anything like those screenshots and restarting the game fixed it.
It's probably also trying without the fix installed at all.
A few other things you might try:
- Changing to a different AA setting (off or one of the MSAA/TXAA variants)
- Switching between SLI and single GPU
- Switching the profile from Max Payne 3 to Far Cry 4 with StereoFlagsDX10 = 0x00004000
- Rolling back to an earlier driver (I'm on 344.75)
I got into shangri la again - now it's ok, it seems the very first mission is messed up
As noted in the comment just above the key bindings in the d3dx.ini, you can look up the keys here:
http://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx
FWIW I've also added aliases for common key names, so even if you don't look up the correct name you can just guess the obvious name and it will probably work as well... Have you tried "capslock"?
FWIW I've also added aliases for common key names, so even if you don't look up the correct name you can just guess the obvious name and it will probably work as well... Have you tried "capslock"?
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
I have a problem with this game forcing 1080i on my projector instead of 1080p.
Does anyone know how I can force far cry to be progressive rather than interlaced.
Thanks.
I have a problem with this game forcing 1080i on my projector instead of 1080p.
Does anyone know how I can force far cry to be progressive rather than interlaced.
Thanks.
Awesome fix, game looks amazing. Only problem is the Nvidia 3d crosshair is displaying at a fixed depth. Known issue, or is there a setting i cant find?
Also, is the constant loading/hitching when traveling a permanent Dunia limitation that we just have to live with or have there been successful workarounds? I've unparked cores, disabled mipmaps, lowered everything, prerenderedframes.. you name it. I've spent countless hours scouring the web and tweaking FC3/4 but the damn hitching still persists. Just wonedering if any miracle solutions have helped anyone here. Thanks.
Awesome fix, game looks amazing. Only problem is the Nvidia 3d crosshair is displaying at a fixed depth. Known issue, or is there a setting i cant find?
Also, is the constant loading/hitching when traveling a permanent Dunia limitation that we just have to live with or have there been successful workarounds? I've unparked cores, disabled mipmaps, lowered everything, prerenderedframes.. you name it. I've spent countless hours scouring the web and tweaking FC3/4 but the damn hitching still persists. Just wonedering if any miracle solutions have helped anyone here. Thanks.
Is there any reason you are using the nvidia crosshair over the in-game one? Personally I can't stand the nvidia one - for me it's always either at a slightly wrong depth (too close) or a very wrong depth depending on the game. [size="S"](Part of the reason I did the auto-crosshair in Miasmata was to prove that it is possible to do something better in the crosshair shader using only the depth buffer - however that approach is difficult and is not supported by 3Dmigoto... yet).[/size]
You can adjust the depth of the in-game crosshair with the x parameter under [Constants] in the d3dx.ini, and the y parameter controls the depth of the weapon sights (-1 will line it up with the glass on the scope, positive values for a percentage of separation). You can also customise the convergence override while aiming under [Key1] (mouse) or [Key2] (controller), which is a large part of what makes this game playable in 3D.
As for the hitching - it sounds like you've already tried all the common suggestions, and depending on your system it may not be possible to eliminate it entirely. If you have an SSD I'd suggest running it off that as the hitching is likely caused by on-demand loading and HDDs are slower at that. If you can keep an eye on your VRAM usage that might provide some clues - if the game is using nearly all your VRAM it will have to discard data more aggressively, which will then need to be loaded again later causing hitching (this is why lowering texture quality and disabling mip-maps keep getting suggested). Terrain detail is also reportedly a major contributor to this.
Is there any reason you are using the nvidia crosshair over the in-game one? Personally I can't stand the nvidia one - for me it's always either at a slightly wrong depth (too close) or a very wrong depth depending on the game. (Part of the reason I did the auto-crosshair in Miasmata was to prove that it is possible to do something better in the crosshair shader using only the depth buffer - however that approach is difficult and is not supported by 3Dmigoto... yet).
You can adjust the depth of the in-game crosshair with the x parameter under [Constants] in the d3dx.ini, and the y parameter controls the depth of the weapon sights (-1 will line it up with the glass on the scope, positive values for a percentage of separation). You can also customise the convergence override while aiming under [Key1] (mouse) or [Key2] (controller), which is a large part of what makes this game playable in 3D.
As for the hitching - it sounds like you've already tried all the common suggestions, and depending on your system it may not be possible to eliminate it entirely. If you have an SSD I'd suggest running it off that as the hitching is likely caused by on-demand loading and HDDs are slower at that. If you can keep an eye on your VRAM usage that might provide some clues - if the game is using nearly all your VRAM it will have to discard data more aggressively, which will then need to be loaded again later causing hitching (this is why lowering texture quality and disabling mip-maps keep getting suggested). Terrain detail is also reportedly a major contributor to this.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Come to think of it I'm not entirely sure why I use the Nvidia crosshair. I guess I just thought we were supposed to? haha. I haven't played too many games in stereoscopic 3d, and the few that I have I sort of liked that the crosshair was deeper in the scene even though you just made me realize that that's not realistic at all. I'll give the ingame another shot and see if i cant get used to it.
I have an aging i5 760 at 4.2, a 970, 8 gigs of 1600, and a 840 evo that performs at only half-speed due to an old something or other on my mobo. Your wording suggests that others have in fact completely cured their stuttering woes?
Come to think of it I'm not entirely sure why I use the Nvidia crosshair. I guess I just thought we were supposed to? haha. I haven't played too many games in stereoscopic 3d, and the few that I have I sort of liked that the crosshair was deeper in the scene even though you just made me realize that that's not realistic at all. I'll give the ingame another shot and see if i cant get used to it.
I have an aging i5 760 at 4.2, a 970, 8 gigs of 1600, and a 840 evo that performs at only half-speed due to an old something or other on my mobo. Your wording suggests that others have in fact completely cured their stuttering woes?
I also like the crosshair deeper into the scene, and would play with the nvidia crosshair if the only alternative was the in-game crosshair at screen depth. But when we fix a game this usually isn't the only option, so most of our fixes will try to make the in-game crosshair more useful as well, by adjusting it's depth (usually with a way to customise this for personal preference) and for shooters we usually add a convergence override to make aiming down sights work. Some of our fixes do still need the nvidia crosshair, but they will usually point that out.
My main problem with the nvidia crosshair is really that it is not deep enough - ideally it would exactly match the depth of the object being aimed at, but it usually ends up floating somewhere in the air instead, which I find distracting.
Lining up the crosshair exactly is difficult (I pulled this off in Miasmata 6B0F82ED.txt), but given the choice between the crosshair being too close or too far, for a first person shooter I find too far less distracting than too close. This might just be personal preference though, which is why I always allow it to be customised in the ini file and/or add key bindings to change it.
Third person games and first person non-shooters are a different story - in these types of games you often need the crosshair to pick up an object pretty close to the camera, so the crosshair being too far is bad, but being too close (or active at inappropriate times) can still be distracting. For a couple of recent games I've worked on I've added keys to cycle the crosshair between several depths and/or added a toggle key to turn it off when not needed (in Stranded Deep I was even able to use the fact that it fades out to disable it automatically when it wasn't needed). If the auto-depth works on the nvidia crosshair it might be a reasonable option for these types of games.
Regarding the stuttering - I'm not sure if anyone has entirely eliminated it, or just minimised it. I've minimised it enough that it doesn't bother me any more, but my performance isn't that great to begin with so maybe I've just got used to it.
I also like the crosshair deeper into the scene, and would play with the nvidia crosshair if the only alternative was the in-game crosshair at screen depth. But when we fix a game this usually isn't the only option, so most of our fixes will try to make the in-game crosshair more useful as well, by adjusting it's depth (usually with a way to customise this for personal preference) and for shooters we usually add a convergence override to make aiming down sights work. Some of our fixes do still need the nvidia crosshair, but they will usually point that out.
My main problem with the nvidia crosshair is really that it is not deep enough - ideally it would exactly match the depth of the object being aimed at, but it usually ends up floating somewhere in the air instead, which I find distracting.
Lining up the crosshair exactly is difficult (I pulled this off in Miasmata 6B0F82ED.txt), but given the choice between the crosshair being too close or too far, for a first person shooter I find too far less distracting than too close. This might just be personal preference though, which is why I always allow it to be customised in the ini file and/or add key bindings to change it.
Third person games and first person non-shooters are a different story - in these types of games you often need the crosshair to pick up an object pretty close to the camera, so the crosshair being too far is bad, but being too close (or active at inappropriate times) can still be distracting. For a couple of recent games I've worked on I've added keys to cycle the crosshair between several depths and/or added a toggle key to turn it off when not needed (in Stranded Deep I was even able to use the fact that it fades out to disable it automatically when it wasn't needed). If the auto-depth works on the nvidia crosshair it might be a reasonable option for these types of games.
Regarding the stuttering - I'm not sure if anyone has entirely eliminated it, or just minimised it. I've minimised it enough that it doesn't bother me any more, but my performance isn't that great to begin with so maybe I've just got used to it.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Get off my lawn ya damn troll!
You say you have less and less time to slog through a mountain of fixes, yet you clearly have enough time to write lengthy troll posts on numerous threads?
Follow the instructions on the blog, or go away.
You say you have less and less time to slog through a mountain of fixes, yet you clearly have enough time to write lengthy troll posts on numerous threads?
Follow the instructions on the blog, or go away.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
[quote="vulcan78"]Wow, with the game on sale I have to say that I am growing less and less willing to slog through a mountain of fixes, none of them very simplistic, simply to get a game working with 3D Vision. I've skimmed through the last 20 pages, let me get this straight, I need to apply a fix from Helix Mod site, start the game, exit the game, minimize the game, then turn the emitter on, then turn terrain to medium oh and since I am using a 2560x1440 monitor I need to do the following to run it without SMAA:
[url]https://forums.geforce.com/default/topic/789514/3d-vision/far-cry-4-3d-screenshots-/post/4492434/#4492434[/url]
Oh and I can forget about using 3D Vision for the Shangrila section, only two hours, that's not immersion breaking at all! And then there's a lot of talk about the pros and cons of using a Max Payne 3 profile and a Far Cry 3 profile with flags? Halos around weapons, not being able to see weapons in the shop, etc. etc. etc. etc. etc.
LMFAO!
You can't be serious!
I'm getting near the end of my rope with the complete disappearance of 3D Vision support. Far Cry 4 is virtually an Nvidia exclusive considering the partnership between Ubibroke and Nvidia (i.e. the superior performance with Nvidia hardware vs. AMD) yet there is no 3D Vision out-of-the-box? WTF?
If this is how it will be from here on out I may say adieu to this nonsense and return to 2D gaming via less expensive and soon to be vastly more powerful AMD alternative (i.e. 390x, and no it won't be priced at $1k). Why are we paying a price premium for Nvidia again? PhysX and garbage drivers? Time for a reality check.
Nvidia and Ubibroke will actually lose money with this one, I refuse to pay anything more than $10 for a Far Cry 3 expansion and having to choose between flawless 2D and nearly completely broken 3D. In fact, as long as I have Nvidia hardware, from here on I will not purchase a game unless it has proper 3D Vision support, period. If I'm to return to 2D gaming, as I said above, I will do so the economical way. No point in paying a price premium considering the now non-existent driver quality assurance and way WAY overpriced hardware. Watch 390x be 30-40% faster than Titan X yet be priced at $700. I'm going to laugh my ass off. I've REALLY, NO SERIOUSLY, had ABSOLUTELY ENOUGH OF NVIDIA'S BS. I'm so frustrated with this. 3D Vision has become a "legacy feature" yet they still have the nerve to ask for $1k for a GPU that WAS ORIGINALLY INTENDED TO BE THE GTX 980. Yeah, you heard that right, Titan X was around during Maxwell's premature launch late 2014 but they offered a gimped down version, what we currently call the GTX 980, as the GTX 980 instead because it would be more profitable to release Titan X for 200% more 6 months later and the "980 Ti", basically the exact same card with half the VRAM 6 months after that. Shenanigans and lies. I'm done. If 390x is considerably faster than GM200 and 3D Vision support does not (I truly do not expect that it will) improve by the end of this year I am completely done with this sham of a product.
[/quote][/quote]
Madman...
vulcan78 said:Wow, with the game on sale I have to say that I am growing less and less willing to slog through a mountain of fixes, none of them very simplistic, simply to get a game working with 3D Vision. I've skimmed through the last 20 pages, let me get this straight, I need to apply a fix from Helix Mod site, start the game, exit the game, minimize the game, then turn the emitter on, then turn terrain to medium oh and since I am using a 2560x1440 monitor I need to do the following to run it without SMAA:
Oh and I can forget about using 3D Vision for the Shangrila section, only two hours, that's not immersion breaking at all! And then there's a lot of talk about the pros and cons of using a Max Payne 3 profile and a Far Cry 3 profile with flags? Halos around weapons, not being able to see weapons in the shop, etc. etc. etc. etc. etc.
LMFAO!
You can't be serious!
I'm getting near the end of my rope with the complete disappearance of 3D Vision support. Far Cry 4 is virtually an Nvidia exclusive considering the partnership between Ubibroke and Nvidia (i.e. the superior performance with Nvidia hardware vs. AMD) yet there is no 3D Vision out-of-the-box? WTF?
If this is how it will be from here on out I may say adieu to this nonsense and return to 2D gaming via less expensive and soon to be vastly more powerful AMD alternative (i.e. 390x, and no it won't be priced at $1k). Why are we paying a price premium for Nvidia again? PhysX and garbage drivers? Time for a reality check.
Nvidia and Ubibroke will actually lose money with this one, I refuse to pay anything more than $10 for a Far Cry 3 expansion and having to choose between flawless 2D and nearly completely broken 3D. In fact, as long as I have Nvidia hardware, from here on I will not purchase a game unless it has proper 3D Vision support, period. If I'm to return to 2D gaming, as I said above, I will do so the economical way. No point in paying a price premium considering the now non-existent driver quality assurance and way WAY overpriced hardware. Watch 390x be 30-40% faster than Titan X yet be priced at $700. I'm going to laugh my ass off. I've REALLY, NO SERIOUSLY, had ABSOLUTELY ENOUGH OF NVIDIA'S BS. I'm so frustrated with this. 3D Vision has become a "legacy feature" yet they still have the nerve to ask for $1k for a GPU that WAS ORIGINALLY INTENDED TO BE THE GTX 980. Yeah, you heard that right, Titan X was around during Maxwell's premature launch late 2014 but they offered a gimped down version, what we currently call the GTX 980, as the GTX 980 instead because it would be more profitable to release Titan X for 200% more 6 months later and the "980 Ti", basically the exact same card with half the VRAM 6 months after that. Shenanigans and lies. I'm done. If 390x is considerably faster than GM200 and 3D Vision support does not (I truly do not expect that it will) improve by the end of this year I am completely done with this sham of a product.
Typical,
Instead of actually thanking the people who IN THEIR FREE TIME developed a fix for FarCry4 where there was none (except CM) and people IN THEIR FREE TIME testing... you come here and say you can't be bothered 2 minutes to apply the fix?
Then you keep going on with the usual crap of AMD vs nvidia GPUS... How is this relevant to the FarCry4 fix? AMD dropped 3D support one year ago... Don't like 3D vision or 2 minutes of your time to apply a fix is too long then don't use 3D vision, or do whatever you want...
But, AT LEAST SHOW SOME RESPECT to the people who were created a fix where there was NONE and troll less:)
Instead of actually thanking the people who IN THEIR FREE TIME developed a fix for FarCry4 where there was none (except CM) and people IN THEIR FREE TIME testing... you come here and say you can't be bothered 2 minutes to apply the fix?
Then you keep going on with the usual crap of AMD vs nvidia GPUS... How is this relevant to the FarCry4 fix? AMD dropped 3D support one year ago... Don't like 3D vision or 2 minutes of your time to apply a fix is too long then don't use 3D vision, or do whatever you want...
But, AT LEAST SHOW SOME RESPECT to the people who were created a fix where there was NONE and troll less:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
In case anyone is confused by the 'difficulty' of getting the fix to work, here are simplified instructions from the blog post. There are more details for more configurations, but the simplest is:
[olist]
[.]Use nvidia inspector to assign the game to the Max Payne 3 profile.[/.]
[.]Unpack zip to Far Cry 4\bin directory[/.]
[.]If game switches to windowed mode after launch, press alt+enter to switch back to full screen[/.]
[.]Set ambient occlusion to HBAO+[/.]
[.]Set Anti-Aliasing to MSAA or TXAA[/.]
[.]Disable motion blur, as it causes rendering artefacts.[/.]
[.]If you are using SLI, set terrain to medium or lower to get good performance.[/.]
[/olist]
I would have thought that Vulcan78 was technical enough to do those steps, but it seems he prefers to spew hate and anger over actually playing games.
In case anyone is confused by the 'difficulty' of getting the fix to work, here are simplified instructions from the blog post. There are more details for more configurations, but the simplest is:
Use nvidia inspector to assign the game to the Max Payne 3 profile.
Unpack zip to Far Cry 4\bin directory
If game switches to windowed mode after launch, press alt+enter to switch back to full screen
Set ambient occlusion to HBAO+
Set Anti-Aliasing to MSAA or TXAA
Disable motion blur, as it causes rendering artefacts.
If you are using SLI, set terrain to medium or lower to get good performance.
I would have thought that Vulcan78 was technical enough to do those steps, but it seems he prefers to spew hate and anger over actually playing games.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
[quote="vulcan78"]Wow, with the game on sale I have to say that I am growing less and less willing to slog through a mountain of fixes, none of them very simplistic, simply to get a game working with 3D Vision. I've skimmed through the last 20 pages, let me get this straight, I need to apply a fix from Helix Mod site, start the game, exit the game, minimize the game, then turn the emitter on, then turn terrain to medium oh and since I am using a 2560x1440 monitor I need to do the following to run it without SMAA:
[url]https://forums.geforce.com/default/topic/789514/3d-vision/far-cry-4-3d-screenshots-/post/4492434/#4492434[/url]
Oh and I can forget about using 3D Vision for the Shangrila section, only two hours, that's not immersion breaking at all! And then there's a lot of talk about the pros and cons of using a Max Payne 3 profile and a Far Cry 3 profile with flags? Halos around weapons, not being able to see weapons in the shop, etc. etc. etc. etc. etc.
LMFAO!
You can't be serious!
I'm getting near the end of my rope with the complete disappearance of 3D Vision support. Far Cry 4 is virtually an Nvidia exclusive considering the partnership between Ubibroke and Nvidia (i.e. the superior performance with Nvidia hardware vs. AMD) yet there is no 3D Vision out-of-the-box? WTF?
If this is how it will be from here on out I may say adieu to this nonsense and return to 2D gaming via less expensive and soon to be vastly more powerful AMD alternative (i.e. 390x, and no it won't be priced at $1k). Why are we paying a price premium for Nvidia again? PhysX and garbage drivers? Time for a reality check.
Nvidia and Ubibroke will actually lose money with this one, I refuse to pay anything more than $10 for a Far Cry 3 expansion and having to choose between flawless 2D and nearly completely broken 3D. In fact, as long as I have Nvidia hardware, from here on I will not purchase a game unless it has proper 3D Vision support, period. If I'm to return to 2D gaming, as I said above, I will do so the economical way. No point in paying a price premium considering the now non-existent driver quality assurance and way WAY overpriced hardware. Watch 390x be 30-40% faster than Titan X yet be priced at $700. I'm going to laugh my ass off. I've REALLY, NO SERIOUSLY, had ABSOLUTELY ENOUGH OF NVIDIA'S BS. I'm so frustrated with this. 3D Vision has become a "legacy feature" yet they still have the nerve to ask for $1k for a GPU that WAS ORIGINALLY INTENDED TO BE THE GTX 980. Yeah, you heard that right, Titan X was around during Maxwell's premature launch late 2014 but they offered a gimped down version, what we currently call the GTX 980, as the GTX 980 instead because it would be more profitable to release Titan X for 200% more 6 months later and the "980 Ti", basically the exact same card with half the VRAM 6 months after that. Shenanigans and lies. I'm done. If 390x is considerably faster than GM200 and 3D Vision support does not (I truly do not expect that it will) improve by the end of this year I am completely done with this sham of a product.
Example:
[quote="Cheezeman"]So I went out and bought another 970 for SLI today just so I can play this in higher settings, but I'm having a hell of time getting things working on higher settings. Things I've learned:
1) Using MP3 profile results in near perfect SLI scaling (don't need FC3 sli bits), both GPUs at 98%+.
2) I have to disable 3D as soon as the game starts, as when you 'press key to continue' and the game quickly minimizes it will never recover and just stays at black screen. Once at the main menu or in the game world you can re-enable 3D just fine.
3) Setting 'Terrain' to Medium is a must. Setting this any higher results in crushing FPS drops for no apparent reason.
4) Upping certain graphics settings will cause my computer to spontaneously reboot!!! So far 'Geometry' and 2xMSAA seem to cause this to happen. I will test more over time as I can but I've already caused my comp to reboot like 30-40 times in the past 3 hours. I'm just going to try playing for a while on settings I know work for now. For now it seems 'Textures' to Ultra and Shadows to 'soft shadows' works OK. I'm going to try to slowly up other settings over time.
I tested all of the above with the various profile configs -- FC4 with StereoDX10Flags, null profile with fc3 bits, MP3 profile with FC3 bits -- with the same results across the board; have to disable 3D at start, upping certain settings causes spontaneous reboot. I am not wholly certain about SLI scaling in the other profiles as I didn't discover the Terrain to medium setting yet, so they may be viable too, but certainly MP3 vanilla profile seems to works well.
(I tried playing BF4 for a while at 150% supersample with all settings maxed just to make sure SLI is working properly or that the reboots weren't being caused by a power draw issue, it played just fine with all 4 CPUs and both GPUs maxed. Also tried re-appyling the patch, verifying game files, and clean driver install)
[/quote][/quote]
So I've not been in the forum much for the past month, but then I come back and see several threads from this guy ranting like a lunatic about capitalism and big bad nvidia, and how bad 3D vision is, and now slagging off the people who provide free game fixes... Huh?
Vulcan78 - you are an A*SHOLE. Go the F*CK away.
vulcan78 said:Wow, with the game on sale I have to say that I am growing less and less willing to slog through a mountain of fixes, none of them very simplistic, simply to get a game working with 3D Vision. I've skimmed through the last 20 pages, let me get this straight, I need to apply a fix from Helix Mod site, start the game, exit the game, minimize the game, then turn the emitter on, then turn terrain to medium oh and since I am using a 2560x1440 monitor I need to do the following to run it without SMAA:
Oh and I can forget about using 3D Vision for the Shangrila section, only two hours, that's not immersion breaking at all! And then there's a lot of talk about the pros and cons of using a Max Payne 3 profile and a Far Cry 3 profile with flags? Halos around weapons, not being able to see weapons in the shop, etc. etc. etc. etc. etc.
LMFAO!
You can't be serious!
I'm getting near the end of my rope with the complete disappearance of 3D Vision support. Far Cry 4 is virtually an Nvidia exclusive considering the partnership between Ubibroke and Nvidia (i.e. the superior performance with Nvidia hardware vs. AMD) yet there is no 3D Vision out-of-the-box? WTF?
If this is how it will be from here on out I may say adieu to this nonsense and return to 2D gaming via less expensive and soon to be vastly more powerful AMD alternative (i.e. 390x, and no it won't be priced at $1k). Why are we paying a price premium for Nvidia again? PhysX and garbage drivers? Time for a reality check.
Nvidia and Ubibroke will actually lose money with this one, I refuse to pay anything more than $10 for a Far Cry 3 expansion and having to choose between flawless 2D and nearly completely broken 3D. In fact, as long as I have Nvidia hardware, from here on I will not purchase a game unless it has proper 3D Vision support, period. If I'm to return to 2D gaming, as I said above, I will do so the economical way. No point in paying a price premium considering the now non-existent driver quality assurance and way WAY overpriced hardware. Watch 390x be 30-40% faster than Titan X yet be priced at $700. I'm going to laugh my ass off. I've REALLY, NO SERIOUSLY, had ABSOLUTELY ENOUGH OF NVIDIA'S BS. I'm so frustrated with this. 3D Vision has become a "legacy feature" yet they still have the nerve to ask for $1k for a GPU that WAS ORIGINALLY INTENDED TO BE THE GTX 980. Yeah, you heard that right, Titan X was around during Maxwell's premature launch late 2014 but they offered a gimped down version, what we currently call the GTX 980, as the GTX 980 instead because it would be more profitable to release Titan X for 200% more 6 months later and the "980 Ti", basically the exact same card with half the VRAM 6 months after that. Shenanigans and lies. I'm done. If 390x is considerably faster than GM200 and 3D Vision support does not (I truly do not expect that it will) improve by the end of this year I am completely done with this sham of a product.
Example:
Cheezeman said:So I went out and bought another 970 for SLI today just so I can play this in higher settings, but I'm having a hell of time getting things working on higher settings. Things I've learned:
1) Using MP3 profile results in near perfect SLI scaling (don't need FC3 sli bits), both GPUs at 98%+.
2) I have to disable 3D as soon as the game starts, as when you 'press key to continue' and the game quickly minimizes it will never recover and just stays at black screen. Once at the main menu or in the game world you can re-enable 3D just fine.
3) Setting 'Terrain' to Medium is a must. Setting this any higher results in crushing FPS drops for no apparent reason.
4) Upping certain graphics settings will cause my computer to spontaneously reboot!!! So far 'Geometry' and 2xMSAA seem to cause this to happen. I will test more over time as I can but I've already caused my comp to reboot like 30-40 times in the past 3 hours. I'm just going to try playing for a while on settings I know work for now. For now it seems 'Textures' to Ultra and Shadows to 'soft shadows' works OK. I'm going to try to slowly up other settings over time.
I tested all of the above with the various profile configs -- FC4 with StereoDX10Flags, null profile with fc3 bits, MP3 profile with FC3 bits -- with the same results across the board; have to disable 3D at start, upping certain settings causes spontaneous reboot. I am not wholly certain about SLI scaling in the other profiles as I didn't discover the Terrain to medium setting yet, so they may be viable too, but certainly MP3 vanilla profile seems to works well.
(I tried playing BF4 for a while at 150% supersample with all settings maxed just to make sure SLI is working properly or that the reboots weren't being caused by a power draw issue, it played just fine with all 4 CPUs and both GPUs maxed. Also tried re-appyling the patch, verifying game files, and clean driver install)
So I've not been in the forum much for the past month, but then I come back and see several threads from this guy ranting like a lunatic about capitalism and big bad nvidia, and how bad 3D vision is, and now slagging off the people who provide free game fixes... Huh?
On the other hand I'm not entirely familiar with how gaming works on multi monitor setups like surround so I may be wrong... I'm also not sure how it works in windowed mode, but given 3D doesn't work in DX11 windowed mode we can probably ignore that.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
I got into shangri la again - now it's ok, it seems the very first mission is messed up
http://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx
FWIW I've also added aliases for common key names, so even if you don't look up the correct name you can just guess the obvious name and it will probably work as well... Have you tried "capslock"?
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Does anyone know how I can force far cry to be progressive rather than interlaced.
Thanks.
Also, is the constant loading/hitching when traveling a permanent Dunia limitation that we just have to live with or have there been successful workarounds? I've unparked cores, disabled mipmaps, lowered everything, prerenderedframes.. you name it. I've spent countless hours scouring the web and tweaking FC3/4 but the damn hitching still persists. Just wonedering if any miracle solutions have helped anyone here. Thanks.
You can adjust the depth of the in-game crosshair with the x parameter under [Constants] in the d3dx.ini, and the y parameter controls the depth of the weapon sights (-1 will line it up with the glass on the scope, positive values for a percentage of separation). You can also customise the convergence override while aiming under [Key1] (mouse) or [Key2] (controller), which is a large part of what makes this game playable in 3D.
As for the hitching - it sounds like you've already tried all the common suggestions, and depending on your system it may not be possible to eliminate it entirely. If you have an SSD I'd suggest running it off that as the hitching is likely caused by on-demand loading and HDDs are slower at that. If you can keep an eye on your VRAM usage that might provide some clues - if the game is using nearly all your VRAM it will have to discard data more aggressively, which will then need to be loaded again later causing hitching (this is why lowering texture quality and disabling mip-maps keep getting suggested). Terrain detail is also reportedly a major contributor to this.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
I have an aging i5 760 at 4.2, a 970, 8 gigs of 1600, and a 840 evo that performs at only half-speed due to an old something or other on my mobo. Your wording suggests that others have in fact completely cured their stuttering woes?
My main problem with the nvidia crosshair is really that it is not deep enough - ideally it would exactly match the depth of the object being aimed at, but it usually ends up floating somewhere in the air instead, which I find distracting.
Lining up the crosshair exactly is difficult (I pulled this off in Miasmata 6B0F82ED.txt), but given the choice between the crosshair being too close or too far, for a first person shooter I find too far less distracting than too close. This might just be personal preference though, which is why I always allow it to be customised in the ini file and/or add key bindings to change it.
Third person games and first person non-shooters are a different story - in these types of games you often need the crosshair to pick up an object pretty close to the camera, so the crosshair being too far is bad, but being too close (or active at inappropriate times) can still be distracting. For a couple of recent games I've worked on I've added keys to cycle the crosshair between several depths and/or added a toggle key to turn it off when not needed (in Stranded Deep I was even able to use the fact that it fades out to disable it automatically when it wasn't needed). If the auto-depth works on the nvidia crosshair it might be a reasonable option for these types of games.
Regarding the stuttering - I'm not sure if anyone has entirely eliminated it, or just minimised it. I've minimised it enough that it doesn't bother me any more, but my performance isn't that great to begin with so maybe I've just got used to it.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
You say you have less and less time to slog through a mountain of fixes, yet you clearly have enough time to write lengthy troll posts on numerous threads?
Follow the instructions on the blog, or go away.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Madman...
Instead of actually thanking the people who IN THEIR FREE TIME developed a fix for FarCry4 where there was none (except CM) and people IN THEIR FREE TIME testing... you come here and say you can't be bothered 2 minutes to apply the fix?
Then you keep going on with the usual crap of AMD vs nvidia GPUS... How is this relevant to the FarCry4 fix? AMD dropped 3D support one year ago... Don't like 3D vision or 2 minutes of your time to apply a fix is too long then don't use 3D vision, or do whatever you want...
But, AT LEAST SHOW SOME RESPECT to the people who were created a fix where there was NONE and troll less:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
I would have thought that Vulcan78 was technical enough to do those steps, but it seems he prefers to spew hate and anger over actually playing games.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
So I've not been in the forum much for the past month, but then I come back and see several threads from this guy ranting like a lunatic about capitalism and big bad nvidia, and how bad 3D vision is, and now slagging off the people who provide free game fixes... Huh?
Vulcan78 - you are an A*SHOLE. Go the F*CK away.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278