Forum Replies Created
-
Posts
-
Interesting. I don’t think there is any other version than the Steam version, so that’s probably not the issue.
I’ll check the matter. If capping the framerate indeed helps, I could implement an FPS cap. Normally vorpX tries to remove any FPS caps if a game has one, but in this case the opposite might make sense.
Just a heads-up that the game has full DirectVR support, including FOV and head tracking. Unless DirectVR does not work correctly for your version, there is no need for a replacement .exe, cloud profile or manual tweaking.
If everything works as it should, DirectVR provides perfect 1:1 head tracking and FOV without the need to change any settings using the default profile.
Please try the latest stable PiTool release linked above, not some beta version. Won’t necessarily solve your problem, but removing beta versions from the equation (PiTool as well as potentially SteamVR) is the first thing you should do.
You can create a trouble shoot data archive in the config app. This archive contains a logfile.
Also please double check whether you really have set up everything as suggested in the Pimax recommendations. Especially the render quality settings in both PiTool and SteamVR are important.
If you haven’t done so already: make sure that you are using the latest regular non-beta PiTool from here. Also make sure that SteamVR (please also use the regular version not the beta version) and your GPU drivers are up-to-date. PiTool requires relatively new drivers.
Vulkan definitely won’t work, OpenGL still works here. Please note though that the game is not officially supported, OpenGL support in vorpX only fully covers older OpenGL versions up until about Doom 3/Quake 4.
However, if it doesn’t hook at all in OpenGL mode, please check for the ‘usual suspects’ in regard to hooking issues: virus scanners, GPU/CPU utilities, messengers, game recording/streaming apps, generally everything that can show notifications in games.
If you haven’t done so already, trying the alternative hooking method in the config app is also worth a shot. Caveat: the alternative method is not meant for general use. Only activate it in case of issues with a specific game.
Profiles and settings can be shared either via cloud up/downloads or as files via drag/drop from/to the local profiles list.
Unfortunately the DirectVR memory scanner always comes with a certain risk of crashes based on your invidual machine/config. Hence the message in that regard that is shown every time the scanner runs.
I’ll see whether I can find something general, but considering how long the DirectVR scanner profile already exists without such reports, it’s more likely something individual.
You can play the game without running the DirectVR scanner. The most important thing you will need in this case is a way to raise the FOV above the max. value the game allows.
For mouse based head tracking the right sensitivity can differ depending on various factors. Most importantly the mouse sensitivity dialed in the game options, but also the mouse used and in some games the resolution/aspect ratio.
It often is, but you cannot expect this value to interchangeable under all circumstances.
A good and fast method to calibrate mouse based head tracking is described here.
Don’t get too excited yet. A first contact is better than nothing, but far from anything being done. I’ll let you know if something actually comes out of this.
This is the vorpX support forum. If you want to discuss things unrelated to vorpX, please do so elsewhere. Thanks for your understanding.
The ‘Play Style’ option is usually set per default to the one that suits a game best. Third person games like Mass Effect are best played in cinema or immersive screen mode. Full VR mode is primarily meant for first person games.
Technically you can also play third person games in Full VR mode, but that rarely is a good experience due to how third person cameras work. For Full VR mode games also need to have their field of view matched to the headset. Please check the Essential Hints Guide to learn more about that.
For a selection of games that allow you to hop right into FullVR without any configuration check this post: Good Full VR Games for Beginners.
Please try a full factory reset in the config app. The games should hook fine normally. If the factory reset does not help, please check the stickied trouble shooting thread above, especially the part regarding conflicts with other programs.
Judging from your log nothing unusual is happening, vorpX hooks the game and starts rendering to the headset, the 101 Submit error is perfectly normal and happens with every game on the first frame. Until you see it more than once, it doesn’t mean anything.
As far as the log is concerned everything looks correct, so unfortunately it is of no help here.
That’s not an issue. Wherever half the headset’s refresh rate is used, vorpX uses half the actual refresh rate, not fixed 45fps.
Please try a full factory reset (trouble shooting page in the config app). If you find your game in the ‘Local Profiles’ list, the according profile is active. Blue means that you are using a custom profile made by another user, which ist not necessary if a game is already in the ‘Local Profiles’ list.
In regard to hooking issues, please check the trouble shooting sticky above.
You can also activate an alternative hooking method in the vorpX config app. Caveat: only use this method in case of problems with a game. It is not meant for general use.