Forum Replies Created
-
Posts
-
@ sympathetic: reinstall with the latest version of the mod. That will reset all settings to default and ensure that CET is installed correctly.
Someone recently guessed that Windows only detects monitors as being on/off via display port. If yours has a display port input, using that instead of HDMI *might* do the trick. Alternatively you can activate the virtual monitor manually via the vorpX tray icon’s right click menu. Only drawback is that you will have to select in manually in games that way.
I’m currently toying with forcing the virtual monitor to become the primary display when it is enabled regardless of the physical monitor’s state, but that’s a double edged sword in some ways, so not sure yet whether it will actually happen.
That’s definitely not right.
Not really sure though what to recommend specifically, sorry. You can find pretty much all information required to troubleshoot conflicts with other programs in the pinned trouble shooting post, there isn’t anything I could add to that. TLDR: disable *EVERYTHING* you may have running in the background.
@ sympathetic: I recently encountered the motion controller not working issue myself for the first time. Worked again after a relaunch. I’ll try to figure out the cause. For now please check whether restarting the game helps in your case too.
Make sure to launch the game with DX11. Important: G3D doesn’t work right after the patch. All shaders have been recompiled, hence shader definitions in the profile don’t work anymore. Use the vorpX 23.1.0 beta for Witcher 3 with DierctVR (AFR) 3D.
As far as Cyberpunk performance is concerned primarily check the hints shown in the profile start message.
Warnings in the log typically are nothing you have to care about. In this particular case they just mean that a wait action in the headset render thread took a few microseconds longer than it ideally would have. Nothing to worry about at all.
The version message is just a leftover debug message highlighted as error so I can find it easier, shouldn’t actually be there at all. All good.
If hooking fails for almost everything, there almost certainly is something getting in the way.
If you haven’t done so already, please first try the trouble shoot options that pop up in the ‘Attaching To’ dialog after a minute or so.
If that doesn’t help, you have to dig deeper. The pinned trouble shooting post on top of this sub forum has more details on the matter.
Just a heads-up that I have updated the standalone installer with a version that includes the latest Cyber Engine Tweaks build. The mod itself hasn’t changed, so no need to reinstall if you already updated CET manually to restore compatibilty with the latest Cyberpunk update.
Z3D still works. The profiles launches the game with DX11 automatically. The game doesn’t really have a DX12 renderer. It uses a DX11 > DX12 wrapper that clashes with vorpX when it runs in “DX12”-mode.
Just speculation, but I’m fairly certain that CDPR made some deal with nVidia to push RTX. TW3 doesn’t even have a real DX12 renderer, instead they use a DX11 > 12 wrapper, implemented some RTX effects on top of that and *heavily* downgraded the original shadow look to make RTX stand out at least in some way.
Doesn’t exactly require an uber brain to guess how something like that may happen… I’m surprised that there is almost no outcry about the whole affair except from one or the other Steam forum thread that noone reads. The gaming related shitstorm machinery went ballistic on less annoying occasions in the past. ;)
The 23.1.0 beta comes with something special for the latest Witcher 3 version. TW3 is now one of the profiles that have been heavily enhanced with a game specific mod programmed in the game’s scripting language. Provides alternate frame 3d, automatic FOV adjustment and auto EdgePeek in cutscenes etc. Reportedly compatible with a first person mod that is available for the game, but I haven’t tried that myself.
You can download the 23.1.0 beta from the first post of the according thread in this sub forum.
Interesting info re DP vs. HDMI, I’ll check that. Not something I could do anything about, but still useful to know. Same for your scaling changes, that’s apparently what Windows does for whatever reason on your machine. Normally I’d expect that only the virtual display’s scaling gets adjusted when it is added. At least that’s what happens here.
That sounds distinctively weird. First please check whether maybe your motion controllers lie on the desk in a way that their triggers are pressed. VorpX can emulate mouse/gamepad input with motion controllers. Might also make sense to take out their batteries, provided that’s possible.
If that’s not the issue, disconnect any additional input device (e.g. a flight stick or a steering wheel) that you potentially may have connected to your PC.
That definitely shouldn’t happen. Try to reset all vorpX and TESO settings to default. Also remove your mods if the issue still occurs afterwards. Graphics related mods for example may hook into the same DirectX functions as vorpX and by doing so cause all sorts of havoc.