Forum Replies Created
-
Posts
-
The game is out since two or three days. Can’t really say much, I haven’t checked it yet.If you want to try the FS2019 profile as a base for creating a custom profile, you’ll have to run FS2022 with DirectX 11. As far a I’m aware FS2022 has both DX11 and DX12.
UPDATE:A preliminary profile that doesn’t require any DX11 .ini hacks can now be downloaded on the ‘Cloud Profiles’ page of the vorpX config app, it’s called ‘Farming Simulator 2022 [vorpX]’.
That’s not something vorpX can do, but there are two tools for displaying desktop windows within games: OVRDrop and DailyOVR.
Caveat 1: I never tried them, and have absolutely no idea if or how well they work together with vorpX. But it’s worth a shot.
Caveat 2: Both are using SteamVR IIRC, so you will have to use vorpX in SteamVR mode, which depending on your headset might not be 100% ideal.
You shouldn’t have to set up anything besides what is mentioned in the top/left corner of the game window. If you already tinkered with settings besides that, please reset the profile to default in (either in the config app or the vorpX ingame menu) and then just follow the instructions.
If ‘nothing but problems’ refers to the black bars above/below the image: that’s unavoidable in this case unfortunately. The game’s camera field of view can’t be set high enough to match the headset FOV without these bars.
Thanks for the hint.
I tweaked the depth buffer heuristics a bit. As far as I can tell it should work now regardless of the shadow resolution.
BigScreen captures the 2D image as shown on your desktop. That’s literally several orders of magnitude less complex than vorpX in 3D mode, where it not only replicates huge parts of the supported 3D APIs, but also has game specific profiles that take hours, sometimes days, to create in itself for every supported game. Not even remotely the same thing. And that’s not even considering things like head tracking, the various DirectVR functions etc.
You can do the same with the vorpX desktop viewer, which comes as a freebie alongside vorpX:
- Start the vorpX desktop viewer
- Pause the vorpX watcher, so that vorpX doesn’t try to hook into games anymore. (tray icon right click > Pause Watcher)
- Make sure to run games windowed or ‘borderless’
BigScreen is just a desktop capture app. You can do the exact same thing with the vorpX desktop viewer by pausing vorpX (tray icon right click > Pause Watcher) while the desktop viewer is running.
My bad, sorry for the confusion. Should work now.
The changes were made with my latest dev build originally, which uses a higher profile version number than the current release build. Hence you couldn’t grab the updated profile from the cloud and instead just redownloaded the one you already had…
Re-created and re-upped with the right profile version number for the current release build now. Note that the scaled HUD that I mentioned above doesn’t work. That’s a bug. Will have to wait until the next vorpX update.
vorpX has FSR built in since the last version, implemented in the ideal fashion directly into vorpX’s existing image processing pipeline instead of just slapping pre-built shaders on the final output. Adding a very similar second solution for doing essentially the same thing may happen in the future, but at this point is not a priority.
http://www.vorpx.com/vorpx-21-3-0-released/
http://www.vorpx.com/forums/topic/anyone-still-looking-for-a-good-upscaler/#post-206907
Since this is beneficial info for everyone trying to create profiles for games that can’t handle simultaneous mouse and gamepad input – and as you noted also a fairly common source of confusion, I’ll leave the thread here.
vorpX comes with a fully configurable built in gamepad > mouse/kb mapper. That’s the solution for using a gamepad together with mouse based head tracking whenever a game can’t handle native gamepad and mouse at the same time. In official profiles it typically is enabled if necessary, but if you create a profile yourself and discover a game can’t handle simultaneous mouse and gamepad input, you have to configure it yourself.
You can enable it on the Input page of the vorpX menu, the option is called ‘Xbox Gamepad Override’. You can either override everything (Full) or sticks and buttons separately (Partial). Most of the time a full override will be necessary, but if you’re lucky just overriding the offending stick can suffice occasionally, which – if it is enough – spares you the button remapping.
Once configured the gamepad essentially acts as mouse/kb, so mouse based head tracking and a gamepad can be happily used together even if a game itself doesn’t support that.
The way vorpX hooks into games is a bit time sensitive. Although I haven’t encountered that myself for quite a while, it’s not entirely impossible that there is still one or the other game where successful hooking appears to be seemingly random. Sounds a bit like that could be the case here.
If you see the ‘Attaching To…’ dialog during an unsuccessful attempt, leave it open for a minute or so, it will then display some trouble shooting options. The first one (‘Install hook helper’) should be able to resolve timing related hooking issues.
ScriptHook is only loaded when the mod is active. After renaming vpxGTA5.dll it is not required anymore and vorpX works as it did before the mod got added. I wouldn’t really recommend to play online, but technically it should be possible again that way.
You don’t need to apply profiles. Profiles that show up in the ‘Local Profiles’ list are already loaded.
Apart from that: If you can’t solve the issue after thoroughly going through the trouble shooting guide, please create a trouble shoot data archive in the vorpX config app (trouble shooting page) and send that to support at vorpx com. Maybe your logfiles/system config show anything that can help.
Just checked this for you to be sure there haven’t been any profile breaking changes. Should work fine with default graphics settings. I used a freshly installed Steam version without any changes aside from the resolution.
You can restore the game’s graphics settings to default in its options menu.
If for some reason that doesn’t help, switching zu Z3D instead of Geometry 3D would be a potential workaround.
Edit: Turning on antialiasing in the game options seems to be the culprit. Forcing AA via the GPU control panel instead appears to work though, so you can try that instead.