Forum Replies Created
-
Posts
-
Good to hear this info, as i’m one of those guys who got greedy for resolution and had to return my Rift S. Now i’m waiting for my HP Reverb order. :)
Ha! I came here to write a new topic with the title “Ralf, are you excited for Cyberpunk 2077?” – but i see, i’m not the first on the hype train. :)
TW3 is my GGOAT (greatest game of all time), and i tried it in Z3D and it works very very well. I figured that since CP2077 uses a new version of the same engine, it should be easy to make it run in vorpX.
Regarding the API: AFAIK the ray-tracing setting is optional, so i doubt that it will be DX12 only. CDPR, like any business, wants to maximize install base and profits, so i’m quite sure they will include a DX11 path as a minimum.
Ofc, DX12 vorpX support would be a nice thing to have, for compatibility with new games.
For what this software does, it’s really cheap. Just make sure you have a good resolution HMD, because many of those PC games have detailed graphics (especially outdoors) and they don’t work nice with a low resolution.
After trying out Crysis, i realized that the SDE is killing my immersion, and returned the Rift S. Now i have an HP Reverb on order. Mainly for VorpX use – yes, that’s how good VorpX is. :)
Yeah, i agree, that’s the reason i’ll stick with Z3D for now, for every game that uses dynamic shadows.
I tested TW3 with Rift S and i agree that the shadows have a parallax problem in G3D (like in most other games with dynamic shadows, i guess).
But! Z3D mode works very well in this game. I can highly recommend it. I could never play without shadows, it’s very immersion-breaking IMO.
Ah, i wondered why my audio didn’t switch, even though it was set in the settings.
That reminds me: Is Oculus Tray Tool (OTT) compatible with vorpX? It does have auto switching for the audio path when it detects that the headset is used.
Yes, security concerns were the main reason for using a restricted account. Especially after hearing people often saying “don’t ever use an admin account with Windows”. But i could never find good info about this.
I guess it’s time to go back to my normal account. :)
I figured out what the problem is. The above problem only occurs if i try to run this combo on a non-admin Windows 10 account.
As soon as i switch to an admin account, the problem is gone. I finally managed to try out Witcher 1! Didn’t test with SteamVR, but it’s probably the same.
I don’t know why this happens, but i think it shouldn’t. I wonder if i’m the only one who uses a non-default (non-admin) account in Win10, so i’m the first to notice? My Windows install and those accounts are fresh, so we are not talking about a corrupted system here.
Any thoughts, Ralf? And maybe the possibility for a fix? For now i’m glad that i can switch the account and still play, but it’s not the cleanest solution. :)
Thanks for the heads-up. I’m aware of that, but the firewall control usually notifies me if something new occurs. It’s not 100% reliable, i think – i remember having exactly the problem you mentioned. I’ll look into it further.
Tomorrow i’ll try vorpX with Witcher 1 on my new install, and i’ll update my other post.
Good news, Ralf! On a fresh Win10 install Desktop Viewer runs fine, even with the gamma loader and custom ICC profile (vorpX required a new install key, though :). No problems with crazy head tracking either. And, even though i did not test it yet, probably the init errors are gone as well.
Looks like i’m gonna trash this installation and use the new one, and re-install all my software carefully, one by one, with frequent vorpX checks and system backups.
This is all very strange, because i know what i’m doing with my Windows, and usually don’t have problems like this.
BTW, is there a possibility to use the Touch controllers to click into the vorpX “in-game” menu? I can move the cursor with the thumbsticks and the shortcuts seem to work, but the emulated mouse buttons don’t “click” on the menu buttons.
Well, if really *everything* fails, i’ll take your offer, of course. I really appreciate your help. But i’ve bought a Rift S mainly for vorpX use, with the intention to completely change the way i play games. I will not accept that easily that my dream is shattered. I’m not giving up. After all, it works for everybody else.
Another nVidia driver did not fix the gamma mismatch, so next on the table is a fresh Win10 install. This could take a bit more time, but i’ll get back to you soon.