Search Results for 'Far Cry 3'

[Boblekobold]

There is already a topic with a lot of them :

Geometry VR Game List.

You can check engines&games here :
https://rjkole.com/gamestuff/engines/index.php

Or looking for the game on the forum.

Or just trying it (the only way to be sure).

From my personnal experience, best profiles are :
Originals Bioshock 1&2&Infinite
Originals Metro (I tried 2033 it has perfect G3D and 6dof) and Redux versions (I tried Last Light Redux and it was perfect but I recommand a top end graphic card with this Redux version, without even knowing if it’s better than standard)
The ascent (and some others Unreal Engine 4 games) works well.
Black Mesa (&Xen), probably Portal and Dark Messiah.
People say Dishonored, Titanfall 2, F.E.A.R, Mirror’s Edge, Fallout 3, etc. works well.
Probably Clive Barker’s Jericho & Undying too.
Originals Stalker works with good G3D but without adavanced lighting (DX9 only).

Kingdom Come Deliverance, Metro Exodus and Farcry Primal works well enough (and so probably Cry Engine games like Prey 2017 / Crysis 1-3, and Snowdrop Engine games like Facry 2-5)

Even if concerning Metro Exodus, I prefer Z3D during most of the game (except bunkers&spiders which are great in G3D) in order to have raytracing, at least on Reverb G2 (no compression, so it’s stunning).

Some Z3D profiles are very close to G3D (Atomic Heart, Frontier Of Pandora, Unreal Engine 5 games seems to work great from my experience).

I may be wrong, but I think most DX9 games probably have perfect G3D, and some DX11 games too.

[GreenThumbFoodie]

Just wanted to say thank you Ralf. I’m a first time user with a backlog of so many games. I wanted to find a reliable way to port games to VR that are not using the UEVR model. I had a slight hiccup yesterday so today I followed your tech support suggestions: turn off Steam Overlay (inc FPS counter), wallpaper engine, nvidia app, and others. It hooked and now I’m in the Himalayas enjoying FarCry 4 in VR. I can already tell that the image rendering is way better than other mods for this game (the one that recently was removed).

Specs:
Far Cry 4
16:9
2560×1440

Vorpx set at standard profile. I can’t believe I can even play in the VR controller!!!

Pimax Crystal Light
Steam Frame set at 50% per eye (still plenty)

PC
7800X3D, 5070TI, 64 GB DDRA5 RAM

Well, I’m excited to play my backlog in VR now.

[Boblekobold]

I just tried the official profile with V24 (I wanted to do it for years and someone just posted about it).

The beginning with the mammoths was very impressive, as expected :)

I played in Full VR G3D with 3840×2880 4:3 resolution and max graphics. 100° (/120°) FOV in the game’s settings (on Reverb G2) and I used this mod to set the weapon FOV to 110° :
https://www.nexusmods.com/farcryprimal/mods/21?tab=description

No problem to hook, even with Virtual Monitor. It worked instantly.

Z3D worked for me when I relaunched the game (not the first time). It’s not the best Z3D I have seen in Vorpx, neither the worse.
G3D is great, but I have indeed shadows glitches in a lot of areas and I agree it hurts eyes a bit sometimes (maybe I could get used to it but a fix would be great).
You can disable G3D shadows in VorpX’s menu (and lower gamma in this case), and it seems to work perfectly but it’s also a bit less beautiful.

Using the lowest shadow parameter (in game’s settings) doesn’t affect graphics a lot (trust me, I usually don’t lower graphics) and it solves most of the G3D shadows problems (at least they are a lot less noticeable). These are probably the most beautiful and impressive settings I tried (but it’s a bit less comfortable than perfect profiles like Bioshock, Metro 2033, etc.)
A G3D shadow fix would still be great (but I guess it’s hard to do).

I would recommand switching between options (you can do it instantly) depending on the area / situation.

I disabled most “auto” options and played with high resolution so maybe I broke something and it’s possible to get a better result.

I was able to resize HUD in both Z3D and G3D modes (at least after switching to Z3D one time). I used max ClarityFX, sharpness and texture enhancement (and low gamma) in VorpX.

Too bad I already finished this wonderful game years ago and I lack spare time, but it’s quite incredible in VR.

[Ralf]

26/01/13 | vorpX 25.1.5 has been released

Another maintenance update. Addresses a couple of input glitches, comes with a rewritten host-exit that better handles exit crashes with Meta’s OpenXR since a recent Meta Link update, makes alternative hooking usable for more games, fixes a rare DX9 issue, has a bunch of profile fixes/updates and more.

Click here for a list of noteworthy changes

• vorpX: keys wrongly blocked in some DirectInput games (e.g. Fallout 3/NV).
• vorpX: the tracking center hotkey also ensures foreground and input focus.
• vorpX: ALT+TAB and back could occasionally confuse key state tracking.
• vorpX: fixed cursor clipping in some older games (e.g. Metro 2033).
• vorpX: headset audio device switching did not work anymore.
• vorpX: D3D9: better unhooked surfaces handling, e.g. Venetica ALT+TAB crash.
• vorpX: improved host exit, cleaner in various games and with Meta OpenXR.
• vorpControl: folder exclude handles symlinks (e.g. latest EA Desktop).
• vorpControl: minimize runtime windows option supports latest Quest Link.
• vorpControl: alternative hooking working for more games.
• Cyberpunk 2077: improved sync between mod-portion and vorpX.
• Tron 2.0: .ini changes weren’t applied anymore since a while.
• Dishonored 2: scalable HUD added.
• Dragon Age Origins: deal with GOG version 2-core lock.
• Dragon Age II: deal with GOG version 2-core lock.
• Farming Simulator 25: Fixed a Z3D issue related to vehicle mirror count.

---

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.

---

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.

---

25/09/12 | vorpX 25.1.2 has been released

Another maintenance update with about a dozen noteworthy changes and fixes.

Click here for all changes

• Head tracking mouse emulation did not work anymore in desktop viewer.
• Messages shown in some games on start could become unresponsive.
• Mod component install with the virtual display failed due to an unclickable prompt.
• Some games did not exit cleanly since vorpX 25.1.0.
• Workaround for 32-bit games that use too much RAM on CPUs with many cores.
• Potential workaround for old games that assign small stack sizes (untested).
• In games with .ini and mem-scan FOV, ini-controls weren’t shown before scanning.
• Avoid more annoying virtual monitor related Quest Link self-restarts.
• Communication between the service and 32-bit vorpControl was broken.
• The service could use an entire CPU core after lock/unlock, standby/resume etc.
• Custom sync selection in the vorpX menu selected different options than shown.
• Trouble shoot data now includes all relevant log files.
• Better service handling in the installer.
• Elder Scrolls Online: HUD shaders updated (again).
• Cyberpunk 2077: mod components updated for CP2077 2.31
• As always numerous smaller fixes and optimizations.

---

25/08/30 | vorpX 25.1.1 has been released

This maintenance update brings some OpenXR improvements, carves out more precious GPU memory, enhances Quest controller support with SteamVR and fixes a bug where Z3D became heavily pixelated after switching 3D modes.

Auto-updating from 24.1.0 and 25.1.0 will likely fail (sorry!), you may have to reinstall manually with your web installer. If you didn’t keep it, you can get one here: click

Click here for all changes

• GPU memory usage reduction due to headset sync optimizations, ~150 MB at 4K.
• Auto judder protection when a VR runtime throttles the headset framerate.
• Rendering the start room could produce glitches/DX errors.
• DX11/DX12 Z3D could become heavily pixelated/after switching 3D modes.
• SteamVR: emulated start/back gamepad buttons on Quest controllers now working.
• OpenXR: deal with outdated OpenXR runtimes (e.g. Valve, WMR)
• OpenXR: VR controllers were rendered upside down since an OpenXR lib update.
• OpenXR: resetting the renderer in case of an error could cause a crash.
• OpenXR: head rotation felt wobbly in immersive screen/cinema mode.
• OpenXR: don’t use Valve’s broken OpenXR, use SteamVR if set as OpenXR runtime.
• OpenXR: auto switch to Quest Link or SteamVR if no active OpenXR runtime is set.

