Search Results for 'update'

[FireBurst]

jazbanter wrote:

Ralf: Huge thanks the recent updates! The virtual monitor capability alone is a game changer and I’m amazed how well it works for new titles that refuse to latch (e.g. ARC Raiders) and old titles that have ceased to latch over time (e.g. KCD II).

Any chance you could add an option to specify the width of the virtual screen without fixed ratio restrictions? 4096 x 2160 is my go to, 5120 x 2160 at 21:9 is as close as I can get now without sacrificing height, and it’s a tad too much for my rig.

Thanks!
jaz

are you saying the latest vorpx version supports Arc Raiders? I don’t see the game in supported games list on the website

[pokkla]

Thanks Ralf, I’ll unblock updates and look forward to the next version.

PS. And, yes, you are correct. With v21 I had to make significant updates to the profile to make it enjoyable. Going forward, I’ll probably just use your default v25.x.x FONV profile to move forward.

[pokkla]

Update: For what it’s worth, I was able to downgrade vorpX from v25.1.4 to v21.3.5. With that, the “ESC” and “E” keys worked fine. It took a bit of thinking to block the update calls so v21.3.5 wouldn’t get overwritten, but it does work. I’m working on a version swapping program so I can keep v25.1.4 from my other games.

If anyone has ideas on why E and ESC don’t work in v25, let me know.

[flobv]

Hello,

Any updates on this beautiful game profile ?

Thank you!

[Cer]

Thank you for your opinion. It seems I better stay with Win10. I have the free extended security updates and end of next year I could buy 0patch to still e on the save side.
But I will also watch out for the new steam-VR headset comming soon. If this is better than the HP Reverb G2, I probaly switch and then can also go to Win11.

[Boblekobold]

Cer wrote:

Oasis?
Is it a way to run WMR headsets with Win11 ??
So far I stick to Win10 just because WMR is not available with Win11.

I don’t think it’s as good as WMR/OpenXR (probably not as optimized and reliable).
You can use Win11, but only if you don’t update it, so It may be easier to stick to Win10 (I don’t know if you can prevent the update when you do a new installation).

[Cer]

Updated today and tryied Desktop Viewer + Virtual Monitor.
Found that it doesn’t work as expected and returned to play without virtual monitor.

Issue:
Playing with HP Reverb G2. Virtual Monitor suggest default resolution of 2560×1440 (which is for some reson default), but I changed it to 3440×1440 as I want to play with 21:10 so I can turn my head a bit without seeing the edge.

I started Ratched&Clank Rift Apart and got a condesed picture. The screen is 3440 wide, but I had black vertical bars left and right. The visible picture is probably 2560 wide, but contains all 3440 pixels, which looked ugly. In addition the tilt settings of the screen didn’t seem to have an effect.
This issue stayed even after switching of virtual monitor by using “Enable virtual monitor” option of the icon in the tray (why is it called “Enable” when it switches off??). Anyway, games played on my main real monitor, but picture was still bad.

Then I disabled virtual monitor in the VorpX Config, restarted VorpX and could play again with full 3440×1440 resolution and correct screen tilt.

Hope you understood what I am writing here and can fix this issue so I can use virtual monitor.

[Benedict81]

Happy to report that the latest update made everything look better! At least with my Pimax headsets there has been some problems (aliasing and such) and now it is gone. Also the expert setting that allows user to choose the sampling setting is great, can fix some problems with high sharpening and lower resolutions (patterns on uniformly colored areas, sky etc, choosing linear fixes those, bicubic seems too ‘soft’).

[Ralf]

25/12/20 | vorpX 25.1.4 has been released

This maintenance update mainly focuses on an annoyance affecting mouse/keyboard players in some games that upscale the image to the monitor size. Under certain circumstances that can lead to vorpX’s stereo cursor being shown at a wrong position, making it difficult to hit buttons in menus etc. Various reasons for this super annoying glitch are now covered. The remaining will follow later.

Apart from that there have been a few more fixes and a new profile for Farming Simulator 2025 with automatic FOV and a scalable HUD.

Click here for a list of noteworthy changes

• vorpX: Improved stereo cursor rendering in games that upscale their output.
• vorpX: Z3D could break in some games after taking off the headset.
• vorpX: some games could crash with Windows display scaling set to 150/175.
• vorpX: some games could crash on audio device change (25.1.3 regression)
• Farming Simulator 2025: new profile with HUD scaling and DirectVR FOV.
• Farming Simulator 2022: DirectVR FOV update.
• Fallout 4: DirectVR FOV scan was broken after a game update.

[sylvan]

HELLO, is this a coincidence: but since the new update, Jedi Survivor and Dead Rising 2 no longer support VorpX?

[Ralf]

Can’t replicate that. Just checked to be extra sure.

Please try a full factory reset in the config app on the trouble shooting page.

