Forum Replies Created
-
Posts
-
There is an option on the DirectVR page of the menu that lets you disable looking up/down only with the headset.
Not recommendend though. Really. Not. Pretty much every VR game ever made only allows looking up/down with your head and not with a gamepad/controller to ensure that your real world horizon and the VR horizon always match. When both do not match playing in VR can become pretty uncomfortable.
Odd. Using a 21:9 monitor on my main dev machine myself. Changing the aspect ratio of the actual display should not affect the virtual monitor. Can’t say anything useful currently, but I’ll try to replicate the issue. Thanks for the heads-up. If you don’t want to use the virtual monitor, you can disable it entirely in the config app.
Unrelated sidenote: should you incidentally encounter a supported game not launching with a required DirectX version, it might be worth a shot not to ignore warnings related to disabling automatic settings. As these warnings suggest, disabling automatic settings can (and often does) break important stuff.
Please 1. try to reset the the controller option in Cyberpunk to default and 2. make sure that Cyberpunk is running in the foregroung, e.g. by clicking into its window once.
Using the KB/mouse emulation may be a workaround, but the default gamepad mode is heavily recommended for various reasons in this case.
I understand your frustration, but that’s a bit out of line, don’t you think? Considering that you installed vorpX without hitches in the past and that noone except you experineces these difficulties at this point, unfortunately there simply is nothing else to suggest than what was suggested already.
I’m not exactly sure what kind of recommendations you expect, but since this very obviously is neither an issue of the installer nor a problem on the server side, your best course of action is probably to revert your setup to the state from before this issue started to occur for you. Only you can know what you changed between the last time(s) the installer worked for you and now.
If you haven’t done that already, you might want to try the latest cutting edge build. If that also doesn’t work, at least you know it’s definitely an issue with your machine/home network. If it works, the issue probably originated at your ISP.
The hotkey settings in the config app are for your keyboard/mouse, not the motion controllers.
The two grip buttons are currently hardcoded by design to ensure everything works right when profiles are exchanged between users/setups with different motion controller types. Considering that everything is gravitating towards the Oculus/Meta layout these days, that *may* change in the future, but right now it’s too early for that. Cross device profile compatibility is still too important.
You can freely remap all other buttons except these two on the motion controller page of the vorpx menu.
Two things:
1. Reset the game’s graphics options to medium before launching it with the mod. certain graphics setting like DLSS may interfere with the mod.
2. the mod uses the CyberEngineTweaks modding framework. Since each version of the CET unfortunately only works with the Cyberpunk version it was made for, you have to make sure that both the mod and your Cyberpunk are up-to-date.
Unrelated, but while am at it:
Once you got it working, make sure to actually read the instructions that are offered to you in the headset on launch. That’s time well spent. Hectically clicking stuff away just makes things less enjoyable. :)
Spamming the forum with the same issue all over the place won’t get you better help, makes any discussion re the issue impossible to follow and ultimately the forum unusable. Hence your other posts have been removed to keep everything related to your issue in the same place.
There have been zero other reports like yours recently, the original post here is more than 9 years old… Obviously this has to be an issue on your end or somewhere in between the server and you. Doubly so considering that you installed vorpX without hitches several times in the past.
Please double and triple check everything that I suggested. As much as I’d like to add something entirely different to these suggestions, unfortunately there just isn’t anything else to suggest than that. Thanks again for your understanding.
As said in your original post, there is neither an issue on the server side nor with the web setup program, which hasn’t changed in years. As you can probaly imagine there would be a lot more reports like yours every day othgerwise.
All that can be recommended has been recommended already. Again in short for your convenience, just in case you missed something:
1. Check that no firewall setting prevents the download
2. Check that no antivirus program blocks the download
3. Try to use a mobile phone as hotspot, just in case the issue originates at your ISP
4. Since you already downloaded vorpX sucessfully earlier: revert any changes you made to your PC since the last time you downloaded vorpX.Nothing else to recommend besides these things. Thanks for your understanding.
Please follow these steps:
1. Download and install the Meta Quest (Oculus) PC-App from the link below.
2. Make sure Oculus is selected in the vorpX config app as your headset type.
3. If you want to use the wired Link, connect the Quest via USB
4. Launch the Meta Quest Link PC App.
5. Launch Quest Link (wired) or AirLink (Wi-Fi) in your Quest.Afterwards your Quest is connected to the Meta Quest Link app and vorpX can send images to it via the Meta Quest PC runtime.
Caveat: AirLink requires a fast Wifi 5/6 connection with low latency. If you are unsure about that, better use wired Link via USB.
The exclude list is the way to go here.
You can however easily pause vorpX entirely from its tray icon’s right click menu. if you can’t see the tray icon, click the little arrow to the left of your taskbar clock.
Might be some annoying AV program’s fault. if you happen to use anything else than Windows’ built in Defender, get rid of it.
Thanks!
One additional hint: After years of (on and off) searching for some mysterious vorpX bug that only materializes in the original Bioshock 2 and a handful of other 32bit DX9 games, I’m pretty sure I recently found the actual issue while I did some general memory optimizations: too much memory used with vorpX.
For the GOG (not Steam unfortunately) version that can be fixed by making the game ‘large address aware’, which raises the 2GB RAM limit 32bit applications usually have to 3GB. The same fix also works for Dragon Age Origins btw., which has similar random crash issues without being large address aware.
A simple patcher can be found here for example:
https://www.techpowerup.com/forums/threads/large-address-aware.112556/Note that trying this fix only ever makes sense for old 32bit games, newer (64bit) games will never need this.
@ Mihalytabornok :
Please ignore any potential recommendations that involve manually tweaking resolution/FOV for this game. Reset the profile to default in the config app and let vorpX do its thing. It knows what it does. Manual tweaking is not necessary for this game, you gain nothing by it except extra work.
The resolution can be changed directly in the vorpX menu up to 2400p. vorpX auto chooses the best aspect ratio and sets the precisely calculated FOV. No need to manually adjust any of that at all.
it‘s always good to learn how to set things up manually for games where vorpX can‘t do it automatically, but whenever it can, it’s usually the better idea to take that offer.
Important:
If you haven’t done that already, make sure your PC can handle resolutions up to 2400p, either by adding custom resolutions (see the vorpX help for detailed instructions) or with the new virtual monitor in vorpX 24.1.0 (link on the front page).
I don’t have any other answer to your question than the one I gave you three times already. Sorry and thanks for your understanding.
It someone else said they got G3D with DX11, please ask them for instructions. The official profile for sure doesn’t, which is why – again – vorpX automatically configures everything to make it work without you having to worry about any of that.