---

25/08/28 | vorpX 25.1.0 has been released

This update reunites the regular and the ‘cutting edge’ branches. For those who until now used the regular version it brings three major new features: motion controller gestures, a rewritten desktop viewer and a virtual monitor.

Those who already used the cutting edge build can skip to the full changelog at the bottom of this post to check what has changed since then.

Motion Controller Gestures

You can now map predefined motion controller gestures to key presses and gamepad actions. Aminig down sights, reloading, melee combat, steering wheels and a lot more gestures are available to turn flat games into more immersive VR experiences. While not every game benefits from gestures in the same manner, some (e.g. first person shooter games) can actually feel close to native VR that way. Even seated just a handful of gestures can tremendously improve immersion compared to playing with a gamepad or mouse/keyboard.

Various profiles already have gestures predefined, try e.g. Cyberpunk 2077, Starfield, Titanfall 2 or Aliens Colonial Marines. More will follow. For other games you can easily define gestures yourself. Be amazed how easy that is and how well it can work. Check the video below for a brief introduction.

Desktop Viewer Rewrite

The rewritten desktop viewer now handles high GPU load a lot more stable and also addresses a bunch of annoyances the old desktop viewer had, e.g. the inability to display Windows admin rights prompts.

If vorpX can’t hook a game, try the new desktop viewer. Especially in tandem with the third new feature the vorpX desktop viewer now is the ultimate VR flat game cinema.

Virtual Monitor

The new virtual monitor finally makes running games at higher resolution than your actual monitor allows a breeze. All important resolutions are predefined, and you can easily add more if you want in the config app.

Added benefit for desktop capturing and playing games unhooked with the desktop viewer: the virtual monitor always runs at the refresh rate of your headset, which removes any form of micro stutter that normally is the result of capturing e.g. a 60Hz monitor and displaying it on a 90Hz headset.

The easiest way of using the virtual monitor is launching the vorpX desktop viewer and putting on your headset. Per default vorpX will then switch to its virtual monitor.

Full Changelog

Biggest changes from official (21.3.5) to last cutting edge build (24.1.0)

• Motion Controller gestures that easily let you map VR controller gestures to key/button presses. vorpX gaming as close to native VR as never before.
• A virtual monitor has been added that lets you play games at arbitrarily high resolutions and always has the exact same refresh rate as your headset, which is especially great in cunjunction with the desktop viewer. The smoothest VR desktop experience ever.
• Desktop viewer rewritten to minimize CPU/GPU usage, get rid of a few annoyances, and work great with the new virtual monitor.

Biggest changes since 24.1.0

• Redesigned rendering/post-fx pipeline that significantly reduces the amount of GPU memory used by vorpX at high resolutions.
• Custom memory manager that keeps memory allocated by vorpX separated from game memory as much as possible. Improves general stability everywhere, most notably when using high resolutions with some 32-bit games, e.g. Dragon Age Origins, Venetica.
• Special treatment for 32-bit games able to handle more RAM than the usual 32-bit 2GB limit. vorpX can now detect and directly utilize the extra memory. If you encounter crashes with 32-bit games at high resolutions, check the internet for tools that make them ‘large address aware’. Note that trying that with modern 64-bit games has no effect, those can use all your RAM per default.
• Major (ongoing) spring cleaning continued: lots of internal changes and refactorings that improve general stability and/or help keeping the developer of this Tower of Babel happy.

Noteworthy smaller changes/fixes since 24.1.0

• Optimized texture sharing between game and vorpX threads. Fixes DX12 black screen caused by nVidia driver 580.88+ and in general may/should be a bit smoother under high GPU load.
• Improved cursor tracking. Fixes cursor flicker e.g. in AC:Valhalla/Odyssey.
• Cinema mode uses reduced lightmap sizes in 32-bit games that aren’t large address aware to squeeze out some extra GPU RAM for higher resolutions.
• DX9: Some rarely/never encountered StateBlock related stuff handled. Just in case.
• DX9: Hooking related changes that may improve hooking reliability in some cases.
• DX9: Generic 3D/Headset modes did not work on some AMD GPUs
• DX9: Fixed an issue that could cause games to hang on device creation.
• DX9: Fixed an issue that could cause games to crash on display mode change.
• DX9: Fixed an issue that could cause games to crash on load (e.g. GTA IV).
• DX9: Fixed an issue that could cause games to hang fullscreen (e.g. Splinter Cell 3).
• DX9: The start scene had some weird render glitches in ‘Generic VR headset’ mode.
• DX10: Potential exception on init (e.g. Crysis DX10)
• DX11: Support some rarely used DX11 features (e.g. WoW non-legacy DX11)
• DX11: Improved G3D performance, up to 300%! Don’t get too excited though, that is an outlier. Usually expect anything from 0%-15%.
• DX11: More efficient multithreading. Improves FPS in some games (e.g. Elex 2).
• DX11: Image was garbled in some games, e.g. ArmaA III (24.1.0 regression).
• DX11/12: Optimized shader bookkeeping. Can save >200 MB of RAM (e.g. HZD).
• DX12: More efficient resource bookkeeping. Up to 20% better FPS (e.g. Uncharted 4).
• DX12: Fix for hiccups/uneven FPS in some games (e.g. The Last of Us/Uncharted 4).
• DX12: display mode switching/window resizing failed for some games (e.g. Far Cry 6)
• DX12: various authoring hotkeys did not work.
• Tracking: The jump/crouch detection didn’t work correctly anymore.
• vorpX control: App could crash on startup (24.1.0 regression).
• vorpX control: App could crash after installing hook helpers.
• vorpX control: App could hang after running for a while.

Game Profile Changes/Fixes since 24.1.0

• Cyberpunk 2077: support for latest game version.
• Dark Souls III: scalable HUD didn’t work under some circumstances.
• The Elder Scrolls Online: shader fixes for latest game version.
• The Witcher 3: The profile’s mod part could activate itself without vorpX running.
• World of WarCraft did not work anymore after removal of the old D3D11 renderer.
• Abzu: ini changes were applied on each launch instead of just once.
• Hellblade: ini changes were applied on each launch instead of just once.
• Observer: ini changes were applied on each launch instead of just once.
• Prey (2006): resolution wasn’t set as intended due to a typo.
• Conarium: improved DirectVR memory apply on/off check
• Deus Ex: Human Revolution: various fixes.
• The Surge: motion blur hint added.
• Morrowind: MGE shader chain could become unavailable.
• dgVoodoo2: shader parser for versions 2.7+

[Cless_Aurion]

Your comment worries me for 2 different reasons.

there is a HUGE difference between 3840p and 2160p in VorpX with my Reverb G2 in most games. You can see so much more details…it’s just incredible.

One, the G2 is a 2.1k per eye display with 24 PPD, which equals to a 900p monitor at a normal viewing distance. There you are seeing improvement when supersampling, which is a finer and less noticeable than increasing regular resolution

It has been confirmed by other people even several times on Pimax Crystal Light (2880p).

Two, to my knowledge, the HMD I’m using right now has almost double the amount of pixels than the Crystal Light, so at the very least, I should see it like that (it doesn’t look as good as a Crystal Light).

That’s definitely not normal. I don’t know exactly what you are doing, but VorpX image quality is far beyond a 4k monitor (it displays a lot more details which wouldn’t even exist on a monitor…)

Well, I wouldn’t go as far as that, since its so HMD dependant. The MeganeX8K I’m using definitely have the PPD of a 4K monitor, but we don’t have any better PPD HMD in the market currently so… :P

Maybe you don’t use VorpX as intended.

