Forum Replies Created
-
Posts
-
Mmmh, no changes to both profiles since last October, before branching off 19.1.0. I’ll look into it.
The menu thing is to be expected, the games don’t clear the depth buffer while showing the menu. Quite a few games do that.
IIRC both games have resolution scaling in their graphics options. While in general that is a fantastic option for vorpX in newer games, it sometimes can confuse the depth buffer heuristics unfortunately. Worth to try 100% if you changed that setting. Same for trying with/without antialising.
Depends very much on the location. With a 1080Ti and the “very high” graphics preset framerate can be anything from borderline playable to full 90fps. You have a 1060 IIRC? If so trying with low/medium details is worth a shot.
You can switch between G3D/Z3D with ALT+K by the way. A good way to deal with occasional low framerate situations. The shortcut can also be re-assigned to something easier accessible in the config app if use it more frequently.
@ Nikolai: Beautiful, isn’t it? Although not really my cup of tea usually some of these sidescroller/platform games are really fascinating with added stereo 3d depth. Ori and the Blind Forest, Unravel or Inside are also great.
All more than worth a try for everyone who likes to (maybe) be surprised by something they wouldn’t consider obvious vorpX candidates normally.
Unless it has to be fixed for every weapon individually, it should be fixed. I only checked the introduction mission though, so I’m not entirely sure.
If you still encounter the issue later in the game with different weapons, let me know.
Not reproducible here, works fine with both regular and alternative hooking. Please check for programs on your PC that might interfere with hooking: first and foremost virus scanners, also any CPU/GPU utility, video recording/streaming apps, messengers and generally everything that can show notifications in games.
If hooking issues suddenly appear after a vorpX update, your virus scanner is the most likely candidate. Might make sense to exclude the vorpX program folder to avoid potential issues in that regard.
Just in case: if you are using a third party AV program, you should consider to switch to Windows Defender. It’s just as good as the best third party AV apps these days, but less invasive and less likely to cause problems. On Windows 10 Windows Defender kicks in automatically when you uninstall a third party AV program.
Thanks guys. Always nice to hear a few kind words, especially after a rather busy game testing week.
Enjoy the update! More to come (as always).
@ all: thanks guys!
@ dellrifter: the automated profile updates are ‘just’ a way to push profile fixes without you having to check/download them manually from the cloud. vorpX checks on start whether a new database build is available on the server. If so, your local profile database is updated with the new one similar to how it happens during a vorpX update.
The worst thing that might happen is that a handful won’t work right anymore, so no need to check everything. Probably not even that, profile backwards compatibility is handled extremely carefully. I just can’t be 100% sure for every potential edge case this time unfortunately.
Resetting your Steam password shouldn’t be much of a problem.
If you haven’t done so already, trying the new alternative hooking method is worth a shot. It should not be used always, but might be useful from time to time if a specific game fails to hook. You can enable it on the “General” page of the config app.
BTW: Make sure that you don’t have settings optimizations disabled. vopX has to change some .ini values for G3D to work correctly with this game.
No white lines here in a brief test. There weren’t many changes to D3D9 all in this update, actually just some device reset related fixes that certainly can’t create white lines. So your issue might just be a coincidence. Please try without mods if you are using any now.
I’ll check a bit more thorough next week to be sure.
Setting an exact 4:3 resolution (e.g. 1600×1200) should resolve the FOV flicker normally. Also try to run the game windowed if you are running it fullscreen now or vice versa. Some occasional weapon flicker might remain unfortunately.
Also make sure that nothing is running in the background that is taxing your CPU. DirectVR requires an entire core on its own for this game. On mid-range quad core systems without hyper threading (i5), or even worse laptops, that might get difficult if something is running in the background that also uses many CPU cycles.
Since DirectVR apparently didn’t work for you before, disabling it brings you back to exactly the state you had before. Not sure why you want that, but of course you can do it.
Again: FOV has always been handled by DirectVR. If you could change it in an .ini before, nothing was working fine. In fact everything was broken in that case. You can however go back to that broken state by disabling DirectVR if you prefer that.
There may be a faint outline around characters under certain conditions, but it shouldn’t be distracting in any way with default settings.
In general: please always first check whether anything you consider broken also appears broken with default settings. Defaults are usually chosen carefully. Most of the time it’s best not to change them.
No, there isn’t, sorry. I cannot provide support for multipe versions. If you had to adjust the FOV in an .ini file before, nothing worked fine. FOV is handled by DirectVR for years. You can adjust the the weapon FOV independently from the world FOV in the vorpX menu if you think that makes sense.
If any .ini edits you made had an effect before, DirectVR was not working as it should have. You will want to use DirectVR with this game as it also provides far superior head tracking.
You can adjust the the weapon/pipboy FOV independently from the world FOV in the vorpX menu if you think that makes sense.