Forum Replies Created
-
Posts
-
Updating CET should suffice. I’ll upload a fresh build when CET got updated, but that won’t do anything else than updating CET manually.
On a sidenote: if you haven’t done so alreedy, read the *very* useful instructions in the vorpX launch room after starting the game. Stuff like this is explained there.
Try the vorpX beta, the desktop viewer has been rewritten entirely and should now also work with most (but not necessarily all!) fullscreen games. Also comes with a virtual monitor that handles resolutions higher than your PC normally can handle automatically.
Please also keep in mind that the desktop viewer is a free convenience app that you get on top of vorpX. It’s not vorpX’s main focus. Thanks for your understanding.
That’s a game glitch. The mod requests the current game state (interactive, combat, cutscene, driving) etc. via the game’s scripting language and then switches vorpX into its according mode, e.g. it enables EdgePeek in cutscenes, applies camera tweaks and context sensitive gestures for driving and fighting, and so on.
After said cutscene for whatever reason the game still reports to be in cutscene mode for a while, so there is no way for vorpX to know that the cutscene has ended. Pretty weird glitch. IIRC the game state changes eventually after a while though, so you should be able to simply play in EdgePeek mode for a minute or two until the game reports the correct game state again.
Auto enabling the virtual monitor by switching off the actual display only works for monitors that Windows can detect as on or off (probably only monitors connected via Display Port).
For enabling it via putting on the headset make sure to launch the desktop viewer first. Also your headset must have the ability to report whether it’s in use or not. Most popular headsets can do that, but there might be some that can’t.
Must be a concidence. vorpX doesn’t do anything unless it is running.
vorpX has do de ‘hooked’ into a game to affect it. It only can do that when it is running. You can be 100% sure that vorpX doesn’t affect your games in any way unless it is running. Also vorpX can’t be running after you uninstalled it.
Yes, that’s the SBS mode vorpX handles.
The way vorpX does it is actually even a bit better than half width SBS normally would be since images are always rendered at full width first and then scaled down to half width when drawing the SBS image, resulting in a 2×1 supersampled image with more preserved detail compared to directly rendering at half width.
As far as the repeated settings change message is concerned please check the thread linked below. TLDR: the issue is caused by a bug in recent nVidia drivers that makes games crash on exit whenever any DLL is hooked into them:
Under normal circumstances, i.e when vorpX can successfully change settings, the game is pretty much plug and play.
Unfortunately this cannot be resolved on the forum.
Please send an e-mail to support at vorpX com with something that helps to verify your order. Either the MyCommerce order id, the name or the mail address you entered into the purchase form would suffice.
Upping this thread since nVidia still hasn’t fixed the issue. Judging from their changelogs they seem to be aware of it as since it also affects their own ‘FreeStyle’ post effects. No sign of a fix yet though…
If you play any game where vorpX changes settings and are greeted with a vorpX message that suggests a restart on each launch due to settings changes, please use the last known working nVidia driver linked below. That will probably fix the issue:
https://www.nvidia.com/download/driverResults.aspx/199654/en-us/
If nVidia doesn’t fix the problem soon, I’ll implement a workaround for vorpX.
The mono/stereo settings are on top of the image page in the vorpX menu i profiles that expect stereo input.
To create an individual SBS profile for a game/app you can try the Basic SBS profile from the cloud. Won’t work with Yuzu though. In that case the destop viewer is the only option.
If it’s a normal screensaver, the executable has the extension .scr. You’d have to search for a .scr file in the install folder of your screensaver. Adding it to the exceptions might be a bit tricky though since the ‘Add exception’ dialog only displays .exe file. You’d have to browse to the folder that contains the .scr file and they type in the file name manually.
Probably a good idea to always exclude .scr files unless there is a dedicated profile for them. I’ll add that for the next beta release.
That’s something I can’t really wrap my head around unfortunately, The desktop viewer actually loads vorpX itself, so failing to attach *should* be next to impossible… Can’t really imagine much more than something getting in the way that also hooks into other programs.
The only suggestion I have is to rigorously disable/uninstall any background apps/tools/utilities. If you happen to have multiple GPUs/monitors, please also check whether the issue occurs with just one GPU and/or monitor.
If you want, send me a trouble shoot data archive. With some luck logfiles help to spot something, I wouldn’t count on it on this case though. You can create a trouble shoot data archive in the config app. Please send it via mail to support at vorpx com.
Try to reduce graphics details a notch, especially things that take a lot of GPU memory. Texture resolution will probably have the biggest impact. Display resolutions in/above the 4K range also start to become a serious factor in that respect.
vorpX as well as the VR runtimes use extra GPU memory. When your GPU memory is fully used, games start to use system memory as virtual GPU memory, which is *much* slower.
Depending on how much memory a GPU has, newer games may almost max out your GPU memory when playing normally already, playing in VR might just be a tad bit too much. Even the 10/12 GB of a 3080 may become tight if you crank everything up in some newer games. By reducing memory heavy graphics settings like texture resolution you can make sure that doesn’t happen. Applies to any game that may potentially max out your GPU memory.
vorpX reads (and later sends) Windows virtual key codes for keys you assign in the gamepad mapper. For the arrow keys that would indeed be 37-40 decimal.
Just a theory: maybe KOTOR directly evaluates hardware scan codes and somehow mangles the virtual key codes into something else. Really just a guess though. Maybe there is an external gamepad mapping app that can handle a (fairly weird) edge case like this, but for vorpX that would be a bit too much.