Well, I use it in screen mode, which should be good enough. Going back to the desktop… the desktop should be rendered at the appropiate resolution, right now it really does look like half of my resolution is missing, easily. I can’t barely read the letters :(

I do play with the cinema-like curved display. I want to play all my games that aren’t UEVR in VorpX… but right now, the image quality is so poor I can’t, I’d just rather play on the monitor to get twice the resolution instead :(

[Boblekobold]

@ Cless_Aurion :
As I said on the other topic, you may have a problem, or unusual expectations (PPD sensitivity regardless of actual graphics quality ?)

Maybe it will be patched (if it’s a real problem).

As far as I can tell from my experience :
– PPD aside (I don’t care and I don’t even notice it), there is a HUGE difference between 3840p and 2160p in VorpX with my Reverb G2 in most games. You can see so much more details…it’s just incredible.
– as far as I know, VorpX’s image quality in most AAA games in full VR / immersive screen has no equal (UEVR is a lot worse, at least at medium/long distance, I never got the same result I can have in VorpX, and I’m not the only one). It has been confirmed by other people even several times on Pimax Crystal Light (2880p).
– In VorpX, you can see every detail miles around with a displayport VR headset like Reverb G2. Most people use a Quest 2/3 with compression and are very far to this quality anyway.
– some people used a Pimax 8k here so they would probably have noticed your problem if they had it.

About the desktop viewer, image quality seems fine if I don’t activate SBS mode and if I choose correctly the resolution. With SBS mode, it seems to be worse the only time I tried (but maybe it wasn’t VorpX’s fault because of course another 3D program was implied, and anyway it was still better than UEVR).

Cless_Aurion wrote:

This is still an issue in V24. It looks about what I could expect a 1440p HMD (like the Vive Pro/Index) to look as.

That’s definitely not normal. I don’t know exactly what you are doing, but VorpX image quality is far beyond a 4k monitor (it displays a lot more details which wouldn’t even exist on a monitor…)

It’s better than any real video I watched (including mines in 8k).

Maybe you don’t use VorpX as intended.

I personnally use it to play in full VR, or alternatively to wrap a giant hemispherical display around me (very close to full VR).

[Boblekobold]

You probably have a good sight and are probably very sensitive to PPD (you bought a 8k VR headset so it’s not surprising ;) )

Maybe there was a limit in order to optimize ?

I wonder how you can use this kind of resolutions in VorpX. We probably don’t play the same games… (Frontier Of Pandora, Metro Exodus, Atomic Heart, etc.)
Or you have a lot better graphic card.

How do you do ? Virtual Monitor is limited to 4860p as far as I know (I never tried above 3840p because I mainly play recent AAA games and even with an RTX4090 it would be hard to keep a decent framerate. I don’t know if it would be useful to me. In my opinion, 2880p is enough with a lot of old games because of textures limit, even if VorpX enhances them a lot).

Besides, I think I prefer my G2 (2160p) over my Varjo Aero (2880p but maybe there is more pixel density at the center of the fresnel lenses), and the G2 ratio is probably closer to my field of view, the way I wear these VR headsets, so I can see more details in full VR with the G2.

Curiously, I can also see more clearly the pixels on the Aero (maybe because the G2 is afocal and my sight is almost but not completely 10/10). Sometimes it’s not so good to see too clearly (but anyway I don’t concentrate on pixels during playthrough).

So I don’t think I could really see the difference, especially in game, between a 4000p VR headset and my G2. Anyway it’s still way better than a Quest 3 at medium/long distance ;)

The most important thing is the displayed image in my opinion.

Even if my Reverb G2 is 2160p and even if my sight isn’t 10/10, I can clearly see :
– the difference between 2880p, 3200p and even 3840p game resolution (but only in very recent games because as I explained it doesn’t really matter in old ones). It seems most games arent really perfect at a given resolution. You have to render them in a higher one than the displayed one.
– the difference between VorpX and UEVR clarity and sharpness.

UEVR’s sharpness & clarity isn’t even close to VorpX at medium/long distance in every AAA game with large outdoors environement I tried (even with 6000p resolution in UEVR, it’s still blurry at medium/long distance while VorpX is usually great even in 2880p). The fact I usually can use a wider FOV in VorpX may play a role but It doesn’t explain everything.

Of course VorpX handles more optimized game engines than UEVR, but even with Unreal Engine 4 VorpX is always a lot better in this case (didn’t really compare UE5 yet). I haven’t found a way to fix it yet, and I don’t think there is. I asked around me and everyone confirmed this phenomena, even on Pimax Crystal Light. It may depend on the technologies used by each game I suppose.

[jaekeau]

Yesterday I bought vorpX, first game that I wanted to try out in VR was FC3, but sadly it doesn’t seem to hook and thus fails to launch. It gets randomly stuck on “hooking to FC3” into “this takes a while” with suggested actions and then stops running, or the game stops running without those pop-up messages and after 30-60s goes directly to “failed to hook”.

– Quest 2
– Steam version, running through Ubisoft Connect
– Steam & Ubi overlays disabled
– Steam & Ubi don’t run as admin
– Tried running in DX9 & DX11 and resp. hook helpers
– Tried running vorpX as admin
– I have Far Cry 3 enabled for Large Address Aware because of the crashing problem, I haven’t tried disabling that, but I would assume that disabling the command that enables a crash-free experience would induce crashes again, thus making it a net-neutral option: it won’t make the game playable.
– No AV other than standard Windows Defender
– Tried Bioshock Infinite today and was basically a plug & play experience (Steam overlay enabled on that game btw)

Idk where to go from here sadly. Any troubleshooting tips or obvious oversights I missed?

[Nigebik]

I was able to set it up! Z3D works! I renamed the exe file of the game, and used the profile of Far cry 6 (author auryza). In the vorpx settings, you need to enable letterbox 2. Now the game works in fullVR. Thank you all for your help. I’ll try to find a way to share the finished profile later.

[Sfenj1]

Hi

I own vorpx now for a longer time.first i used it with my rtx3080 gaming laptop. after some time i made a pc build with a rtx4090. now on both devices i have some random crashes. especially in direct vr games its worse. sometimes i can play for one or two hours without any issues and sometimes it crashes every 5 minutes. i try a lot of different combination of settings and tricks but i can’t figure out why. i also have try to conntact the vorpx support but it seems to be not existing anymore.. so maybe somone in the forum can help me. below u will see my specs and the end of the log file where it crashed.

_ Operating System _______________________________________________________

Name: Microsoft Windows 11 Pro
Version: 10.0.22631
Architecture: 64-Bit
Build Number: 22631
Boot Device: \Device\HarddiskVolume1

_ Folders ________________________________________________________________

System : C:\Windows\system32
Documents: C:\Users\Pando\Documents
Local AppData: C:\Users\Pando\AppData\Local
Common AppData: C:\ProgramData
vorpX Install: C:\Program Files (x86)\Animation Labs\vorpX\
vorpX MainData: C:\ProgramData\Animation Labs\vorpX\

_ CPU ____________________________________________________________________

Name: Intel(R) Core(TM) i9-14900K
Cores: 24

_ Memory _________________________________________________________________

Name: Physikalischer Speicher
Capacity: 32768.00 MB

Name: Physikalischer Speicher
Capacity: 32768.00 MB

_ GPU ____________________________________________________________________

Name: Virtual Desktop Monitor
Device ID: VideoController1
Adapter DAC Type:
Driver Files:
Driver Version: 10.54.50.446
Video Processor:
Video Architecture: 5
Video Memory Type: 2
Name: NVIDIA GeForce RTX 4090
Device ID: VideoController2
Adapter RAM: 4095.00 MB
Adapter DAC Type: Integrated RAMDAC
Driver Files: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nvldumdx.dll
Driver Version: 32.0.15.5612
Video Processor: NVIDIA GeForce RTX 4090
Video Architecture: 5
Video Memory Type: 2

INF: ********************************************************************

