Forum Replies Created
-
Posts
-
The profiles are stored in a database under C:\ProgramData\Animation Labs\vorpX. You shouldn’t tinker with that though. Profiles have their own versioning system, replacing the database at best will cause newer profile updates to become unavailable and at worst mess things up entirely.
The right way to backup/restore settings and profiles is via drag and drop from/to the ‘Local Profiles’ list in the config app. That way they are imported/exported in a version-aware fashion.
Note that for official profiles only the user settings are saved to disk that way (.vps), while for custom profiles the entire profile ist written (.vpp). This distinction makes it possible that A. older user settings for official profiles can be restored even in cases where the underlying ‚system‘ part has been updated in the meantime due to profile breaking game updates, and B. I can update official profiles without breaking changes you may have made to your settings for a game.
Sounds as if your Windows is messed up somehow. Since several years the profile database is stored in a shared ProgramData folder (usually C:\ProgramData) that is shared across all accounts. Both the config app and the actual vorpX request the actual location via built in Windows functions. If these functions point to the virtual store in your user folder when requesting the shared ProgramData folder, something is seriously wrong.
If I had to guess, I’d say for some reason there might be no write access to C:\ProgramData for the user in question. Just a guess though. Either way, under normal circumstances the database would definitely not be inside the virtual store.
Das geht auch, dazu kannst Du im Menü die ‘Play Style’-Option auf ‘FullVR’ stellen. Das Menü öffnest Du mit der ENTF-Taste.
Gibt da allerdings etwas SEHR Wichtiges zu beachten: Damit das nicht merkwürdig verzerrt/hereingezoomt aussieht, muss das Kamera-Sichtfeld (field of view) größer sein, als es normalerweise bei Monitor-Spielen ist. Für rund 150 Spiele kümmert sich vorpX automatisch darum, aber für andere muss man das selbst machen.
Hilfreiche Tipps (und Workarounds) dazu gibt es hier:
http://www.vorpx.com/forums/topic/how-to-get-the-most-out-of-vorpx/
oder hier in der etwas holprigen Google-Übersetzung:
Außerdem noch in der vorpX-Hilfe, die kannst Du in der Config-App ansehen. Unter ‘1-2-3 Game-Setup’ ist Schritt für Schritt eine zwar nicht optimale, dafür aber schnelle und einfache Methode erklärt.
An updated profile that restores G3D support is now available, you should receive a profile database update next time you launch vorpX. If that fails for some reason, you can grab the profile manually from the cloud profiles page in the config app.
Note that full support for the Game Pass version will have to wait until the next vorpX update, the Steam version however should work as intended again with the updated profile.
(Was) broken indeed. Thanks for the heads-up. Since this issue also affected a bunch of other older DX9 titles, it was severe enough to warrent a quick hotfix. I didn’t bump up the version number, so no auto update, but reinstalling with your web installer should get you a version that brings back G3D in Far Cry 1.
if you didn’t keep a copy of the installer, you can get a fresh link here: click.
Per default the motion controllers should act as gamepad in the first place, so you should always see the gamepad prompts in the game when using motion controllers. If not, something is defintely wrong.
Please first check whether you maybe accidentally changed the motion controller mode to keyboard/mouse in the mod’s options menu. if so, switch back to gamepad.
If that is already the case or does not help, check whether you maybe have any external tools running that potentially hook into game input. Disable *every* extra tool/utility you may have running in the background.
Lastly check your controller settings in the game’s Steam properties. Should be ‘Use Defaults’. Someone had a similar problem earlier, turned out they had tinkered with that setting. Unlikely, but maybe you did the same.
I don’t really have the time/resources to officially support 3D-displays, hence the according hint whenever you start the game. I do what i can to help, but as far as trouble shooting more weird issues is concerned, I can’t really help much. Sorry.
If you have both a TV and a monitor connected to your PC, try with only the TV. While vorpX can try to force games to a specific display there is no guarantee it actually can, so multi-monitor setups of any kind may not work under all circumstances.
Any headset that works correctly with either SteamVR or OpenXR automatically also works correctly with vorpX. So the the question you should really ask is: how good is the Pico’s SteamVR/OpenXR support?
2022/11/10
Version alpha 8 is now available. This update adds compatibility with Cyberpunk 2077 1.61.
Faster than expected, luckily everything required for a new C++/game scripting communication method was already largely in place on the vorpX side, so the hardest part was figuring out what caused the issue and coming up with an idea to deal with it.
Latest version available here:
DownloadDoesn’t work currently. The latest version of the Cyber Engine Tweaks modding framework comes with changes that break the communication between the C++ and the game script portion of the mod. I have to figure out something new in that respect. Might take a few days.
Just a little heads-up that Geometry 3D is currently broken for both versions since the latest game patch. For the time being please switch to Z3D in the vorpX menu.
I have to redo parts of the profile to make G3D work again, I’ll let you know here when an updated profile is available (hopefully before the weekend).
Awesome.
I don’t think there is much of a difference to any prior profiles you got working with SBS 3D.
Was just a bit difficult to find a base profile with SBS input enabled. The general purpose SBS profile is mainly intended to make that easier. Works with all supported APIs, i.e. DX9-12, as well as OpenGL.
Only the Steam version is supported currently. The Game Pass version apparently uses a different .exe.
You can try to make a copy of the profile and then add ‘Project76_GamePass.exe’ to the newly crewated profile. However, some GamePass games aren’t hookable, so there is no guarantee.
IMPORTANT: while the basics *might* work that way, advanced DirectVR features (memory scanner tracking, FOV etc.) that the profile comes with would be broken for sure. Also it’s quite likely that shader definitions for the scalable HUD, shadow handling and so on don’t work.
I’ll check out the Game Pass edition before the next vorpX update, but for the time being I’d highly recommend to use the Steam version, even if you can make the Game Pass version work in principle with a profile copy.
You can create a trouble shoot data archive with logfiles and some basic system information in the config app. Not really sure whether it will contain anything useful in respect to your issue, but when you send it as an e-mail attachment to support at vorpX com, I can check whether there is something unusual.
There is a regular profile for D2X-XL, which works fine.
If you still want to try dxx-rebirth:
I uploaded a general purpose SBS 3D base profile to the cloud. Should work with pretty much anything that has native SBS (or Over-Under) 3D output.
- Download the ‘SBS 3D Base [vorpX]’ profile from the Cloud Profiles page in the config app.
- Switch to the Local Profiles page and make a copy of the downloaded base profile
- Assign d1x-rebirth.exe to the copy.
Caveat: There is no 100% guarantee that creating profiles that way works. I briefly checked the regular non-stereo dx1-rebirth with the profile, which seemed to work when run windowed. Freezed on launch in fullscreen mode though.