Forum Replies Created
-
Posts
-
Don’t you ever say Dishonored 2 to me again. I literally spent over 2 weeks – enduring up to five minutes load times per game start – to even get that thing show up correctly, only to realize that G3D does nothing although it should.
There will be a Z3D profile for the game in the next vorpX version, but I can’t promise more. I won’t rule anything out, I just can’t promise more. Loading times are often so prohibitive long that it’s almost impossible to actually work on the title. Maybe some issue with their implementation of the Denuvo copy protection in conjunction with vorpX, that’s just a guess though. Sometimes loading times feel almost normal, but most of the time starting the game takes forever.
Prey (the new one) is in my Steam library and looks like a good candidate, but I haven’t looked into it yet. So I can’t say anything profound.
The best games to start with are undoubtedly those with Direct VR support. After applying Direct VR these have perfect 1:1 head tracking and perfect FOV without the need for any further setup. In *some* cases Direct VR even provides basic roomscale, i.e. you can walk around a bit more freely than with the normal vorpX positional tracking.
In no particular order:
Bioshock 1 (original version in DX9 mode)
Bioshock 2 (original version in DX9 mode)
Bioshock Infinite
Borderlands 2
Borderlands Pre-Sequel
Skyrim (original DX9 version is best for VorpX)
Fallout 3
Fallout New Vegas
Fallout 4
Dishonored
Half-Life 2 (incl. Ep. 1+2)
The Stanley Parable
Dear Esther (Source engine version)
Portal
Portal 2
Black Mesa
Deus Ex: Human Revolution
Left 4 Dead 2
Mirror’s Edge
Aliens Colonial Marines
Duke Nukem Forever
Quake III
Star Trek Voyager Elite Force
Return to Castle Wolfenstein [2001]My latest personal recommendation would be Half-Life 2 Episode 1, which I just recently played for two hours. Something I don’t do nearly as often as I’d like to these days. Call me heavily biased, I am for sure, but that was more fun than 99% of made for VR games. I actually ended up doing that after buying and trying a bunch of highly praised made for VR titles the same evening.
In case someone never played HL2 Episode 1: right at the start you enter an alien fortress, which not only still looks great after all these years, it’s also a perfect-for-VR mix of shooting sequences and (easy) physics puzzles. Most importantly: all that in a highly intense atmosphere that almost inescapably sucks you into the game. Creating such an intense atmosphere is the hard part of making good single player shooters and it really makes all the difference in VR. Hard to top if you ask me.
Similar things could be said about Bioshock, Black Mesa (Half-Life 1 remake), the Fallout games, Skyrim or – insider tip – Aliens: Colonial Marines, which may just be a mediocre shooter on the monitor, but is actually great with vorpX.
Important side note: whenever possible play standing with Touch controllers or Vive wands!
One last thing: not a Direct VR game, but also extremely intense (and visually great) is Resident Evil 7. I chickened out before the introduction mission was over. Good luck with that one.
There hasn’t been any changes to the basic rendering pipeline in vorpX. Direct VR isn’t really related to the graphics pipeline, and all that is related is basically the same as before. The headset vendor’s runtimes however evolve quickly and so far aren’t really SLI friendly on their own, so I wouldn’t rule out that overall recently something may have changed that causes trouble for SLI.
You could try the “Direct Mode GPU Sync” setting in the display page of the ingame menu (requires expert settings enabled in the config app). Per default it’s usually set to the most conservative option though, so unless you changed it before that probably won’t help.
If you happen to use a Rift, it might also be worth a try to switch to Steam VR in the config app instead of using the Oculus mode. Maybe that makes a difference.
Since January both Fallout 4 and Portal 2 have full Direct VR support. Among other things that means that FOV is automatically set 100% correct for both games without anything needed than a click on the Direct VR scan button after entering the game.
The plot thickens: judging from the IP addresses all three reports about this issue are from Australia and an ISP called Optus, which almost certainly isn’t a coincidence.
A not unlikely option seems to be that Optus cached the installer file, which then got corrupted in their cache, and because of that you get a corrupted one although the original file on the server here is perfectly fine. Might make sense to contact them and ask whether that could be the case.
vorpX is not supposed to hook into that exe. It should be safe to ignore the message, but to avoid it alltogether, please add the .exe to the exclusion list in the vorpX config app.
Normally everything in the SteamVR folder should be excluded automatically, apparently finding the Steam folder on your system fails for some reason.
Please make sure to adjust camera field of view with the Game Optimizer in the vorpX config app prior to launching the game.
If that fails for some reason, you can do it with a manual ini edit using the insructions given by this Arma 3 FOV calculator. You need an FOV of 110° horizontically.
Unfortunately it’s impossible to recreate the issue here. It’s also hard to even think of anything except some external factor that might corrupt the vorpConfing.exe, which obviously is totally fine within the installer archive and extracts perfectly fine in almost all cases.
The issue will be investigated further, but right now there is nothing I can recommend besides what I recommended above, sorry.
Windows Defender does not cause any problems here, please double check whether you maybe have other “internet security” software or something similar installed that might cause problems. There definitely is no issue with setup file on the server, it somehow has to get corrupted during download, or (more likely) extraction on your PC, otherwise the installer would most likely report a checksum error on start.
The setup on the server has been re-uploaded nonetheless just in case it might have been a very odd general issue with the file that only causes issues for every 100th download or so.
Very odd issue. This has never been brought up until a few days ago. Might be an odd virus scanner problem with the latest version. Try to disable your virus scanner.
Please also try to completely uninstall vorpX and then remove the vorpX program folder manually before reinstalling. It can be found in C:\Program Files (x86)\Animation Labs\vorpX
BTW: if you use anything else than Windows Defender, I would highly suggest to switch to that, some rather annoying over scanners cause trouble with each new vorpX build.
Please make sure that the name field looks *EXACTLY* like in the e-mail you received. That is almost certainly the issue.
It has to contain your name followed by the e-mail address in parantheses, exactly like in the mail you got.
Take a look at the example image that is attached to the key e-mail. It shows how it is supposed to look.
Use COPY AND PASTE to avoid typos.
Please first try to reinstall vorpX, normally the installer should take care of installing missing MSVC DLLs.
If that does not help, please install the MSVC runtime libraries manually from the Microsoft website:
https://www.microsoft.com/en-us/download/details.aspx?id=40784
You need to disable BattleEye in the Arma III launcher, then it should work. BattleEye completely blocks the way vorpX uses to hook into games, discussing the matter with its programmer lead nowhere unfortunately.
Please try to disable your virus scanner. The latest update only fixed a single bug, certainly nothing that could potentially lead to vorpX not working anymore. Your description sounds a lot like a conflict with some other software.
Some overzelaous AV scanners however “detect” each new vorpX as potentially malicious since it hooks into otherf programs. If you use anything else, I would highly suggest to switch to Windows Defender, which provides good protection without being as annoying as some other scanners.