INF: App: Attaching to fcprimal.exe, pid:29284 (64bit)
INF: App: cmd: “C:\Program Files (x86)\Steam\steamapps\common\Far Cry Primal\bin\FCPrimal.exe” -uplay_steam_mode
INF: App: vorpX version: vorpX 21.3.5, build time: Jul 29 2023 | 15:43:03
INF: App: max. supported profile version: 21.2.1
INF: MemScanManager: Created
INF: App: Authoring mode: 1
INF: ProgSettings: Versions: system: 0.0.0, user: 21.2.1
INF: GameHelper: Instance created
INF: App: BaseInit: crash handler set.
INF: HookBase: Installing base init hooks single-threaded
INF: HookBase: Overlay detected: gameoverlayrenderer64.dll
WRN: HookBase: Overlay already loaded on hook init: gameoverlayrenderer64.dll
INF: DXGIBase: Installing Main Hook
INF: D3D11Base: Installing Main Hook
INF: HookBase: Installing system hooks
INF: HookBase: Installing mouse hook
INF: vorpControl: Starting process life thread: proc id: 29284, hook count: 2
WRN: AudioHelper: No known VR playback device found.
INF: vorpControl: Exiting process life thread: FCPrimal.exe, 43304
INF: DXGIBase: CreateDXGIFactory1
INF: DXGIBase: Installing DXGI factory method hooks.
INF: DXGIBase: Installing DXGI factory2 method hooks.
INF: D3D11Base: CreateDevice
INF: App: Performing Hooked Init, thread id 46556
INF: App: Profile GUID: 9E1423C9-F16A-4F32-BA36-02A795708548 (official)
INF: High Performance Counter Frequency: 10000000
INF: VorpSetting: /: 0.007000
INF: VorpSetting: /: Cabin Condensed
INF: VorpSetting: /: Cabin Condensed
INF: VorpSetting: /: Arial
INF: VorpSetting: /: Wingdings
INF: VorpSetting: /: 547
INF: VorpSetting: /: 803
INF: VorpSetting: General/sDeviceIniName: SteamVR
INF: VorpSetting: Display/iAdapterIndex: -2
INF: VorpSetting: Display/bDisableDWM: false
INF: VorpSetting: GUI/bShowAdvancedParameters: true
INF: VorpSetting: GUI/bShowPosTrackingNotification: true
INF: VorpSetting: GUI/bShowStartMessage: true
INF: VorpSetting: GUI/bHideUnimportantNotifications: false
INF: VorpSetting: GUI/iGuiTexWidth: 2048
INF: VorpSetting: GUI/iGuiTexHeight: 2048
INF: VorpSetting: GUI/bShowWatermark: true
INF: VorpSetting: Audio/iAudioMode: 0
INF: VorpSetting: Input/fHtRecenterDistance: 0.799994
INF: VorpSetting: Input/iMouseWheelShift: 0
INF: VorpSetting: Input/iMouseWheelAlt: 0
INF: VorpSetting: Hooking/iHookThreadMode: 0
INF: VorpSetting: Hooking/iHookStyleDX9: 1
INF: VorpSetting: Hooking/iHookStyleDX12: 0
INF: VorpSetting: Hooking/bOverlayBlock: true
INF: VorpSetting: Hooking/sOverlays32: GameOverlayRenderer.dll##IGO32.dll##overlay.dll##overlay_mediator_Win32_Release.dll##overlay_mediator_Win32_ReleaseWithLogging.dll##EOSOVH-Win32-Shipping.dll
INF: VorpSetting: Hooking/sOverlays64: GameOverlayRenderer64.dll##igo64.dll##overlay64.dll##overlay_mediator_x64_Release.dll##overlay_mediator_x64_ReleaseWithLogging.dll##EOSOVH-Win64-Shipping.dll
INF: VorpSetting: Authoring/sAuthorCode: 0
INF: VorpSetting: Authoring/bShaderAuthoring: true
INF: VorpSetting: Authoring/sNppPath:
INF: VorpSetting: Authoring/sAuthorDataPath:
INF: VorpSetting: Authoring/bDumpShaders: false
INF: VorpSetting: Authoring/bDumpShaderBinary: false
INF: VorpSetting: Authoring/bCreateAdditionalHashes: false
INF: VorpSetting: Authoring/iAllShadersTimeRangeMs: 5000
INF: VorpSetting: Dev/bForceWindowed: false
INF: VorpSetting: Misc/bTsDisableDX9GrabberScan: false
INF: VorpSetting: Misc/bGhDisallowSettingsChanges: false
INF: VorpSetting: Misc/sSrvMonitorNamesOculus: MONITOR\NVDD
INF: VorpSetting: KeyMappings/iKeyMenu: 46
INF: VorpSetting: KeyMappings/iKeyEdgePeek: 4
INF: VorpSetting: KeyMappings/iKeyVRHotkeys: 260
INF: VorpSetting: KeyMappings/iKeyReset: 813
INF: VorpSetting: KeyMappings/iKeyCursor: 835
INF: VorpSetting: KeyMappings/iKeyStereoDisable: 856
INF: VorpSetting: KeyMappings/iKeyFovAdjust: 854
INF: VorpSetting: KeyMappings/iKeyCenterPosTracking: 800
INF: VorpSetting: KeyMappings/iKeyCenterGamepad: 544
INF: VorpSetting: KeyMappings/iKeyInfoOverlay: 838
INF: VorpSetting: KeyMappings/iKeyMagnifier: 4
INF: VorpSetting: KeyMappings/iKeyG3DZ3DSwitch: 843
INF: VorpSetting: KeyMappings/iKeyDvrScan: 844
INF: VorpSetting: KeyMappings/iKeyDvrEnable: 834
INF: VorpSetting: /: 770
INF: VorpSetting: /: 846
INF: VorpSetting: /: 857
INF: VorpSetting: /: 956
INF: VorpSetting: /: 845
INF: DeviceSetting: Hardware/sProductName: SteamVR
INF: DeviceSetting: Hardware/sFriendlyName: SteamVR (Index, Vive, Pimax)
INF: DeviceSetting: Hardware/sManufacturer: SteamVR
INF: DeviceSetting: Hardware/sModelNumber:
INF: DeviceSetting: Hardware/iType: 50
INF: DeviceSetting: Hardware/bAllowDisplayClone: false
INF: DeviceSetting: Hardware/iDesiredFps: 90
INF: DeviceSetting: Hardware/iPerformanceWarnFps: 0
INF: DeviceSetting: Hardware/iRecommendedGameResX: 1920
INF: DeviceSetting: Hardware/iRecommendedGameResY: 1080
INF: DeviceSetting: Hardware/fDisplayCamFovV: 95.000000
INF: DeviceSetting: Hardware/fPhysicalScreenWidth: 125.769997
INF: DeviceSetting: Hardware/iScreenResX: 1920
INF: DeviceSetting: Hardware/iScreenResY: 1080
INF: DeviceSetting: Hardware/fScreenAspect: 1.777774
INF: DeviceSetting: Hardware/fChromAberrationStrengthRed: 0.000000
INF: DeviceSetting: Hardware/fChromAberrationStrengthBlue: 0.000000
INF: DeviceSetting: Hardware/fMinColor: 0.000000
INF: DeviceSetting: Hardware/fIPDDefault: 64.000000
INF: DeviceSetting: Hardware/iRollMode: 1
INF: DeviceSetting: Hardware/fLensDist0C1: 1.000000
INF: DeviceSetting: Hardware/fLensDist0C2: 0.000000
INF: DeviceSetting: Hardware/fLensDist0C3: 0.000000
INF: DeviceSetting: Hardware/fLensDist0C4: 0.000000
INF: DeviceSetting: Hardware/fLensDist0Scale: 1.000000
INF: DeviceSetting: Hardware/bVerticalShiftEnable: false
INF: DeviceSetting: Hardware/bDmNewDirectModeAllow: true
INF: DeviceSetting: Hardware/bDmFluidSyncAllow: true
INF: DeviceSetting: Hardware/fDmGammaCorrection: 1.000000
INF: DeviceSetting: Hardware/iHtType: 50
INF: DeviceSetting: Hardware/bHasDeviceAudio: true
INF: DeviceSetting: Hardware/sAudioSearchNames: Index HMD|HTC-VIVE|Rift Audio|Rift S|Oculus Virtual Audio Device
INF: DeviceSetting: User/iStereoDisplayMode: 4
INF: DeviceSetting: User/iAnaglyphMode: 2
INF: DeviceSetting: User/iRenderMode: 10
INF: DeviceSetting: User/iTimewarpMode: 1
INF: DeviceSetting: User/iPrediction: 1
INF: DeviceSetting: User/fVignetteScale: 1.000000
INF: DeviceSetting: User/fUserIPD: 64.000000
INF: DeviceSetting: User/fVerticalShiftLeft: 0.000000
INF: DeviceSetting: User/fVerticalShiftRight: 0.000000
INF: DeviceSetting: User/bChromaticAberrationCorrection: true
INF: DeviceSetting: User/bMinimumColor: false
INF: DeviceSetting: User/bEnableDeviceAudio: true
INF: DeviceSetting: User/bDmNewDirectModeEnable: true
INF: DeviceSetting: User/bDmAllowWaitForDmmRender: false
INF: DeviceSetting: User/bVrApiMotionSmoothing: false
INF: DeviceSetting: User/iVrhcControllerType: 1
INF: DeviceSetting: User/bVrhcbSwapButtonsBYEnable: true
INF: TrackerSetting: Hardware/sProductName: OpenVRTracker
INF: TrackerSetting: Hardware/sFriendlyName: OpenVR Tracker
INF: TrackerSetting: Hardware/sManufacturer: OpenVR
INF: TrackerSetting: Hardware/sModelNumber:
INF: TrackerSetting: Hardware/iType: 50
INF: TrackerSetting: Hardware/bHtHasPosTracking: true
INF: TrackerSetting: Hardware/bHtUseAxisMultipliers: false
INF: TrackerSetting: Hardware/iHtAxisIndexX: 0
INF: TrackerSetting: Hardware/iHtAxisIndexY: 1
INF: TrackerSetting: Hardware/iHtAxisIndexZ: 2
INF: TrackerSetting: Hardware/fHtAxisMultX: 1.000000
INF: TrackerSetting: Hardware/fHtAxisMultY: 1.000000
INF: TrackerSetting: Hardware/fHtAxisMultZ: 1.000000
WRN: AudioHelper: No known VR playback device found.
INF: UIManager: Initialized
INF: Keyboard: Init
INF: InputManager: Initialized
INF: MemScanManager: Initialized
INF: HookBase: Installing hooked init hooks single-threaded
INF: XInputBase: Checking loaded XInput versions.
INF: XInputBase: Checking Main Hook
INF: XInputBase: Hooking xinput9_1_0.dll
INF: DirectInputBase: Checking Main DirectInput Hook
INF: DirectInputBase: DirectInput not detected, hooking delayed
INF: DirectInputBase: Checking Main DirectInput8 Hook
INF: DirectInputBase: DirectInput 8 detected.
WRN: Hook: Source module mismatch (di8_GetDeviceStateW), expected: C:\Windows\system32\dinput8.dll, actual: C:\Program Files (x86)\Steam\gameoverlayrenderer64.dll
INF: MouseKeyboardBase: Installing Main Hook
INF: OpenTrackHelper: Init
INF: SoundManager: Initialized, audio mode: 0
INF: App: Hooked Init success, thread id 46556
INF: App: Graphics API changed: DX11
INF: ProgSettings: Versions: system: 0.0.0, user: 21.2.1
INF: G3DSettings: Loading settings (18.2.0)
INF: ProgSetting User: General/sVersion: 21.2.1
INF: ProgSetting User: Image/iImageRenderQuality: 0
INF: ProgSetting User: Image/fImageZoom: 1.000000
INF: ProgSetting User: Image/fUiScale: 0.355000
INF: ProgSetting User: Image/fUiScaleHorizontal: 0.725000
INF: ProgSetting User: Image/fUiStereoOffset: 0.950000
INF: ProgSetting User: Image/bEdgePeekLockVertically: true
INF: ProgSetting User: Image/fEdgePeekScaleMin: 0.400000
INF: ProgSetting User: Image/fEdgePeekStereoMultiplier: 1.000000
INF: ProgSetting User: Image/iEdgePeekBackground: 0
INF: ProgSetting User: Image/fTextureDetailEnhance: 1.000000
INF: ProgSetting User: Image/iImageBackground: 0
INF: ProgSetting User: Image/fImageAmbienceBrightness: 1.000000
INF: ProgSetting User: Image/iAspectRatioCorrection: 2
INF: ProgSetting User: Image/fImageSharpnessV2: 1.800000
INF: ProgSetting User: Image/fImageGameGamma: 0.650000
INF: ProgSetting User: Image/fImageGameSaturation: 1.000000
INF: ProgSetting User: Image/iImageInputGeometryType: 0
INF: ProgSetting User: Image/iImageInputStereoType: 0
INF: ProgSetting User: Image/bImageInputStereoFlip: false
INF: ProgSetting User: Image/iImageInputSurroundFovH: 360
INF: ProgSetting User: Image/iImageInputSurroundFovV: 180
INF: ProgSetting User: Image/bImageInputSurroundGuessParams: false
INF: ProgSetting User: Image/iGameDisplayMode: 1
INF: ProgSetting User: Image/iVirtualScreenScene: 100
INF: ProgSetting User: Image/fVirtualScreenHtMultiplier: 0.000000
INF: ProgSetting User: Image/fVirtualScreenDistanceOffset: 0.000000
INF: ProgSetting User: Image/fVirtualScreenScale: 1.000000
INF: ProgSetting User: Image/fVirtualScreenPitch: 0.000000
INF: ProgSetting User: Image/fVirtualScreenCurvature: 1.000000
INF: ProgSetting User: Image/bVirtualScreenCurvedVertical: true
INF: ProgSetting User: Image/fVirtualScreenBrightness: 1.000000
INF: ProgSetting User: Image/fVirtualScreenEnvBrightness: 1.000000
INF: ProgSetting User: Image/fVirtualScreenEncGamma: 1.000000
INF: ProgSetting User: Image/fVirtualScreenEnvSaturation: 1.000000
INF: ProgSetting User: Image/iVirtualScreenAspect: 0
INF: ProgSetting User: Image/iVirtualScreenAntialias: 4
INF: ProgSetting User: Image/fImmersiveScreenHtMultiplier: 0.500000
INF: ProgSetting User: Image/fImmersiveScreenDistanceOffset: 0.000000
INF: ProgSetting User: Image/fImmersiveScreenScale: 1.000000
INF: ProgSetting User: Image/fImmersiveScreenPitch: 0.000000
INF: ProgSetting User: Image/fImmersiveScreenCurvature: 1.000000
INF: ProgSetting User: Image/bImmersiveScreenCurvedVertical: false
INF: ProgSetting User: Image/iImmersiveScreenBackground: 10
INF: ProgSetting User: Image/iImmersiveScreenEdgePeekBackground: 10
INF: ProgSetting User: Image/iDirectModeRenderAsyncModeNew: 0
INF: ProgSetting User: Image/bDirectModePresentOrigImage: false
INF: ProgSetting User: Image/iDirectModeRenderQuality: 1
INF: ProgSetting User: Image/bVirtualScreenMode: false
INF: ProgSetting User: Image/bVirtualScreenLockHeadTracking: true
INF: ProgSetting User: Image/bEdgePeekDisableStereo: false
INF: ProgSetting User: Input/bHtEnable: true
INF: ProgSetting User: Input/bHtRollEnable: true
INF: ProgSetting User: Input/fHtSensitivity: 1.300000
INF: ProgSetting User: Input/bHtInvertX: false
INF: ProgSetting User: Input/bHtInvertY: false
INF: ProgSetting User: Input/bHtPosTrackingEnable: false
INF: ProgSetting User: Input/bHtPosTrackingOverrideLock: false
INF: ProgSetting User: Input/fHtPosTrackingUserMultiplier: 1.000000
INF: ProgSetting User: Input/fHtG3DLatencyEnhancement: 0.000000
INF: ProgSetting User: Input/bHtCrouchJumpEnabled: false
INF: ProgSetting User: Input/fHtCrouchPosYThreshold: -0.100000
INF: ProgSetting User: Input/fHtCrouchVelocityThreshold: 0.700000
INF: ProgSetting User: Input/iHtCrouchKey: 162
INF: ProgSetting User: Input/bHtCrouchCrouchKeyIsToggle: false
INF: ProgSetting User: Input/fHtJumpPosYThreshold: 0.050000
INF: ProgSetting User: Input/fHtJumpVelocityThreshold: 1.000000
INF: ProgSetting User: Input/iHtJumpKey: 32
INF: ProgSetting User: Input/bHtOtEnable: false
INF: ProgSetting User: Input/bHtOtSupportsPosition: true
INF: ProgSetting User: Input/bHtOtSupportsRoll: true
INF: ProgSetting User: Input/bHtOtDisableMouseYawPitch: true
INF: ProgSetting User: DirectVR/bDvrEnable: true
INF: ProgSetting User: DirectVR/bDvrForceGameHelperFov: false
INF: ProgSetting User: DirectVR/fDvrFovWorldOffset: 0.000000
INF: ProgSetting User: DirectVR/fDvrFovPlayerOffset: 0.000000
INF: ProgSetting User: DirectVR/bDvrLockLookPitch: false
INF: ProgSetting User: DirectVR/bDvrPositionEnable: true
INF: ProgSetting User: DirectVR/bDvrUseCache: true
INF: ProgSetting User: GameHelper/bGhChangeSettings: false
INF: ProgSetting User: GameHelper/bGhChangeResolution: false
INF: ProgSetting User: GameHelper/bGhChangeFov: true
INF: ProgSetting User: GameHelper/bGhChangeFovRT: true
INF: ProgSetting User: WeaponHandling/iWhdMode: 1
INF: ProgSetting User: WeaponHandling/iWhdTimeout: 8
INF: ProgSetting User: WeaponHandling/fWhdTweakPosX: 0.000000
INF: ProgSetting User: WeaponHandling/fWhdTweakPosY: 0.000000
INF: ProgSetting User: WeaponHandling/fWhdTweakPosZ: 0.000000
INF: ProgSetting User: WeaponHandling/fWhdTweakSeparation: 0.000000
INF: ProgSetting User: WeaponHandling/fWhdTweakScale: 1.000000
INF: ProgSetting User: WeaponHandling/sWhdKeysVisible:
INF: ProgSetting User: WeaponHandling/sWhdKeysADS:
INF: ProgSetting User: WeaponHandling/sWhdXiButtonsVisible:
INF: ProgSetting User: WeaponHandling/sWhdXiButtonsADS:
INF: ProgSetting User: Input/bMouseDisableAcceleration: false
INF: ProgSetting User: Input/bMouseHandleCursor: true
INF: ProgSetting User: Input/bMouseForceVorpCursor: false
INF: ProgSetting User: Input/bKeyBlockAlt: true
INF: ProgSetting User: Input/bKeyBlockEdgePeek: true
INF: ProgSetting User: Input/bKeyBlockVorpX Menu: true
INF: ProgSetting User: Input/iXiOverride: 0
INF: ProgSetting User: Input/iXiOverrideDirectVR: 0
INF: ProgSetting User: Input/bXiOverridePartLeftStick: false
INF: ProgSetting User: Input/bXiOverridePartRightStick: true
INF: ProgSetting User: Input/bXiOverridePartButtons: false
INF: ProgSetting User: Input/iXiHtControllerNum: 0
INF: ProgSetting User: Input/iXiHtMode: 0
INF: ProgSetting User: Input/fXiHtDeadzoneCorrection: 0.000000
INF: ProgSetting User: Input/fXiHtSensitivityX: 1.000000
INF: ProgSetting User: Input/fXiHtSensitivityY: 1.000000
INF: ProgSetting User: Input/fGpadSensitivityLeftX: 0.150000
INF: ProgSetting User: Input/fGpadSensitivityLeftY: 0.150000
INF: ProgSetting User: Input/fGpadSensitivityRightX: 0.500000
INF: ProgSetting User: Input/fGpadSensitivityRightY: 0.100000
INF: ProgSetting User: Input/fGpadDeadzoneLeft: 0.200000
INF: ProgSetting User: Input/fGpadDeadzoneRight: 0.200000
INF: ProgSetting User: Input/iGpadWalkRunKey: 160
INF: ProgSetting User: Input/bGpadWalkRunInvert: false
INF: ProgSetting User: Input/bGpadWalkRunIsToggle: false
INF: ProgSetting User: Input/fGpadThumbStickCurve: 2
INF: ProgSetting User: Input/iGpadVorpXButtonMode: 2
INF: ProgSetting User: Input/iGpadVorpXButtonBind1: 1
INF: ProgSetting User: Input/iGpadVorpXButtonBind2: 2
INF: ProgSetting User: Input/fGpadNativeSensitivityRightYFullVR: 1.000000
INF: ProgSetting User: Input/fGpadNativeSensitivityRightYCinema: 1.000000
INF: ProgSetting User: Input/iGpadKeycode0: 69
INF: ProgSetting User: Input/iGpadKeycode1: 70
INF: ProgSetting User: Input/iGpadKeycode2: 82
INF: ProgSetting User: Input/iGpadKeycode3: 32
INF: ProgSetting User: Input/iGpadKeycode4: 71
INF: ProgSetting User: Input/iGpadKeycode5: 77
INF: ProgSetting User: Input/iGpadKeycode6: 2
INF: ProgSetting User: Input/iGpadKeycode7: 1
INF: ProgSetting User: Input/iGpadKeycode8: 38
INF: ProgSetting User: Input/iGpadKeycode9: 40
INF: ProgSetting User: Input/iGpadKeycode10: 37
INF: ProgSetting User: Input/iGpadKeycode11: 39
INF: ProgSetting User: Input/iGpadKeycode12: 67
INF: ProgSetting User: Input/iGpadKeycode13: 81
INF: ProgSetting User: Input/iGpadKeycode14: 27
INF: ProgSetting User: Input/iGpadKeycode15: 9
INF: ProgSetting User: Input/iVhkKeycode0: 27
INF: ProgSetting User: Input/sVhkVisText0: ESC
INF: ProgSetting User: Input/iVhkKeycode1: 116
INF: ProgSetting User: Input/sVhkVisText1: QSave
INF: ProgSetting User: Input/iVhkKeycode2: 120
INF: ProgSetting User: Input/sVhkVisText2: QLoad
INF: ProgSetting User: Input/iVhkKeycode3: 77
INF: ProgSetting User: Input/sVhkVisText3: M
INF: ProgSetting User: Input/iVhkKeycode4: 49
INF: ProgSetting User: Input/sVhkVisText4: 1
INF: ProgSetting User: Input/iVhkKeycode5: 50
INF: ProgSetting User: Input/sVhkVisText5: 2
INF: ProgSetting User: Input/iVhkKeycode6: 51
INF: ProgSetting User: Input/sVhkVisText6: 3
INF: ProgSetting User: Input/iVhkKeycode7: 73
INF: ProgSetting User: Input/sVhkVisText7: I
INF: ProgSetting User: Input/iVhkKeycode8: 52
INF: ProgSetting User: Input/sVhkVisText8: 4
INF: ProgSetting User: Input/iVhkKeycode9: 53
INF: ProgSetting User: Input/sVhkVisText9: 5
INF: ProgSetting User: Input/iVhkKeycode10: 54
INF: ProgSetting User: Input/sVhkVisText10: 6
INF: ProgSetting User: Input/iVhkKeycode11: 0
INF: ProgSetting User: Input/sVhkVisText11:
INF: ProgSetting User: Input/iVhkKeycode12: 55
INF: ProgSetting User: Input/sVhkVisText12: 7
INF: ProgSetting User: Input/iVhkKeycode13: 56
INF: ProgSetting User: Input/sVhkVisText13: 8
INF: ProgSetting User: Input/iVhkKeycode14: 57
INF: ProgSetting User: Input/sVhkVisText14: 9
INF: ProgSetting User: Input/iVhkKeycode15: 48
INF: ProgSetting User: Input/sVhkVisText15: 0
INF: ProgSetting User: Input/iVrhcControllerMode: 2
INF: ProgSetting User: Input/iVrhcTrackPadModeLeft: 2
INF: ProgSetting User: Input/iVrhcTrackPadModeRight: 1
INF: ProgSetting User: Input/fVrhcDeadzoneMouse: 0.100000
INF: ProgSetting User: Input/fVrhcDeadzoneKeys: 0.300000
INF: ProgSetting User: Input/bVrhcAllowLeftStickShift: true
INF: ProgSetting User: Input/bVrhcShiftSwapLeft: false
INF: ProgSetting User: Input/bVrhcShiftSwapRight: false
INF: ProgSetting User: Input/iVrhcKbmStickModeLeft: 1
INF: ProgSetting User: Input/fVrhcSensitivityLeftX: 0.250000
INF: ProgSetting User: Input/fVrhcSensitivityLeftY: 0.250000
INF: ProgSetting User: Input/fVrhcSensitivityRightX: 0.600000
INF: ProgSetting User: Input/fVrhcSensitivityRightY: 0.150000
INF: ProgSetting User: Input/iVrhcExtraKeyLeftGamepadDefault: 0
INF: ProgSetting User: Input/iVrhcExtraKeyRightGamepadDefault: 3
INF: ProgSetting User: Input/iVrhcControllerVisType: 1
INF: ProgSetting User: Input/iVrcKeycode0: 1
INF: ProgSetting User: Input/iVrcKeycode1: 2
INF: ProgSetting User: Input/iVrcKeycode2: 87
INF: ProgSetting User: Input/iVrcKeycode3: 83
INF: ProgSetting User: Input/iVrcKeycode4: 65
INF: ProgSetting User: Input/iVrcKeycode5: 68
INF: ProgSetting User: Input/iVrcKeycode6: 69
INF: ProgSetting User: Input/iVrcKeycode7: 67
INF: ProgSetting User: Input/iVrcKeycode8: 82
INF: ProgSetting User: Input/iVrcKeycode9: 70
INF: ProgSetting User: Input/iVrcKeycode10: 71
INF: ProgSetting User: Input/iVrcKeycode11: 32
INF: ProgSetting User: Input/iVrcKeycode12: 27
INF: ProgSetting User: Input/iVrcKeycode13: 9
INF: ProgSetting User: Input/iVrcKeycode14: 160
INF: ProgSetting User: Input/iVrcKeycode15: 162
INF: ProgSetting User: Input/iVrcKeycode16: 38
INF: ProgSetting User: Input/iVrcKeycode17: 40
INF: ProgSetting User: Input/iVrcKeycode18: 37
INF: ProgSetting User: Input/iVrcKeycode19: 39
INF: ProgSetting User: Input/iVrcKeycode20: 136
INF: ProgSetting User: Input/iVrcKeycode21: 137
INF: ProgSetting User: Input/iVrcKeycode22: 49
INF: ProgSetting User: Input/iVrcKeycode23: 50
INF: ProgSetting User: Input/iVrcKeycode24: 51
INF: ProgSetting User: Input/iVrcKeycode25: 52
INF: ProgSetting User: Input/iVrcKeycode26: 69
INF: ProgSetting User: Input/iVrcKeycode27: 81
INF: ProgSetting User: Input/iVrcKeycode28: 82
INF: ProgSetting User: Input/iVrcKeycode29: 32
INF: ProgSetting User: Input/iVrcKeycode30: 0
INF: ProgSetting User: Input/iVrcKeycode31: 0
INF: ProgSetting User: Input/iVrcKeycode32: 0
INF: ProgSetting User: Input/iVrcKeycode33: 0
INF: ProgSetting User: Input/iVrcKeycode34: 0
INF: ProgSetting User: Input/iVrcKeycode35: 0
INF: ProgSetting User: D3D11/i3DCreateMethod: 3
INF: ProgSetting User: D3D11/fSeparationNormal: 1.500000
INF: ProgSetting User: D3D11/fFocOffsetNormal: 0.030000
INF: ProgSetting User: D3D11/fSeparationComplex: 1.000000
INF: ProgSetting User: D3D11/fFocOffsetComplex: 0.000000
INF: ProgSetting User: D3D11/bUseDOFComplex: true
INF: ProgSetting User: D3D11/fZMultF: 0.500000
INF: ProgSetting User: D3D11/fSeparationG3D: 1.000000
INF: ProgSetting User: D3D11/fFocOffsetG3D: 0.000000
INF: ProgSetting User: D3D11/fG3DFovEnhance: 0.000000
INF: ProgSetting User: D3D11/fG3DCamHeightModifier: 0.000000
INF: ProgSetting User: D3D11/iG3DMainEye: 0
INF: ProgSetting User: D3D11/fPlayerModelOffsetY: 0.000000
INF: ProgSetting User: D3D11/fPlayerModelOffsetZ: 0.000000
INF: ProgSetting User: D3D11/iG3DShadowTreatment: 3
INF: OpenVRDevice: Initializing device
INF: TrackerOpenVR: Init
INF: OpenVRDevice: Init succeeded, HMD found: Oculus Oculus Quest2 (tracker: oculus)
INF: OpenVRDevice: Runtime Path: C:\Program Files (x86)\Steam\steamapps\common\SteamVR
INF: OpenVRDevice: API DLL Path: C:\Program Files (x86)\Animation Labs\vorpX\Devices\OpenVR\win64\vpenvr_api.dll
INF: OpenVRDevice: Render target size: 3120×3120
INF: OpenVRDevice: Render target AR: 1.000000
INF: OpenVRDevice: Desired game AR: 1.000000
INF: OpenVRDevice: Desired framerate: 90.000000
INF: OpenVRDevice: FOV: 103.982010
INF: OpenVRDevice: IPD: 63.230000
INF: OpenVRDevice: Zoom multiplier: 0.868231
INF: ExtraSetting: EnvImageMap/:
INF: ExtraSetting: /: 1.000000
INF: ExtraSetting: MouseDisableAxisY/: false
INF: ExtraSetting: VrhcSwapHands/: false
INF: ExtraSetting: GhResolutionQuality/: 6
INF: ExtraSetting: DmThreadSyncMode/: 0
INF: ExtraSetting: DmFluidSyncMode/: 3
INF: ExtraSetting: DmFluidSyncFpsCapMode/: 0
WRN: D3D11Base: No DeviceContext created, not hooking device
INF: D3D11Base: CreateDevice
WRN: D3D11Base: Microsoft Basic Render Driver detected, returning early.
INF: D3D11Base: CreateDevice
INF: DXGIBase: Installing DXGI device hooks.
INF: DXGIBase: Installing device method hooks.
WRN: Hook: Source module mismatch (dxgi_QueryInterfaceDevice), expected: C:\Windows\SYSTEM32\dxgi.dll, actual: C:\Windows\SYSTEM32\d3d11.dll
WRN: Hook: Source module mismatch (dxgi_GetParentDevice), expected: C:\Windows\SYSTEM32\dxgi.dll, actual: C:\Windows\SYSTEM32\d3d11.dll
INF: D3D11Base: FeatureLevel: D3D_FEATURE_LEVEL_11_0
INF: D3D11Manager: Instance created
INF: ShaderParser created: FarCryPrimal (3)
INF: DXGIBase: CreateSwapChain
INF: DXGISwapChainHelper: Installing swapchain method hooks.
INF: DXGISwapChainHelper: Installing swapchain1 method hooks.
INF: DXGISwapChainHelper: Installing swapchain3 method hooks.
INF: UpdateScreenSettings: res: 3840×2160, fullscreen: false
INF: DXGISwapChainHelper: SwapChain method hooks removed.
INF: D3D11Manager: Initializing device (frame: 0)
INF: Display Adapter Description: NVIDIA GeForce RTX 4090
INF: Nvidia Driver Version: 55612, r556_09
INF: Available GPU Memory: 24142MB
INF: D3D11Manager: Buffer Resolution: 3840×2160, Format: DXGI_FORMAT_R8G8B8A8_UNORM, MSAA: false
INF: UpdateScreenSettings: res: 3840×2160, fullscreen: false
INF: D3D11BufferGrabber initialized. Grab mode: 1, Sync mode: 1
INF: D3D11ShaderManager: shaders created
INF: D3D11GameRenderer: Initialized
INF: UIRendererDX11: Initialized
INF: ProgState: UpdatePostFrame first time.
INF: HookBase: Installing first frame hooks single-threaded
INF: XInputBase: Checking loaded XInput versions.
INF: DirectInputBase: Checking Main DirectInput Hook
INF: DirectInputBase: DirectInput not detected, hooking delayed
INF: ProgState: First Time Init 1
INF: OpenVRDirectModeManager: base init, mode: extra thread
INF: TrackerOpenVR: Init
INF: OpenVRDirectModeManager: base initialized.
INF: DirectModeManager: headset render target size reduced (unecessarily large): 3888×3888 > 3072×3072
INF: DirectModeManager: headset render target size final: 3072×3072
INF: OpenVRDirectModeManager: renderer initialized.
INF: UIRendererDX11: Initialized
INF: Engine3D: Scene Initialized: 13
INF: RendererDX11: Initialized (3072×3072). Multisampling off.
INF: OpenVRInputHandler: Initializing controller 1 using VRInput
INF: OpenVR ControllerManager: new controller found, type: 2, num: 0
INF: OpenVRInputHandler: Initializing controller 2 using VRInput
INF: OpenVR ControllerManager: new controller found, type: 2, num: 1
INF: OpenVR ControllerManager: Initialized
INF: MemScanManger: cache readiness: r:f p:f f:f
INF: SettingsUI: Init
INF: vorpScan: Starting to scan host: fcprimal.exe
INF: vorpScan: Rotation scan succeeded.
INF: vorpScan: Exiting.
INF: vorpScan: Starting to scan host: fcprimal.exe
INF: vorpScan: Rotation scan succeeded.
INF: vorpScan: Exiting.
ERR: App: TopCrashHandler: unhandled exception ACCESS_VIOLATION at 0xFFFFFFFFFFFFFFFF
ERR: App: TopCrashHandler: module: FCPrimal.exe, offset: 0x3AE05F7
ERR: App: TopCrashHandler: unhandled exception end
INF: Main: Detaching from fcprimal.exe
INF: Main: Graceful Exit
INF: UIManager: Released
INF: GamepadManager: Released
INF: Keyboard: Release
INF: InputManager: Released
INF: SoundManager: Released
INF: D3D11Base: Removing Main Hook
INF: XInputBase: Removing Main Hook
INF: DirectInputBase: Removing Main Hook
INF: MouseKeyboardBase: Removing Main Hook
INF: HookBase: Removing system hooks
INF: HookBase: Removing mouse hook
INF: OpenTrackHelper: Release
INF: VRControllerManager: controller deleted (0)
INF: VRControllerManager: controller deleted (1)
INF: OpenVR ControllerManager: Released
INF: OpenVRDirectModeManager: Releasing
INF: TrackerOpenVR: Release
INF: OpenVRDirectModeManager: Released
INF: TrackerOpenVR: Release
INF: OpenVRDevice: Released
INF: ResourceManager: Released
INF: MemScanManager: Released
INF: MemScanManager: Destroyed
INF: GameHelper: Destroyed
INF: App: Released
INF: Main: Graceful Exit Success

