I’m not sure if anyone can help me with this. I’m using VorpX 24.1.0 (for the native Starfield support) on Oculus Rift S, and I decided to try Left 4 Dead 2 (build ID: 15163053).
When using the Rift S controllers in Keyboard/Mouse emulation mode I can’t use the left stick to move forward, only backward. While it might be interesting to play the game as a marine who can only back-pedal in a panic, that’s not really what I’m hoping for!
When using the Rift S controllers in Controller emulation mode, the left stick does nothing at all.
I’ve tried memory scan repeatedly, but it fails every time. Is there something obvious I’m overlooking, or is L4D2 support just broken in this version of VorpX? Also, is it possible to disable the right stick so I don’t accidentally nudge my view off centre?
Thanks for any help.
Thanks for coming back to me Boblekobold.
Still not sorted but close! I haven’t had this with other games im playing such as Starfield or Stalker Anomaly, just with Fallout 4.
I am playing the Fallout Anomaly mod pack and it all looks really good apart from this scope thing. I have tried with as many FalloutPrefs, custom etc to match up FOV’s and done the directVR scans in game but nothing works.
I then downloaded the 24.1.0 vorpx beta today, fired the game up and did a DirectVR scan and it worked! Scopes were working as they should and zooming in. Paused the game, it then went really blurry and crashed when i tried to reload. Now getting in game and doing the scan doesn’t change anything and scopes not working again.
The FOV does stutter around in game so i think it might be one of the mods causing problems but with 816 mods i have not idea which one!
any news on a starfield profile? ralf said he would make one months ago.
Hello,
I am using Vorpx 24.1.0.
The official profile for Starfield is causing the 3D effect to rapidly turn off and on when close to a wall, large object or confined space. It makes a kind of vibrating/shaking effect with your character as the 3D rapidly turns off and on. Sometimes the 3D effect stays off in certain areas of the game like caves or certain hallways.
I turned the 3D effect down to 0.34 to reduce the effects of this happening but there is not a lot of 3D effect happening at that level.
I noticed the same thing would happen with a USER profile before the official profile was released with version 21.3.5.
There was a profile when the beta was available based on Resident Evil Village profile that this vibrating/shaking 3d effect was not occurring.
It is playable with the 3D effect turned down though and is still quite good.
Is there a graphics setting I have turned on that is causing this?
Has anyone else experienced this issue?
Thanks.
Anybody know of a way to get headtracking to work for Starfield? I’m using 24.1.0 and it all seems good but the headtracking will not work for me at all.
Trying Starfield with 24.1.0 everything seems good except i can’t get headtracking to work at all, anybody know of a way i can get it to work?
@Xoleen It was the config files in “C:\Users\<username>\Documents\My Games\Starfield”, StarfieldCustom.ini and StarfieldPrefs.ini
When you delete them the game will recreate them from defaults the next time you launch.
Launch with VorpX active, and from the main menu open the VorpX menu, set resolution option, save and exit. Next launch, worked perfectly!
No. Vorpx dont work in g3d for dx12 games. Only zadptive and znormal.
For me , most games run better with znormal that in g3d.
Ralf, is this true? I was under the impression that VorpX supports DirectX 12 games in the best 3D experience obviously (G3D). If not that might explain why Star Wars Battlefront 2 is not even hooking when I use DirectX 12, even though I’m using the official game profile. If true it kind of sucks, because in my mind I payed for that as future proofing for a 3D injector that is in development (as opposed to Tridef). If yes, do you have plans for that? Some new games are DirectX 12 only, like Starfield :/
Update on that Starfield problem I was having: deleted all the config files and this time VorpX was able to update properly — all the FOV and resolutions working as expected!
User error as usual ))))
Game is looking fantastic now, and the gestures are a great addition — good work as usual!
Hi Ralf,
Starfield experience is so far great. Thank you!
One question – the mouse pointer only works in the upper left quadrant of the screen. Can’t move it below this quadrant. Any suggestions?
Is there any way to automate the request code / response email for key generation? I’ve been waiting for about 12 hours for a new key to get going in Starfield or at least start trying to get it working on Proton for Linux. Given I may be making several installation rounds on various prefixes, I may have to be requesting a half dozen request code responses for keys to get vorpX working in each Proton instance. I get it’s Christmas – but if this was automated I wouldn’t have to rely on a human to respond with a license key.
Great to see more updates!
For the Starfield profile, what are the recommended resolution and FOV settings?
Ok I can’t edit this previous post. I wish this were a better support platform but someone is averse to Discord. Ok so here is the update I was trying to edit to:
Ralf, I’ve found vorpx to be quite useful. Following this thread, I encountered the same issue on version 24.1.0 where I can open Vorpx Desktop Viewer, and all the Vorpx tools are present. However, upon launching StarField, the game starts to load but freezes, returning me to Vorpx Desktop Viewer. This confirms that hooking is functional since Vorpx Desktop Viewer runs, just like any game attempting to hook. So, the question arises: why does launching the game fail even when the Vorpx Desktop Viewer option is operational?
I’ve disabled AMD CPU video, Disconnected all my monitors other than my primary, disabled MS Defender, and removed all possible software that could talk to my RTX 4080. Clean Windows 11 install 23H2.
Running Starfield from MS Store / GamePass purchased
This issue seems specific to Starfield. Before starting, I run Vorpx Desktop Viewer, and Vorpx Desktop Viewer initiates while my primary monitor is disabled. I can’t see anything on my monitor unless I enter my VR headset (Quest 3). If I previously used your settings for Starfield, should I clean all of that up now? Do I need to perform a fresh Starfield install without any special files from previous attempts for it to work in version 23.1.0? Is there a need to create a special display in VorpxConfig? With Vorpx now showing Starfield as having native support, the details related to Starfield and version 24.1.0 are somewhat unclear. I hope you can provide some clarification. Thank you!
I ran the vorpX web installer I downloaded previously but it only downloaded version 21.3.5. I’m trying to get version 23.x BETA so I can play Starfield on it. I don’t know how to download the beta though – it’s not listed under Home or Support FAQ.
Ralf, I have really gotten a decent amount of use out of vorpx. Following this thread I have the same issue here on 24.1.0 where I can open Virtual desktop, and all the vorpx tools are there. But launching StarField, it starts to load then just freezes, and takes me right back to Virtual Desktop. So that means, to me, that we have confirmed that hooking is working or Virtual Desktop would also not run ,just like any game trying to hook. So what could it be if Virtual Desktop option from Vorpx (not the alternate Virtual Desktop app on Steam or Meta) is working, but launching the game starts and then fails. This is specific to Starfield. Preparing to start I run VD and Virtual desktop does start and my primary monitor is disabled so I can’t see anything on my monitor unless I go into my VR headset (Quest 3). If I was using your previous settings for Starfield, do I need to clean all of that up now? Do I need a fresh Starfield install with no special files from previous attempts to have starfield work in 23.1.0? Do I need to create a special display in VorpxConfig? Now that Vorpx is showing Starfield as native support, the information related to starfield and 24.1.0 is a bit vague. Hoping you can fill in some blanks. Thank you!!!