Forum Replies Created
-
Posts
-
G3D shouldn’t be selectable in AC:Origins, sorry for the confusion. At this point the game is still Z3D only.
If you want to play the game in full VR mode without a “fishbowl effect”, you have to raise the field of view in the game’s options menu to the max and then use the Image Zoom option in vorpX to account for the rest since the FOV itself can’t be set high enough unfortunately.
If you don’t know what FOV means or the instructions above seem complicated to you, please simply reset the profile to its factory default in the config app. Since vorpX can’t adjust the FOV automatically for ESO, the profile defaults to immersive screen mode, which doesn’t require a perfectly fitting FOV.
Please check whether the request shown in the license dialog is still the same as before. if not, please request a new key with the new code.
In most games the cursor should auto-hide. If that fails, ALT+C should do the trick.
If you want to map hotkeys to a gamepad, you can do that after enabling the “Override X-Box Gamepad” option in the vorpX menu (Input Settings page). Alternatively you could use an external mapping program like X-Padder or Pinnacle Profiler if you want something with more options than the built in override provides.
The situation is better than before, but apparently still not perfect. I literally spent two full weeks on this, rewrote half of the DX9 pipeline, even implemented a custom memory allocation just to find the root cause of this issue, but no dice. Extremely odd and diffcult to debug problem that seems to be exclusive to this one game.
The next vorpX version will get support for the HD versions of Bioshock 1+2. While they perform worse with vorpX due to their extremely lackluster DX11 conversion, you should be able to play Bioshock 2 without crashes that way in the not too distant future.
Without having a tried it, a streaming app that can stream SteamVR games (with vorpX in SteamVR mode) should be enough for that. IIRC Trinus can do that, not sure though whether that supports the Go.
@ nieda : Far Cry 5 is unlikely to happen. The game uses anti cheat software that prevents vorpX from hooking into it. Unfortunately they don’t reply to inquiries about whitelisting. Whithout even being able to talk to someone there is not much I can do.
@ dellrifter : IIRC I implemeted that option sometime last year on someone’s request (maybe yours?).
You have to restart the game though after changing it. Once the ALT key is added to the blocked keys list, it doesn’t get removed when you change the option. On next start however it won’t be added to that list in the first place, so a restart should do the trick.
Admittedly not exactly ideal, I will change that in the next update to make it more intuitive.
That should be easy to solve. vorpX doesn’t handle these old DX7 games directly, you need to copy the dgVoodoo2 wrapper to the folder where the game’s main exe is. It converts DX7 to DX11, which vorpX can handle.
@ nieda : Come on, don’t be mad about a little jest. You literally asked for it with your post. Of course not every single update can have something for everyone. I always try to have at least one game of any popular genre in each larger update though, so maybe next time there is one for you again too.
@ redushi : Not really sure what to recommend, sorry. Except basic things like making sure the Oculus software is up-to-date. Also using vorpX in SteamVR mode is worth a try, that would also work with an Oculus.
No problem. I would have been genuinly shocked to not see you complain about something. ;) Considering that you bought vorpX years ago and probably got 20 or so free updates since then, I hope you can live with this one not being for you. Maybe the next one will have something in store for you again.
Nice find. Now they just have to release the game without the Microsoft Store protection and we can check for ourselves…
vorpX 18.2.2 has been released. This is a hotfix release that addresses the issue below. No other changes.
- Multi-threaded hosts could crash during shader init (e.g. Dark Souls III)
A hotfix (18.2.2) is available now that should address these crashes.
Please let me know whether you still experience the issue with vorpX 18.2.2. Thanks in advance.
I still haven’t tried dgVoodoo myself on Win7, but TBH I’m a bit surprised that the trick vorpX uses to make it work fails on Win7.
One thing you could check is whether you run the games you tried with a compatibility mode setting (e.g. Vista, XP or even lower). If so, disable any compatibility mode setting.