25.1.3 in fact comes with a vital improvement specifically for ESO: a game specific shader parser that should prevent the black screen on launch after almost every game update until the profile gets updated.

[Ralf]

25/12/16 | vorpX 25.1.3 has been released

Another maintenance update, mainly addressing various issues and annoyances that came up since 25.1.2. Aside from the fixes there is a subtle improvement in regard to how the game/desktop images are sampled before sending them to the headset. Power users can also configure the sampling method now with expert settings enabled.

Click here for a list of noteworthy changes

• vorpX: Battlefield 2 could crash on map load.
• vorpX: some games could crash on CPUs with more than 12 cores.
• vorpX: different image sampling methods for screen/FullVR modes.
• vorpX: image sampling method user selectable (expert setting).
• vorpX: option to improve FPS in games that limit core count (e.g. Witcher 1 GOG).
• vorpX: back to OpenXR 1.0 due to outdated runtimes (eg. Valve, Virtual Desktop).
• vorpX: relaunching games with another graphics API could fail.
• vorpX: DX9: (rare) 64-bit DX9 games ran at roughly half the supposed FPS on Win11.
• vorpX: DX9: some FPS lost since quite a while have been reclaimed (eg. Skyrim).
• vorpX: DX11: Z3D did not work anymore in several games (e.g. COD Black Ops III).
• vorpX: DX12: fixed an (currently unused) Z3D method that didn’t work at all.
• vorpControl: hook helper install auto API detection didn’t work anymore.
• vorpControl: creating desktop shortcuts did not always work anymore.
• vorpService: fallback for virtual display/desktop viewer not working on some PCs.
• vorpService: The virtual display didn’t always get disabled on standby as intended.
• vorpService: Quest Link detection not working anymore after a recent Link update.
• Just Cause 3: depth buffer detection could fail occasionally.
• The Witcher 3: DirectVR: camera position was broken, second position added.
• The Witcher 3: DirectVR: auto EdgePeek for menus, cutscenes etc. didn’t work.
• Elder Scrolls Online: shader parser to detect future UI changes automatically.
• F1 2019: restarting with DX11 didn’t work anymore.
• F1 2020: restarting with DX11 didn’t work anymore.

[kerekeslaszlo]

I understand that this is beneficial in normal VR games, but in VorpX it’s extremely distracting.
I’ve been trying to solve this issue for 5 days now, but nothing has worked.

What I’ve tried so far:

All settings that are in vorpx

Quest 3 settings “lying down mode”

ALVR + SteamVR + lying down mode

Virtual Desktop

OpenVR-AdvancedSettings + SteamVR

Unfortunately, none of these could lower the screen offset enough to get the crosshair centered.
It seems that in VorpX Full VR mode the screen attachment to the camera is hard-coded, so no external offset can modify it.

I’m running out of ideas at this point.

If you could add a screen height adjustment option in Full VR mode in a future update, that would perfectly solve the problem.

Thank you!

[Anatolij]

Thank you very much Ralf, for your reply and support. Please don’t think I don’t appreciate your efforts and the fact that you constantly update the program. However, I personally have had very bad luck with these updates, and this isn’t the first time the updated VorpX has performed worse than previous versions. The problem is truly strange. Games like The Witcher 1.2 have worse performance than, say, Lust From Beyond (I recently played it), which is also rendered in G3D. In this game, with its very capricious and unoptimized engine (Unity 5), Lust From Beyond runs at a stable 80-90 frames per second almost all the time. But when I decided to try Lust From Beyond on the previous versions 21.3.5 and 24.1.0, the performance also surprised me. The FPS barely dropped, remaining at a stable 90 frames per second almost all the time, even at maximum graphics settings and a resolution of 2880×2160.

Could you be more specific about where I can get these log files (system information) ? I’m just not sure what data you need. A screenshot, if possible. I’ll try to send them to you; maybe it will help solve my problem.

[Boblekobold]

When you download a profile in the Cloud Profiles section, there are instructions next to it (you can also see them by clicking “Edit Profile Properties” even in the Local Profiles section)
Concerning this game, it should tell you how to change the FOV with the console for example.

Anyway, you can usually find this information here for most games :
https://www.pcgamingwiki.com/wiki/Kingdom_Come:_Deliverance_II#Field_of_view_.28FOV.29

Or on Reddit / Steam forums.

—-

Concerning KCD2 :

But as I said, read the comments below this first video because it’s not optimal.
Update by the same person :

Another topic :
https://www.vorpx.com/forums/topic/kingdom-come-deliverance-2-2/
So you should use the Auryza profile (or maybe Starfield) and not the KCD1 profile. You may have to rename the executable in order to make sure VorpX hook with this profile, instead of using first game profile (because apparently they have the same .exe name so VorpX thinks KCD2 is KCD1)