Search Results for 'cyberpunk settings'

[Ralf]

When you lower the image zoom setting, you get black bars above and below the image. That’s how the zoom works. Alternatively you can instead set an ambience colored background after clicking on ‘More FullVR settings’ in the menu if you prefer that.

The black area below the image is a bit larger than above since VR headsets use an asymmetric view frustum where more pixels are shown below the eye than above to have more precious pixels where it counts. A neat optimization that factors in human vision, which focuses more on things below your eyes than above in the sky. Since the the game was rendered with its usual symmectric frustum, you end up with more space below than above the image when you zoom out.

In addition to that:

If you want to utilize the full screen of your Quest3, set the image zoom to the max. Unless capped on purpose to deal with game quirks (like in Cyberpunk) that will ensure the screen is used fully. To make sure profiles and potnetial setup instructions for user profiles are universally correct, per default everything is setup the same way on each headset, reflecting roughly the original Oculus Rift FOV. You can however adjust that to your liking, unless – again – the zoom is capped on purpose to deal with game quirks.

Caveat: As Boblekobold pointed out in the other thread, you will have to adjust the game FOV accordingly in games where vorpX doesn’t do that automatically.

More detailed information about how FOV and ImageZoom are two sides of the same coin can be found in the vorpX help.

[alien]

Hello,

I have the full version of Vorpx, not the free Cyberpunk edition ( idk if it matters )

While I was adjusting the settings, I notcied that I can’t zoom the image more than %85. There is a black bar / ambience down my POV and it’s very distracting.

Normally I can zoom in to the image to 1:1 … I just finished all the Bioshocks and this wasn’t an issue there… i don’t understand why Vorpx doesn’t let me zoom %100 on Cyperpunk specifically.

I’m using Z-Normal. Not Direct VR/G3D. Resolution @ 3840 x 2880 / Quest 3

Any help would be appreciated..

[Marozaki]

I’m using AirLink or SteamLink for MetaQuest 3, but after about 5 minutes the left and right images start to get out of sync, freeze, and move up
and down.
This happened with both the standalone version and the retail version, and it was the same even when I changed the image quality.
Ray tracing is turned off in the in-game settings, and the FPS is high on the flat version.
The refresh rate is 72MHz for both MetaQuest 3 and SteamVR.
The wireless connection is Wi-fi 6, but I don’t have a wired connection or virtual desktop so I haven’t tried it.
I recently upgraded to an AMD RX9070 and started playing Cyberpunk VR again, but I can only play for 5 minutes at a time.
Previously, I was able to play without any problems with Valve Index and AMD RX6800, but since I switched to MetaQuest 3 which has high resolution, I would like to play at ultra resolution.
When I check the SteamVR performance graph, I occasionally see purple lines indicating display errors and light blue lines indicating network latency, but I don’t experience any lag or freezes in other games.
If anyone has experienced similar symptoms, or knows the cause or how to resolve it, I would really appreciate some advice.

Translated by Google.
From a VorpX fan in Japan.

[flamefury42]

What’s the best way to optimize my game for pc build? What settings should I tweak? Also, does the licensed vorpx inject the cyberpunk 2077 from the free version of the mod? I’m just trying to make sure I’m running the latest version from vorpx. I’m up to date. I updated CET and I can get in and run the vr. I’d like to fix the black bars that I see around my screen, do i need dial up my screen resolution in game? It’s also very choppy when I play so I know i have to tweak some things back in my settings. Does Vorpx allow dlss or no? Thank you for any assistance that you can provide me.

[HarnessedYeti]

Need a to get a link or info on how to DL 21.3.5 mainly because I don’t
like the forced VR in Cyberpunk. Tried switching to immersive screen mode but
not all settings like screen size and scale work anymore for some dumb reason.

[djbert]

