Forum Replies Created
-
Posts
-
I don’t believe in manipulation. Motivate a bunch of people without having the extra (and probably primary) goal of gaining something from their motivation. We can discuss the matter further afterwards.
I’m notoriously unreceptive to obvious influencing attempts via affirmation too, sorry again. ;)
If I may give you a bit of unsolicited life advice: leave stuff like that to bank consultants and the likes. They have to, whether they want or not. You don’t.
I’m notoriously unreceptive to obvious influencing attempts via compliments, sorry. I might actually consider that an insult if you overdo it. ;) Don’t hold your breath in regard to The Last of Us this weekend.
Unfortunately I spent the whole week with this shitty nVidia driver bug that pretty much breaks half the DirectVR profiles. I *might* upload a beta build with the ‘The Last of Us’ profile tomorrow, but honestly can’t promise anything. Working around the nVidia bug comes first. Might not look that important to you, but is a catastrophic emergency style top priority for me…
The issue only affects certain games and most of the time you won’t notice it even if strikes. For whatever reason it prevents DLLs hooked into some games frome exiting cleanly. That’s what makes it so sneaky. It only affects the very last few seconds once you exit a game.
Both the current regular nVidia driver and the Last of Us hotfix driver come with this bug.
The biggest actual problem the bug creates as far as vorpX is concerned is that vorpX can’t save game settings on exit.
If you don’t play games where vorpX can adjust FOV or other settings automatically, you can largely ignore the issue. It will still occur, but only has minor effects due to the incomplete exit cleanup. You probably won’t notice anything. Not good, but bearable.
When you play a game where vorpX does handle settings automatically though, the effect of the bug is a lot worse, since it might prevent vorpX from applying settings changes altogether. You’d see vorpX asking for a restart over and over and again on each launch when that happens. Going back to the driver linked above will almost certainly help in that case.
Why check something yourself when you can just as well ask someone. That’s so much easier, isn’t it? ;)
vorpX is alive and welll, in this very moment it’s gaining functionality that makes it easier to use (virtual display) and seriously beefs up motion controller support (gestures).
Fourth post from the top when you asked your question:
The beta aside, you also have received several profile database updates since the last regular vorpX update, at least unless you disabled that.
That’s an error messages the SteamVR runtime relays to vorpX when it fails to initialize. Try to reset all SteamVR settings to default. If you happen to have any SteamVR plugins/tools/overlays installed, try to remove them.
I’m still not really sure what that means, sorry. Here’s how you typically use vorpX:
- Launch the Oculus PC app (download here: https://www.meta.com/de/de/quest/setup/).
- Start Oculus Link (wired or wireless is up to you) in your Quest.
- Make sure ‘Oculus’ is selected as youe headset type in the vorpX config app (‘General’ page).
- Start vorpX.
- Start a the game you want to play with vorpX (or the vorpX desktop viewer if you want to use that).
Hope that helps.
If you see this message without an error code something seriously went wrong very early on. Probably some AV scanner running amok.
Try to exclude the vorpX program folder from your AV scanner, usually that would be C:\Program Files (x86)\Animation Labs\vorpX. If that doesn’t help and you happen to use some invasive third party AV, get rid of it. Windows Defender will kick in instead. It’s on par with the more annoying third party AV apps since almost a decade while causing less false alarms.
That’s not really enough information to give any useful hint. What headset do you have? What exactly do mean by ‘try to connect my VR to vorpX’? I’m not really sure what that means.
What *exactly* does the message say? If you want me to take guess what this might be about I need the error code.
Please reset the ARMA3 profile to default and check whether you maybe have accidentally disabled automatic settings changes. If so, re-enable that. None of the issues you encounter occur with default settings under normal circumstances if you let vorpX just do its thing.
Per default the profile has Geometry 3D, a scalable HUD, 6DOF head tracking, automatic FOV adjustment, and if you enable TrackIR in the game even decoupled walk/look on top of that. In other words: there is nothing you have to change except resolution/graphics details to find your individual compromise between fidelity and performance.
Also keep an eye on any hints/messages vorpX displays in the game window and/or in the headset.
RE8 is DX12, but the vorpX profiles for 2+7 are for DX11 (incl Geometry 3D, which currently is not possible for DX12).
Signing up to the ‘dx11-no-rt’ beta in Steam will help (right click game in list, click properties, go to beta page). It’s not really a beta, but in fact the last build before they removed dx11 support a while ago.