Forum Replies Created
-
Posts
-
That looks strange indeed, especially that it affects the actual game and not just the image in the headset. Maybe some kind of GPU memory problem because of the high Reverb resolution. Just a guess though.
A Lenovo WMR headset works perfectly fine here with Rocket League (just checked), so all I have are a few generic recommendations:
- Run the game without using the vorpX desktop viewer
- Run the game windowed
- Run the game with a common resolution (e.g. 1920×1080)
- Check (and potentially reduce) your super sampling settings in SteamVR
- Reset all game settings to default (especially video/graphics settings)
- Reset the vorpX profile to default (config app)
- Reset your graphics driver 3D settings to default
- Make sure Windows, WMR, SteamVR and your graphics driver are up-to-date.
That’s pretty much all I can think of you might want to try.
If the issue persists after checking everything above, it would also be great if you could send me a trouble shoot data archive to support |at| vorpx com, so I could check the final render resolutions used by vorpX. You can create one in the config app.
Difficult to say anything useful to this. I don’t really have a clear idea what exactly you mean. WMR in general works fine, for vorpX WMR headsets are just SteamVR headsets like any other SteamVR headset. I usually have the WMR software running first when working with WMR and start SteamVR afterwards.
I can’t really recommend anything else than I recommended above already, sorry again.
You can use vorpX like described above without the config app, even if that obviously is not ideal. All official profiles are already stored in your local database. Including F1 2018 if that helps.
Otherwise you might want to consider a Windows reinstall to fix the DortNet issue. IIRC that helped the guy in the other thread you posted in.
One more thing: If you use anything else than Windows Defender, please also try to disable/uninstall your AV program.
If you have set the game to DX11 already, there might be something on your PC preventing vorpX from hooking it. Please check the trouble shooting guide for more detailed information in this regard. It lists various potential candidates and a few less common issues that may also lead to hooking problems. You can find it either in the vorpX help or here.
That’s what the installer might say. But the error message you posted above says that v4.0.30319 is active on your machine.
Please try the DotNet repair tool I linked above. Otherwise I can’t really recommend much, sorry.
To access the config app you need to fix your broken DotNet install.
The currently active DotNet version on your PC is v4.0.30319, vorpX requires 4.6.2 or higher.
you don’t need cloud profiles. All official profiles are already included.
To access the config app you need to fix your DotNet install.
Your error message says something else. Looks like your DotNet install is messed up
Application: vorpConfig.exe
Framework Version: v4.0.30319Try the DotNet Repair tool, maybe it helps
https://www.microsoft.com/en-us/download/details.aspx?id=30135Alternatively you can use vorpX without the config app, the only thing that strictly has to be set up with the config app is the headset type. To do that mannually:
1. Navigate to C:\ProgramData\Animation Labs\vorpX
2. Open vorpX.ini with an editor
3. Set sDeviceIniName like described below.For all SteamVR headsets (Vive, WMR, Pimax etc): sDeviceIniName=HTCViveCV1
For Oculus headsets: sDeviceIniName=OculusRiftCV1If you can’t see the C:\ProgramData folder, enable ‘Show hidden files’ in the Windows Explorer options.
Please make sure that you have DotNet 4.6.2 installed. Normally the installer should do that automatically.
https://www.microsoft.com/en-us/download/details.aspx?id=53344
BTW: If you are still on Windows 7 (a 10 years old OS), consider switching to Windows 10. Windows 10 has numerous advantages for VR.
Profile is available in the cloud as ‘Resident Evil 2 [vorpX]’. Make sure to check the hints in the top left corner of the game window. The required .ini edit will be done by DirectVR with the next vorpX version, for now you have to do it manually.
The profile defaults to Immersive Screen Mode, supports both G3D and Z3D, also a scalable 3D HUD is available. Pretty much everything that makes sense for a third person game.
G3D looks flawless (checked in the police station), a fast machine is recommended.
Head tracking is off per default for now, didn’t have time yet to check whether that would introduce any issues with the gamepad. Probably it won’t, set the head tracking multiplier to 0.3 in the vorpX menu if you want to try.
@ Du1g0 : That hint was pure gold! I spent hours with this thing shortly after release without getting anywhere…
Don’t get overly excited yet, but if all goes well I *might* have a working profile later today.
The Oculus Home always appears when you put on your headset without a VR app running. That’s perfectly normal, there is no (official) to way to disable it. Games with vorpX should launch despite that.
The most likely cause of injection issues with multiple games is a conflict with some other software on your PC. If you haven’t done so already, please check the trouble shooting guide. It lists a few typical candidates and also some potential other issues that may lead to vorpX not working.
IIRC the shader used for the HUD is also used for other elements in the scene, so the the HUD couldn’t be separated from the 3D scene properly. It’s been a while since the profile was done though and there are additional heuristics options now, maybe there is way to do it now. I’ll check it again on occasion, but no promises.
If you are playing in immersive screen/cinema mode, changing the ‘Focal Offset’ option carefully! (read: very carefully) may help. Doesn’t have to though and may break other things.
The option is probably invisible per default, to see it enable ‘Expert Settings’ in the config app.