I just wanted to drop some feedback on Cyberpunk in VR with Vorpx since I got working this week. It is awesome! I got the same feeling again like when I played Half-Life: Alyx for the first time with my Meta3; I was floored! Once you dial in the VR settings with Vorpx, it looks great and is smooth. I find myself just putting around and taking in the sights, as it really changes the perspective of the game; almost like it is brand new game you are playing for the first time. The immersion even gets to me a little bit. Like being high up in the game and looking around/down, I will get the heebie-jeebies for a bit lol. I wear my Astro A50 headphones with my meta3 and it is a great immersion bubble for the game. The sights and sounds really are great. And aiming with your head is growing on me as well, though I play with a xbox controller to get around. It works well imo once you practice the aiming mechanic with your head movements and the body movements with the controller.
Some parting thoughts. I fired up Alyx again to compare the graphics between both and Alyx is way better than CP2077 by a long shot imo. To note I do have an RTX 5090, so I am sure that is factor. However, to be fair of course, Alyx is a purpose-built VR game, and it is nowhere as open-ended like CP2077. But if CP2077 was as CLEAR and SMOOOTH as Alyx in VR at least, man CP2077 would be the game of the decade for VR play. Well, if anyone actually knows how to tweak CP2077 to have the same clarity and smoothness as Alyx on a meta3, I am all ears lol.

