Forum Replies Created
-
Posts
-
The current vorpX version has flawless G3D with both DX11 and DX12 using the latest game version. Just make sure that the 3D-method stays at its default (DirectVR). Caveat: camera mods may interfere.
I added a profile for the game. You should receive a profile database update next time you launch vorpX. If not, you can grab the profile manually on the cloud profile page of the config app.
Steam should just work, GamePass requires an additional step:
The automatic hook helper installation fails currently for the GamePass version. Will be addressed in the next regular vorpX update, until then please manually copy the dxgi.dll file from the link below to [Your Forza Horizon 6 Folder]\Content
https://www.vorpx.com/share/7743-2761/dxgi2510.zip
the password for the ZIP file is ‘vorpx’ (without quotes).
Just in case you didn’t check that already: make sure that the game actuall runs at the desired resolution in the game’s graphics/video options.
I uploaded a an updated profile to the cloud (Config app > Cloud Profiles).
Caveat: Only the D2X-XL port is covered, other ports almost certainly either won’t work at all or have no stereo 3D.
That sounds weird for sure. Try this workaround. Afterwards you should see the A/E label above the screen right away.
- Paste this address into your Windows Explorer address bar and hit enter: %ProgramData%\Animation Labs\vorpX
- Open ‘extra.ini’ with a text editor (e.g. Notepad)
- In the [StartRoomFinished] section add ‘your-game.exe=True’ (without quotes). Caveat: your-game.exe must be the main game .exe that vorpX actually hooks into, not a potential launcher.
At the end of the tutorial screens a blinking label should appear on top of the screen that displays the keys/buttons (A/E) to enter the game.
You can add programs to the exclude list in the config app.
If an app doesn’t hook fully, you can do that comfortably from the trouble shoot dialog that the ‘Attaching to…’ hint morphs into after a while.
If an app actually uses DirectX and thus hooks fully, the easiest way is launching it with the watcher paused and then add it via the ‘Add Process’-button in the config app on the ‘Excluded Programs’-page. If you know where it is installed, you can alternatively use the ‘Add File’-button instead and browse to the .exe in question.
Default Windows apps and Office folders where Teams normally is installed get auto excluded completely though. Maybe they differ on your machine.
Different list. When geometry gets drawn both a vertex and pixel shader are active (actually to be precise often more than that, but those are the only ones we care about here), so both can be utilized do define special stuff.
Usually it’s best to start with vertex shaders, especially for HUD or shadow. Try pixel shaders if that doesn’t work, e.g. because it catches too much. Effects like unwanted DOF, motion blur etc. on the other hand are often better manageable via pixel shaders. Very different from game to game though. The only useful universal rule is: try vertex first.
In case of Fallout 76: if nothing has changed in a recent update, all HUD elements – at least those I am aware of – should be definable via vertex shaders.
I’ll look into it, thanks for the heads-up.
BTW: If you don’t want to wait for fixes after a game update has broken stuff like this, you can usually fix it yourself. That’s quite easy:
- Enable shader authoring in the vorpX config app (General page).
- Ingame press ALT+END to open the shader authoring menu.
- Flip through available vertex or pixel shaders to find the HUD shaders.
- Add found HUD shaders to the known shaders list and mark them as HUD.
- Save the settings.
Klingt, als hättest Du entweder die Meta Horizon Link PC-App gar nicht installiert oder Horizon Link in der Quest nicht gestartet.
https://www.meta.com/de-de/help/quest/1517439565442928/
Außerdem muss Horizon Link in der Quest gestartet sein, damit die PC-App die Quest verwenden kann.
Falls Du eine halbwegs sinvolle Antwort haben möchtest, müsstest Du ein klein wenig mehr Information liefern:
1. Um was für ein Headset handelt es sich?
2. Grobe System-Specs: CPU/GPU, Windows-Version, Laptop ja/nein etc.
3. Was genau heißt ‘alles ausprobiert’?Make sure you run the DirectVR scanner as indicated by vorpX. Once the scanner ran successfully, you can use your motion controllers in gamepad mode (should be the profile default).
The kb/mouse emulation before running the scanner is only necessary because the game doesn’t support simultaneous mouse/gamepad input and vorpX needs to emulate a mouse for head tracking.. After running the scanner vorpX accesses the game camera directly for head tracking, which provides better head tracking and also let’s you use motion controllers as gamepad since vorpX doesn’t have to simulate a mouse anymore for head tracking.
That aside shift mappings work fine here. Just in case: If you use some third party VR runtime to send the image to the headset, try Meta Link to check whether maybe the runtime is the culprit.
Thanks for the heads-up. That can happen after game updates whenever the update changes shaders. Fixed right away, you should receive a profile database update next time you launch vorpX. If not, you can manually download the updated profile in the config app.
Let me know whenever you encounter something like this. Can’t promise it will always get fixed *that fast* though.
That’s an inherent side effect of how Z3D works. Instead of rendering everything twice like G3D, it shifts pixels of the final image to the left and right based on how far a away from the camera they are. That leaves some ‘holes’ in the image, which are then filled with neighboring pixels. Those are the halos you noticed.
You can play around a bit with the 3D-Strength and (after clicking the ‘More Z3D Settings’-button) the advanced Z3D options to check whether you find a balance that fits you better than the default, but there is no way to get rid of the effect entirely. The stronger the 3D with Z3D the more pronounced these halos become.