Search Results for 'Rime'

[Reaver Shadow]

Can confirm, VDXR OpenXR Runtime in Virtual Desktop WORKS with VorpX [i.e. VorpX + Virtual Desktop(OpenXR aka VDXR)].

BUT not without hiccups/issues ;(

VorpX: v21.3.5
Oculus Quest Desktop Software: Rendering Resolution 3712 x 1888 / 90Hz
Virtual Desktop Streamer: v1.30.1 / VR Graphics Quality: Medium / 90Hz
Headset: Meta Oculus Quest 2
Game Resolution (The Witcher, Nexus Mods Collection: “best experience LOREPLAY”): 2560 x 1600 (16:10), ~55FPS (seems to be frame caped at 60, 1080p is same)

Report
– [PSA] Start VorpX after your streaming within Virtual Desktop, or VorpX tries to hook it (I know i can exclude it, but i’m lazy).
– [Minor] I have Virtual Desktops Performance Overlay on by default. As soon as it click both sticks to turn off, I lose the mouse. Found no way to get back outside of quitting everything and running again. So disable Performance Overlay prior to starting game.
– [Major] I’m not sure what to call it other then artifacts. I would have random, not sure if individual or groups, of pixels in my peripheral be sparkling/shimmer/be wrong colour briefly. At first i thought it was dead pixel, but this same behavior did not occur with AirLink, or was not apparent when running game in flat mode. ( I believe it was both the virtual screen and in the lounge.) Unfortunately, this was too distracting for me, and I when back to AirLink.

Side Experience Notes
– IMO the UI and User Experience of Virtual Desktop is levels beyond AirLink (The virtual keyboard alone in AirLink is just inconvenient/dumb).
– In my testing play the witcher, VorpX + AirLink, the combo does NOT recover AT ALL from any type of disconnect, (WIFI related, PC/VorpX error, or the WORST simply removing the headset for a washroom break. This is EXTREMELY frustrating. Where as Virtual Desktop recovered 3 out of 3 times.

Side Technical Notes
– Rendering Resolution != Game Resolution. (It’s complicated)
– As best as i can figure, in Virtual Desktop Streaming Menu (within Headset), VR Graphics Quality, is the equivalent to Oculus Quest Desktop Software Rendering Resolution.

Questions
– One thing i haven’t figured out for sure, hoping someone can verify. For Virtual Desktop flat screen/AirLink desktop/VorpX Desktop Viewer, you are simply cloning the Monitor, including the refresh rate and resolution, so they matter and should match. But when running in “VR mode”, your physical monitor res and refresh rate don’t apply. (My current theory is a sort of virtual monitor is created. Your physical monitor can display a limited portion, like reduced resolution and refresh rate, aka with safer perimeters for your physical monitor, of that virtual monitor???)

[RJK_]

Only a certain number of factory profiles change games settings for an optimized performance. User profiles mainly dont change game seetings.There is no mechanism for it. So if for axample “Bloom” is disabled, there is a reason for it. See below.

Since vorpx wants to cover a wide range of games and each game is different graphicswise, certain game settings like Bloom or other effects may be in the way when vorpx creates 3D.
So its always a good idea, when trying to find a suitable profile for a game thats not supported yet also to experiment with the games graphic settings manually. Shadows for example are a very common issue for example, especially on newer games.

Mods may work, mods may not work. There is no rule for it. Best thing is to temporarily install a mod to see if it works or not.

[nexusiceland]

This thread is your virtual portal to unravel the mysteries of game-specific settings in vorpX. Whether you’ve discovered the perfect configuration to turn a beloved game into a VR masterpiece or you’re seeking guidance on optimal settings, this is the place to be.

Share your insights, tips, and tricks for specific games, and let’s create a collaborative library of game-specific vorpX settings. Be sure to mention the game title, version, and any modifications you’ve made to enhance the VR experience. If you’ve encountered challenges along the way, fellow users might offer solutions to elevate your virtual reality gameplay.

Feel free to ask for recommendations or advice on tweaking settings for particular games. Together, we can unlock the full potential of vorpX and enhance our gaming adventures.

Remember, the more details you provide, the better—resolution, field of view, 3D strength, and any other settings you’ve experimented with. Let’s embark on this virtual journey together and make our vorpX experiences truly immersive!

[anarose192]

I hope everyone is doing well. I recently acquired vorpX and have been thoroughly enjoying the immersive experiences it provides. However, I’ve encountered a unique challenge that I’m hoping some of you might have insights on.
I’ve been trying to optimize 360-degree videos for seamless VR viewing using vorpX. While I’ve managed to get some to work effectively, I’m struggling with others. Specifically, I’m facing issues with correct mapping and depth perception.
Has anyone else experimented with this? If so, could you share your tips or any custom settings you’ve found effective? Additionally, are there any specific video formats or resolutions that tend to work better in this context?

Any advice or suggestions would be greatly appreciated. Thank you in advance for your help!

[Mazzle]

I can’t even get as far as you do. My bg3 crashes before I get a hooking message, but runs fine if I tell vorpx to not watch.

Do you run mods, specifically the native mods (like WASD or camera tweaks) or the mods that require script extender? It seems like those tools also use hooking/dll injection to do their thing. I tried disabling them, but it still crashed for me. But I did it manually — I just moved NativeMods, dwrite.dll, the modified bink and SDL.dll out of the bin directory — so perhaps I missed something.

Have you tried the beta of vorpx that has a lot of experimental new stuff in it? I’m thinking of giving that a try.

[Zel1984]

I for one did not know that it had official VR support till i saw the comment above (thanks JXJS) although it is still experimental it works fantastic with my Rift S on a 6700XT, tested some free roam, scenarios & a bit of the career mode, i think this will be my main VR racing game now, crashing in slow motion in VR feels great, i also like the direction the career mode is going in, i think that will be brilliant once it’s finished.

[Malsyste]

OK this is like the 3rd time I’m writing this response, my shit keeps getting deleted or signing out or getting marked as spam… what’s up with this message board lol.

Anyways, nice try but that doesn’t sound like real3d anymore. However for experimenting, which scripthookrdr3 needs deleting? the .dll or the .log? Im finding both.

Also for some reason, I cant even remove the official local profiles to swap with any other, how do people do that? Both remove options are grayed out on official local ones. I can only remove the imported ones form cloud. And if I cant remove, I cant reassign the .exe to a different profile.

[GoooRooo]

Hi! First of all, my best wishes goes to VorpX development team. You guys are supporting very cool tech that gets ignored by big players. I’m fan of this 3D-stereo tech since 3DVision.

I’ve bought VorpX recently to play Baldurs Gate 3 with my new XReal Air AR glasses (3840×1080 in 3D mode) while streaming via Moonlight from a gaming PC (32Gb RAM, RTX3080, i9).

I do know that SBS output (Generic 3D Display) is quite experimental, but I will still kindly ask for some assistance.

I’ve got Baldurs Gate 3 running in G3D mode with some artefacts, but Z3D seems to give no stereo effect in SBS mode at all. With G3D enabled I can start the same normally, but when loading a saved game it’s get frozen on 80% loading.

Is this something that can be fixed relatively easy?

Thank you very much for your product and support. I believe with more users of AR glasses your client base will also grow :)
Ultimately I would like to see official support for AR glasses in your software, but it’s of course up to you to decide.

[Ralf]

Please check the performance optimization section in the vorpX help if you haven’t done that already. Given that vorpX exists since 10 years you can probably imagine that you aren’t the first one with questions regarding performance. To make getting answers to these questions easier for everyone all relevant information in that respect has been compiled into an existing help section years ago.

If you still experience issues after the suggestions given there and are 100% sure that a game you are trying can run safely at >200fps monoscopic, which would be necessary to reach 90fps with G3D (including a little safety margin), check the trouble shooting guide, especially the part regarding apps that may cause a conflict by also hooking into games.

You may also want to experiment with the sync/fps limit options in the vorpX menu. If a game can’t reach your full headset FPS, reducing the FPS to half of that can enhance the perceived smoothness compared to running at an uneven fraction.

[splurk]

Hi,

Is it related to the graphics quality ? I mean have you ever tried to go low resolution low graphics just to check if you experiment this issue also ?

You can also check the VRAM available on your graphic card, with GPU-Z for instance.
Remember that in VR, you need to compute every picture 2 times, one from each eye point of view. On my RTX 3080 with 10GB, I use to reach 80 to 90% of the VRAM available, and I cannot sustain full quality everywhere. The GPU temperature also may affect the performances, as if it high, it will tend to reduce the usage to avoid damages (thermal throttle).

[splurk]

Hi all,

I’m playing Cyberpunk with the latest patches.
I have an RTX 3080, and my computer can easily sustain 45 FPS in VR with 90Hz mode on my PICO 4.

I was using Vorpx 21.3.3, and playing the game with a resolution in game of 1920×1080 with Z-normal. The 3D effect was working fine. However when I tried to add custom resolutions and go up to 2880×2160 (something close to the native resolution of my PICO 4), then the Z-normal or Z-adaptative stopped working. I experimented a little bit and found that for resolutions that higher than my native 2560×1080 screen resolution, Z-normal and Z-adapative are ineffective.

I downloaded the last beta version, and happily found that the DirectVR option is there. Unfortunetly it is not playable when turning with the mouse, both screen seems not synchronized perfectly and the screen is almost unreadable during such movement. I have looked around other topics but nothing clear appears (FPS are still 45 at 90Hz). That’s sad because the immersion is fantastic when just contemplating the world.
Ok so back to Z-normal or Z-adapative, nothing works better than the previous version. So I have to choose between being short-sighted or in a flat world.

Does anyone already noticed such behavior? Is there anything to do ?

Thanks

[dellrifter22]

It’s been months since I messed with the demo, but these are the notes from the profile I included at the time. Might need to turn off DLSS and Shadow quality to avoid weirdness in G3D.

System Shock Demo (2023)
Experimental G3D/Z3D
-use a 16:9 resolution (2560×1440)
-set FOV to max 120 in game
-turn off DLSS
-set Post Processing to Medium

*shadows cause occasional flicker. If you want to disable, open Engine.ini found in:
C:\Users\*NAME*\AppData\Local\SystemReShock\Saved\Config\WindowsNoEditor …
add lines at bottom and save:

[SystemSettings]
r.ShadowQuality=0

And yes, this was uploaded with vorpX beta, so it might not show in the cloud for non beta users, sorry.

[socode]

Okay, I think I managed to beat the flat screen. Removed the folder “Plugins” from the directory bin/x64, put a new Standalone mod and run the game, flat screen. Unpacked the archive CET to bin/x64 folder, run the game from exe, all worked. I do not know if the intermediate run between mods and CET patch makes sense, but still.

!!!WARNING!!! If you previously had another version of the game (especially portable), and now there is Steam, then after removing the portable version, be sure to clean the registry (eg through Auslogics BoostSpeed Registry Cleaner or something else), as he himself will not do it. It got to the point that the mod was installed in the wrong directory, which he showed in Explorer himself, or which I pointed him! All because of old registry keys, which led the installation of mods in the wrong place, and never mind that the game is no longer there.

Unfortunately, the game is not playable at the moment in VR for other reasons:
1) You can not choose the option of dialogue, not a hand, not a stick. Only with the keyboard or if you connect an additional gamepad from some console.
2) Performance. When you rotate your head, there is a sense of missing frames. If you move the mouse, or rotate the sticks this problem is not, all smoothly. The pulse of the game in Steam looks like this:
_||_||_||_||_
All in the green range, but with gaps. Various experiments with the game and mod settings have shown that, in general, the situation does not change globally. Different settings make the game a little less twitchy or a little more twitchy. But you can’t get rid of it completely.

There are other shortcomings, but most of them are solved by mods. Like GUI, sharp ICONS and etc.

It would be cool to see a guide on “how to set up the game with the highest possible graphics and the lowest possible lag”.))

[Ralf]

@ dellrifter: I‘ll check that tomorrow. Can‘t recall currently whether it worked at some point or whether it‘s a leftover from a failed experiment.

[dellrifter22]

Yeah, it seems that any cloud profiles created or saved while using the betas are not compatible with other version of vorpX yet. I’m guessing it’s a safeguard vorpX has when it doesn’t recognize a newer version number. But I’ll admit it is the more painful part of using the beta for me, as I can’t really upload any new cloud profiles or updates to old ones – as most can’t see or import them.

The other small annoyance is that any changes made to profile settings are automatically saved upon closing the menu, and not only upon clicking “save” or “save and close” – and therefore there is no reverting back from accidental or experimental changes. At least this was with the first beta. I admit I have not had time yet to test the newest build.