INF: vorpControl: Exiting process life thread: FCPrimal.exe, 29284

[Boblekobold]

Bioshock Infinite (especially Burial at Sea Episode 2) and Bioshock 1 original (I guess Bioshock 2 original is even better) if you have an old graphic card.

Metro 2033/Last Light, etc. are awesome (Metro Exodus is the most beautiful game you could do I think). But a good graphic card is needed.

All Bioshock and Metro have G3D (even if raytracing without G3D can be a good option too in Metro Exodus).

Cyberpunk 2077 isn’t the best because even with an RTX4090, it’s not enough.

Elden Ring, Death Stranding, Guardian of the galaxy are really better in VorpX (even if it’s not full VR).
Redfall too. Deathloop is Ok (especially the end).

I guess games like Farcry Primal, Dishonored, Prey 2017, etc. must be really good (I think they have G3D but I didn’t try them yet).

Dying Light 1 of course.

First person game that allow you to have high 4:3 resolution (3480×2880 or at least 2880×2160) and 120 FOV are like native games in VorpX (with G3D, or at least Z3D but It’s not so important to me and even without 3D at all, some games are awesome in full VR).

Any game with good looking graphics, heights/vertigo or giant environment/ennemies are usually great in VorpX.

[Laser]

Well I wasn´t going to upgrade my G2, but it decided to die unexpectedly. First I looked at Crystal and Big Screen but both have downsides and are quite expensive units, then I thought about Quest3 and almost bought one. But finally I decided to get Pico 4, my thought process was that I needed something that was available immediately and its really cheap unit.

