Forum Replies Created
-
Posts
-
Just an observation: both me and markus are running the Steam version of the game(s) on an WMR headset (Samsung Odyssey+ in my case).
Hi markus,
FC3/4 integration is broken–this has already been reported by multiple people. Don’t expect any support from the developer though, the only thing you’ll get will be quotes from the manual and subtle hints that you or your system are at fault.
The first thing you need to know is that for FC3/4, it will take an insane amount of time to hook; I’m talking 5 minutes at least. You just have to be patient.
Then, after Vorpx updates the config, you have to kill the game and manually update the config file, setting the refresh rate to 0. Follow the directions from this post:
https:// http://www.vorpx.com/ forums/ topic/ far-cry-4-black-screen/ page/ 2/ #post-198112
Any updates on these?
– Is there a way to profile the game to find out where the bottleneck is (GPU, video memory, CPU?)
– Are you able to reproduce the black screen issue by setting the RefreshRate to 60 in your GamerProfile.xml?
PS I’m slowly getting frustrated by this support forum.
Hi Ralf, thank you for responding on Sunday–you can be sure I’ve tried all the config variations. The only two things Vorpx does really is change the FOV and change the AA mode in case it’s anything other than “2.” I didn’t change the FOV, and I tried both “2” and “4” for the AA, with the FPS being abysmal in both cases and the bloom layer “standing out.”
In case of NFS Rivals, I didn’t touch the config at all.
Re 1)–I too had figured it wasn’t a bug, that’s why I wrote that maybe some of the things I’d listed were features.
Re 2)–I don’t know how best to describe it. G3D works perfectly on the world geometry itself, but the bloom around the specular highlights feels like it’s sitting in a totally separate, flat layer glued to the screen. It’s right there in the first scene (“the dinner”), so I doubt a savegame would help much. I’ve got the same problem in NFS Rivals. I saw somebody on the forum mention the same about another game.
Re 3)–Yes, I get it that I can speed things up by cranking down every setting, but that’s beyond the point. I’m playing on a GTX 1070 which admittedly isn’t a top dog, but I presume something’s not right if it goes from 120 to 28 (more than 75% decrease in performance–c’mon). Is there a way to profile the game to find out where the bottleneck is (GPU, video memory, CPU?).
Here are some more bugs (or are some of them features?):
1. Regardless of which anti-aliasing mode you choose, Vorpx rewrites the config to set it to “2.” The only way out here is to run the game without Vorpx, do the setup, run the game with Vorpx, disable rewriting the config, then change the anti-aliasing mode in the text editor (because if you do it in-game, FC4 will set the refresh rate to 60 and Vorpx will black-screen).
2. With G3D, the bloom layer has an incorrect depth, and the picture is literally falling apart. I’ve got the same problem in Need For Speed, but obviously not in Quake4 and other older games which don’t make use of post-processing.
3. G3D FPS is horrendous. I get 120 FPS on ultra-high without Vorpx; 28 FPS with Vorpx (identical config). I can understand Vorpx halving the FPS, I can understand a small injection penalty (let’s say -10 FPS?), which would bring me down to 50. But 28? It’s literally unplayable on my rig.
Ralf, are you able to reproduce the black screen issue by setting the RefreshRate to 60 in your GamerProfile.xml?
Okay, so after two days of straight f**king with the game’s, Steam’s, Uplay’s, and Vorpx’s settings, I’ve figured out the problem, the reason behind it, and the solution.
Why it took me so long: there’s not one, but two issues at play here. One is hampering Vorpx and causing the black screen, another is directly caused by Vorpx itself. Because of that, it’s difficult to figure out what’s happening.
ISSUE #1 (THE SECONDARY ONE)
(At least in the Steam version of the game,) Vorpx’s injector messes up with FC4’s loading process.Because of that, loading takes ~5 minutes instead of ~20 seconds, and the game will freeze on “Login succeeded.” You’ll need to patiently wait until it unfreezes and displays the “Cannot reach Far Cry 4 servers” message. After that, you won’t be able to play online.
This issue will persist even if you solve Issue #2.
PARTIAL SOLUTION: obviously, to prevent Vorpx from f**king up the loading process. To achieve that, pause the Vorpx’s Watcher, start the game, wait until the Ubisoft logo comes up, resume the Watcher. The loading process will take the usual 20 seconds, and you will be able to play online, but Geometry3D will remain disabled, and the game will give you a light vertigo.
ISSUE #2 (THE PRIMARY ONE)
If you change FC4’s graphics settings via the in-game menu, FC4 WILL SET THE REFRESH RATE TO 60. THIS WILL CAUSE THE BLACK SCREEN EVERY TIME YOU’LL TRY STARTING THE GAME.This is why somebody in this thread had suggested deleting all the files from the MyGames folder: if you do that, the refresh rate will revert back to 0.
SOLUTION: Start the game with Vorpx, kill it or exit it properly, go to c:\Users\[username]\Documents\My Games\Far Cry 4\[uuid]\, and update both GamerProfile.xml.vorpxbak and GamerProfile.xml, setting RefreshRate=”0″.
If it’s of any relevance, I’m running the Steam version with the “Season Pass” (i.e. all the DLCs installed).
Here’s what I wrote:
Hi Ralf! Thank you for responding (if not solving the issue), I greatly admire your work. Vorpx is a wonderful tool.
Forget the DirectVR scan, I’ve only mentioned it because I thought it might help you debug the problem.
First of all, most people here are running the Steam version. If it’s not too much trouble, would there be any chance of you testing Vorpx on that version? If the integration only works for the Origin one, it’s okay, the game’s on sale right now and I don’t mind spending another 15 bucks–however, I want to know if it’ll work first.
Meanwhile, I think I’ve figured out what the root of the problem is.
-
1. If the Steam version is launched with Vorpx trying to inject itself from the start, the injector messes up with the loading process somehow; this is evidenced by the fact the loading with Vorpx enabled takes 3-4 minutes as opposed to the normal ~20 seconds without it.
2. More specifically, Vorpx seems to prevent the game from connecting to the Ubisoft servers. After displaying the FC4 logo and trying to “log in,” the main window goes unresponsive while the headset switches to pitch black.
3. After a prolonged period of time, the main window comes back and spews out a message saying it can’t connect to the FC4 servers. After that, it’s possible to start the game offline in Windows, but the headset never recovers.
4. The only way to prevent this is to pause the Watcher and resume it after the loading finishes and the Ubisoft logo appears; however, in that case, the injection itself doesn’t proceed properly, and G3D remains disabled.
I would really appreciate your support here. I only bought FC4 to play it with Vorpx–I’ve got no other use for a 2014 FPS.