Forum Replies Created
-
Posts
-
Can’t replicate your issue here, neither with default settings nor with the ‘High FOV’ user settings from the cloud. The screenshot below is vorpX 19.2.2.1 with the ‘High FOV’ user preset. Looks perfectly fine to me, nothing glitchy around the ball at all as far as I can tell.
Please try a factory reset (config app > trouble shooting), also set all game options to default and remove any mods you may be using.
Can’t really recommend anything else without being able to replicate the issue.
There actually was a hotkey in early vorpX versions that allowed to hide the entire HUD for full immersion in any game that had HUD shaders defined. Personally I considered that a fantastic feature as it allowed you to be fully immersed for walking around and enjoying the scenery.
the major drawback were complaints about invisible menus etc. since in the vast majority of cases the same shaders are used for both HUD and menus. Some people simply forgot that they had hidden the HUD, didn’t understand that HUD and menus technically may be the same thing or considered it to cumbersome to switch it on again when they want to use a menu etc. So in the end I decided to remove the feature.
Unfortunately you sometimes have a small percentage of people who manage to spoil something completely optional for everyone if it doesn’t work 100% perfect instead of just not using it.
Without having tried yet my guess would be that you restored the settings to default by reverting, but of course I can’t be sure. Might be worth a shot to uninstall vorpX entirely (you can keep the license information when the uninstaller asks about it) and then reinstall the latest version. That ensures that everything is at default with the newest version.
So far just a guess though, of course. As said above I’ll take a look at it and let you know.
If you are using any additional software to measure your performance, first and foremost please remove it. Such software also hooks into games like vorpX and in the worst case might actually cause your issue. vorpX has a built in FPS counter (ALT+F). Also disable/uninstall any other background program that might hook into games, e.g. anything that can show notifications ingame.
If you are using any other antivirus than Windows Defender, please also try to disable/uninstall that for testing purposes. Just in case. Some AV programs may constantly scan your PC’s memory in a way that potentially causes all sorts of problems with a program like vorpX.
If you can’t identify any external issue, it might also be that the DX11 games you are using are just way more demanding than the DX9 games you tried. If that’s the case, you can do several things to improve performance: mainly reducing graphics detail settings, reducing the game resolution or switching to Z3D. Some additional options to enhance performance are listed in the performance guide in the vorpX help.
No changes whatsoever to the Rocket League profile. There was another report regarding an outline around the ball two or three weeks ago though. If such glitches appear seemingly out of nowhere it’s typically a game update that breaks shader definitions. Not sure whether I would call something like that ‘unplayable’ :), but I’ll take a look at it.
Please also always try the official profile with default settings if you suddenly encounter a glitch that didn’t exist beore, just in case the glitch is somehow triggered by the custom settings you are using.
Shouldn’t be an issue, tried that in the meantime using the latest version of the mod (0.83 I think) since I suspected the same.
Maybe you need to update the mod and/or make sure to use the latest openvr_api.dll the mod author links on the website.
If you use the VR controllers in gamepad mode, change the gamepad sensitivity in the game just like you would do with an actual gamepad.
Sensitivity settings in vorpX only are used (make sense) when vorpX emulates a mouse since in that case changing the mouse sensitivity in the game may affect head tracking, so it’s better to have a dedicated setting in vorpX here.
If you have further questions, no more answers until tomorrow, sorry. I’ll be offline for the meager rest of my Sunday.
The sensitivity settings only are visible with ‘Gamepad Override’ on since they don’t have any effect otherwise. If you use a game’s native gamepad mode, change the sensitivity in the game.
Just in case: settings on this page are related to actual gamepads. If you are playing with VR controllers, the sensitivity settings to use are the ones on the vr controller page in the menu.
BTW: Might be unrelated to the Witcher 1, but important: whenever you encounter a profile where ‘Gamepad Override’ is set to anything else than off per default, do not change it. There always is a reason for the gamepad override being enabled. Usually such games don’t allow gamepad and mouse to be used together. At least for official profiles leave the override at the default value. Unless I made a mistake (not totally impossible of course) the default is always the best value.
1. The gamepad sensitiviy settings are on the input page of the ingame menu.
2. Use ‘Z3D Normal’ and try different 3D-Strength values. Z3D however will not give you a 100% correct scale impression usually due to the way it works. Only G3D works like 3D works in reality. Your brain will adapt though.
3. Just in case you missed it: there is a tooltip shown on the bottom of the settings window for most settings.
A little warning: Don’t tweak too much. There are so many settings that it’s fairly easy to break something. Take any potential warnings VERY seriously that may get shown when you change some some settings. If in doubt you can restore profile defaults in the config app.
Please reinstall vorpX manually. I lowered the grip action threshold a bit again to better account for controllers that might not work as expected. There are far too many settings already, so no more settings unless unavoidable.
I’ll check your swap issue later. Now it’s Sunday for me too. :) Can’t remember to have changed anything in that regard. For now please leave it on, controls usually make more sense that way anyway, hence it is on per default. If you absolutely need to swap the buttons back, you probably can do it in the game options for now.
Comparing the single core performance of your CPU with the single core performance of a Ryzen 3000 on userbenchmark.com should give you a decent impression of what to expect.
Don’t expect anyone to do extensive benchmarks for you, the CPU is so new that I would consider it rather unlikely to find someone willing to do that. I would, but I also don’t have one here. Also the situation will differ so much from game to game that a general comparison is the best indicator you can get anyway.
USUAL STAR CITIZEN DISCLAIMER (forgot that above): As suggested by the message on start the game is not officially supported by vorpX due to its alpha state. The profile is merely provided for those who like to experiment.
That said:
You might be able to set the FOV manually to higher values using a user.cfg file in your SC directory. Not sure whether that still works, but it did in the past.
Check the guide linked below for where to put the user.cfg, the variable to set would be cl_fov (provided it still works), e.g. cl_fov = 100.
Assuming SC means Star Citizen, you can adjust the game’s field of view in its graphics options instead of using vorpX’s image zoom. Or use a combination of both in case the max. allowed FOV is not enough (haven’t checked the game in a while so I’m not sure).
With a recent i7-9700K for example you may see a ~30% improvement coming from your 4-core i5-4670K in the best case. Maybe a bit more with highly multithreaded games since vorpX likes to have 1-2 cores for itself. Best case means entirely CPU limited games here. Not all games are CPU limited though, if the GPU is the limiting factor in a game, a CPU upgrade does nothing.
With Geometry 3D the probability of a game being CPU limited is relatively high with vorpX though due to the stereo rendering, higher than for monitor gaming.
The most important aspect is the single core speed here since vorpX with Geometry 3D puts a lot of stress on the rendering thread of a game. More cores also will help coming from a 4-core i5, but not as much as raw single core speed. Sadly single core CPU performance doesn’t improve as much anymore these days as it did in the past.
In a nutshell:
The ideal vorpX CPU has 6+ (virtual) cores with high single core performance. You can compare CPUs on userbechmark.com.
https://cpu.userbenchmark.com/Compare/Intel-Core-i7-9700K-vs-Intel-Core-i5-4670K/4030vs1538
No issues with the Lenovo WMR headset in GTA V here. I don’t have an Odyssey+ here, but there shouldn’t really be any difference between WMR headsets controller wise.
In case you use any mods, please try unmodded.
Please also try to reinstall vorpX, just in case the controller definitions are missing.
Last but not least check whether SteamVR is up-to-date. Should be version 1.5.16 as of today.