After few days of setting this thing up and testing it in various ways I am positively surprised how good it is. Compared to G2 the resolution is littlelower but the pancake lenses are far better than the fresnel lenses of reverb. I have only used the pico in wireless mode with my pc, its really nice being wire free even when gaming seated. Pico´s own streaming assistant didn´t work at all for me but with virtual desktop I was able to connect instantly. I still need to mess around with my routers and settings to get best possible wifi connection.

Downsides and upsides compared to Reverb G2 V1
-Slightly lower resolution
-Built in audio isn´t great (I plan to use wired phones connected to pico)
-Stock facial interface isn´t that comfortable (I already printed new interfaces to fix this)

+pancake lenses offer much wider sweet spot and the image is clear to almost the edges of the screen
+optional wireless mode
+stand alone mode (not sure that I will be using this much though)
+really cheap, I only paid little over 300€ for the 128GB model, that is almost half the price of quest 3)
+colour passthrough mode vs the black and white in G2 (resolution isn´t great but its enough that you can move around in your house without taking the headset off.
+headset/controller tracking is far better, I couldn´t really play beat saber with G2 controllers due to losing controller tracking.

[Meowvyrn]

Poppy Playtime; specifically Chapter 3.
Far Cry 5 Also.

[MarcDwonn]

Please report if the nVidia Ambient Occlusion works in stereo mode. I’ve never been tempted to add AO to The Witcher 1, because it already uses baked lighting. On the other hand i tried out the Far Cry VR mod the other day, and that one really needs some AO because it looks super flat. I briefly thought about nVidia AO, but dismissed the idea as “not compatible” with stereo view.

So yeah, looking forward to hear about your experience.

About modding: i played TW1 fully modded with texture mods and other stuff, and the engine gets a bit more unstable, but it works great in G3D, S3D is perfect, even the particles have proper depth. It was my first vorpexed game i played and i was mighty impressed.

[Wehrwolfi]

Hi Vorpx lovers !

I’m a recent Vorpx user and tested it so far only with a few games, maybe not the best ones as they are not officially supported (Far Cry 5, Guardians of the Galaxy).
Although the result is great and in some cases really near to my 1080p physical display, letting me use the headset most of the time.
I play mostly in Immersive Screen for those games without head tracking, so basically, I mainly use the stereo-3D function as I would have done with Reshade+SuperDepth3D in the past.

My headset is Pico 4, I connect through Virtual Desktop, my GPU is RTX 3090.

I found that the best graphical quality was achieved with those settings :
– Games resolution the higher possible (over 4k resolution I don’t find that much difference and performance decreases a lot)
– Play through steamVR mode instead of just Generic 3D Display (then Virtual desktop SBS desktop mode). Because VD is capped at 1440p…
– VD setting in Godlike (3120×3120), HEVC-10 codec, max bitrate.

What I would like to understand is how the render chain is made to find the “sweet spot”.

First step is the game itself : setting the higher resolution improves the quality and sharpness, making the use of AA unnecessary.
I would tend to say that here the higher is the better.
Then Vorpx :for example, in my case, if I don’t run the game through Vorpx virtual screen, then 4K resolution will be in fact DSR. Does Vorpx “grab” the output at 4K before downscaling to 1080p ? If yes, we benefit from DLDSR a bit. If not, it would be better to use custom 4K resolution on virtual screen.
Then SteamVR : renders at 3120×3120 because of VD Godlike setting. Don’t know if I should put a manual value there? Maybe the same as game resolution?
Then Virtual Desktop : takes the output from SteamVr, encodes it and sends to Headset, then decodes it in Standalone and updscales/downscales to headset resolution, with barrel distortion etc…

So, there is a whole chain of conversions involved there. I would like to get your advise on what could be a common guideline to set it up. Is simply the higher resolution at all steps the best if the computer can manage it? Or should we try to align everything on same value to avoid upscales/downscales etc?

Thanks in advance :)