Forum Replies Created
-
Posts
-
That’s weird for sure. Are you by any chance running a system with multiple user accounts, i.e. a dedicated admin user and a ‘normal’ user? In such cases a game may run under a different user account than vorpX if you run vorpX as admin and the game as normal user or vice versa, which potentially might lead to problems like that.
Also please check whether you maybe have some super aggressive “security” option enabled in your AV scanner that might affect communication between two running processes. if in doubt, use Windows Defender with default settings.
The games that are working for you use DirectX11, the ones that don’t DX9, with the exception of Alan Wake. Sounds as if something might be running in the background that causes a conflict for DX9/10 games. A lot of programs also hook into games like vorpX and may cause issues like that. The trouble shooting guide on top of this sub forum has more details on that matter. Best way to trouble shoot this is exiting *everything* running in the background.
In case you have multiple monitors also please check whether the same issue occurs while you only have one monitor connected. If it works that way mirroring the primary monitor instead of extending it might help. vorpX can try to force games to a specific monitor, but that might not work as expected under all circumstances.
Sounds like an issue that I encountered early on where depending on the ‘Color Precision’ option in the game’s graphics options locating the depth buffer could be glitchy. Has be set to ‘High’. vorpX should handle that automatically unless automatic settings are disabled.
The default for the controller setting in Steam’s Cyberpunk properties you mentioned above is “Use Default”, which works perfectly fine here. My guess would be that maybe you changed it before and Steam pulled the changes you made from the cloud when you reinstalled Steam.
Anyway, glad you fixed your issue. Also thanks for sharing your solution! Might indeed be useful if anyone accidentally changed that Steam setting. As far as I’m concerned I consider this matter closed.
What the OP didn’t consider is that in contrast to their batch file idea some settings changes vorpX applies depend on information that is only known to vorpX while hooked into a game. Secondly vorpX hooks into a game after it has already been launched. Trying to only apply settings changes temporarily at that point in time would be heavily unreliable and actually fail for a fair amount of games since they might already have loaded or at least opened config files at that point.
All in all temporary settings changes would be less reliable and in some cases, which rely on information only known at runtime (e.g. resolution anf FOV related settings), also impossible to apply with the precision vorpX does apply them.
Please don’t overlook the last part of the reply. The wishlist is fairly long and as much sympathy as I have for your hardware tinkering, I simply can’t treat something as special as your wish with priority. In short: no promises when (or even if) this actually happens.
Incredibly cool to see that there are still people who tinker with their own hardware, feels a bit like good old times…
I‘ll add your wish to the already fairly long list of nice-too-have features. However, this is a bit too special to be treated with priority, sorry. So don‘t get your hopes up that it will actually happen anytime soon.
Take that with a little grain of salt, I don’t have a Pico, but since it can handle SteamVR games, it will almost certainly work fine with vorpX via SteamVR.
Can’t really say anything useful to that question. You would have to implement some intermediate layer between vorpX and your modified headset yourself that changes the perspective similar to how Pimax does with the parallel projection option in their headset driver.
The override is off per default. like said above, you don‘t have to tinker with any input related settings under normal circumstances. If you encounter further issues, please reinstall the mod next time. That resets all settings to default.
Doesn‘t it work by using the Grounded profile as a base? Detailed step-by-step guide a few posts above. I’m not 100% sure, but I think the game uses Unreal Engine 4, so it probably will work just fine that way.
Please check whether your version of the game maybe uses a different .exe name than the one that is assigned to the profile. There are a variety of cases where that might happen. E.g. Game of the Year editions sometimes use a different .exe name, sometimes also Epic Store versions are differently named than Steam versions and so on, also occasionally not so official versions of games.
In such a case you can make a copy of the existing profile and then assign the actual .exe to the copied profile. There is no guarantee that that will work, but it’s worth a try.
The .exe name(s) that a profile is assigned to are shown in the config app. You can compare them with your game version by locating the actual .exe in a game’s install folder.
vorpX automatically chooses the profile to apply depending on the application it is hooked into. I.e. if not hooked into a game, there is no way to tell what profile to select.
I have the this matter already on the nice-to-have-list. Not as easy as it sounds unfortunately, the desktop viewer would have to be extended with some way to load profiles partially on top of its own. That’s not a trivial thing to implement. I can’t promise when (or even if) that actually will happen.
The exact resolution computed from a chosen quality varies slightly depending on the headset and some internal factors.
From where I sit d-pad not working, but the rest of the gamepad emulation working, looks virtually impossible TBH, at least without something interfering.
You should really focus on fixing the gamepad mode issue. Nothing of what you do for days now is necessary, and I never heard of anything like this in the last 10 months since the mod is out, so it’s fairly safe to assume this is some individual problem with your setup.
Anyway, I uploaded a new build that *MIGHT* help with your keyboard mapping problems.
That’s definitely all now I can do for you, I’m afraid.