[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+

[abeardedpirate]

Have a PSVR 2. Installed the free mod to see what this is about.
In settings selected SteamVR since PSVR is using SteamVR app.
Launch game. SteamVR never brings up the game. Can see game if going to desktop mode or theater mode.
While game is open no inputs work. No keyboard inputs, no gamepad inputs, no inputs from my PSVR2 controllers.

I have uninstalled the mod, the game, fresh reboot, installed the game, rebooted, installed the free mod, fresh rebooted again and everything in between. The game will never register inputs. My keyboard does work as I can press Windows Key and get the start menu up to do other things. I can also hit the PS home key to bring up steam interface so I know my buttons work but they are not registering with Cyberpunk itself.

I uninstalled the mod and selected default on every setting inside of cyberpunk 2077 before rebooting and reinstalling the mod just to make sure everything is good. Since there is 0 interface with the free mod the only way I can get the VR selector up (Steam / Meta / Other) is to just reinstall the mod again.

I’ve launched Cyberpunk 2077 letting it open Steam VR and I’ve launched Steam VR and then opened Cyberpunk with no luck.

I went on Steam settings and have enabled steam input override for Cyberpunk 2077. I’ve tried it disabled and enabled same issue both ways.

I’m on an i9900k with a 2080ti with the PSVR2 plugged directly into my 2080ti. I haven’t had issues with other actual VR games/programs but I can’t make this work. Nothing seems to do anything. Delete / left button + right button / and L3 or w/e gamepad is nothing brings up any settings like the mod installer says it does.

Any help would be appreciated cause I feel like I’ve exhausted all the troubleshooting steps I’ve seen on this forum at this point.

[fitprovr]

For Cyberpunk 2077. I can’t get my quest 3 to go to VR with all of the steps. It stays in flat screen but all of the controls work. I’m not sure what else to do. All the configurations seem fine. Headset, controllers, and gesture settings all work in game, it’s just stuck in flatscreen.

[_John Smith_]

After watching some YouTube videos and playing a bit with the settings I seem to have found solutions:
1. I set the framerate cap to off and headset sync to custom/fast. This seems to give a smoother gameplay and – perhaps I’m mistaken – even slightly better graphics.
2. I increased vertical field of view in Cyberpunk settings to 90 (from 80). I also discovered that Vorpx apparently automatically added a custom resolution to Cyberpunk of 3200×2200 automatically and changed to that resolution (I set render res to Ultra in Vorpx).

Problems are solved and everything looks fine (I’m using Virtual Desktop on Quest 3 set to use OpenXR in God-Like render res at 90 Hz, DLSS Transformer Model set to Quality).

[_John Smith_]

I need help with 2 issues in Cyberpunk.
First one is that the movement of NPC characters in 3D view does not look smooth even though my headset frame rate is at 90. Vorpx sets the game frame rate by default to 2/3 of that, 60, an d according to the built-in fps display I achieve 60, but still the movements of the waitress in the bar at the beginning don’t look smooth. Is that due to the rendering method of Vorpx or should I change any settings?

2. My vertical field of view is a bit too narrow, there are a few degrees of black content below the picture. Is there any way to increase it like a zoom factor in Vorpx settings? This may be due to me using a 16:9 screen resolution (4K) but I’m hooked up to a 4K TV which does not allow me to add custom resolutions in the NVIDIA control panel (TV can’t display them).

Thanks for your help!

[Boblekobold]

Cless_Aurion wrote:

I have to partially disagree.

Concerning details in VR vs monitor : if used normally, most people don’t really see pixels and details on a 4k/8k monitor.

This is objectively false.

So why people go to the cinema ? It’s easier to notice details on a giant screen.
Ok you can be very close to your 4k monitor, but I really don’t like that, and it’s not curved properly (vertically and horizontally) so it’s not as immersive as VorpX.
If I don’t use VorpX, I prefer video projector because comfort matters and 1080p is enough for me in this case, as long as the display is 2m60 large and not too close I’m happier than with a monitor.

But I always play FPS/TPS with VorpX. It’s so good to be in the game, and it’s so much more detailed and beautiful ! And as my G2 is afocal, it’s like looking at a very long distance.

Cless_Aurion wrote:

If you play in immersive screen, the displayed game can be larger than your FOV so it can be more detailed than a monitor with the same resolution than your VR headset.
It’s the difference between an hemispherical Imax theater (with headtracking and 3D in this case) and a monitor.

Yeah, we agree there, it is also an absolute crazy waste of performance unless you have a way to cull the polygons you aren’t looking at directly though, which is why UEVR is so neat, it is able to use the native software built-in UE to show the game not as AER, but its full proper VR version, with all the software boosts that that means.

It should be a (little) waste of performence (because you still have headtracking). But in fact, in my experience with AAA games, UEVR’s performences and image quality are so much worse that VorpX is still better, whatever display mode you use (full VR or immersive screen).

And it’s not a waste of performance, because it’s very useful (for example if a first person camera is partially locked because for example your character is seated in the original game, it avoids clipping and broken animations you would have in UEVR, and it also avoids to rotate the entire world around you).
It also allow you to clearly see the HUD and to switch instantly between display mode with edgepeek.
It’s a great way to play ! Even if I usually prefer full VR, some games (or some part of them) would be too altered.
It’s the best compromise, and you can only do that with VorpX.

Anyway, VorpX always do that, even in full VR (if you don’t want to see borders…)
The game is rendered at high resolution with high FOV and you look at a part of this render (most of it of course if properly configured).

Cless_Aurion wrote:

VorpX does so too in its VR form I believe, but don’t really know much about how @Ralf does his black magic on it. The fact it works in so many different engines is flatout baffling.

I guess there are several methods. It’s not AER (except Cyberpunk), It’s true 3D stereo in hundred of games (it probably adds an additional camera and move the original one, exactly as UEVR does, except with VorpX it’s not a broken/automated/unused feature from Unreal Engine and it actually performs better in some games, especially DX9 ones).
It’s great to be able to configure 3D settings and it’s more comfortable in a lot of cases (and accurate/immersive in first person games because UEVR can break easily when something is close to your head).

But in my opinion, when G3D can’t be perfect, a good Z3D is better than a bad G3D, at least in large outdoors environments, so VorpX’s Z3D options can be the best choices sometimes (even better than UEVR’s G3D in some games because it avoids a lot of glitches and incompatibilties with raytracing, etc.)
And anyway with the most beautiful games if you want good graphics settings, you have no choice. G3D can be too demanding, even when it doesn’t break effects.

[Django9898]

Ralf wrote:

Please make sure that your CP2077 controls are also set to default and you do dont use any tool/mod that affects input. Under normal circumstances everything is preconfigured correctly out of the box.

I found the problem.

Go to Steam library/ right-click on Cyberpunk 2077/Settings/Controller and in the drop-down menu activate Steam- Input.
Now the controls are fully working as a gamepad.

[Django9898]

Ralf wrote:

Please reinstall the mod to ensure that all settings are set to their defaults. Also reset your Cyberpunk input settings to default. Per default the steering gestures work like analog sticks on a gamepad.

Just to be sure…
Should the control settings set to KB/Mouse or to Gamepad in the VORPX Menü?
When i use the KB/Mouse option are the Steering Analog or Digital?
I tryed both but the results are the same for me…
Next step i try to reinstall like you said.
And thx for your fast response!

[Ralf]

Please reinstall the mod to ensure that all settings are set to their defaults. Also reset your Cyberpunk input settings to default. Per default the steering gestures work like analog sticks on a gamepad.