Forum Replies Created
-
Posts
-
As everyone should, I have a habit of not answering questions that start with “So…”, but for you I make an exception from the rule. :)
I was somewhat distracted by real life matters for quite some time recently (good ones, so nothing to worry about). Life is slowly shifting back towards me being your usual ‘vorpX guy’ for the most part now though.
The next version will be out in the not too distant future.
Each CET version only works with the Cyberpunk version it was made for. You either need the CET for Cyberpunk 1.5 if you still have that installed, or wait until I have the mod update ready that works with Cyberpunk 1.6.
You have to run vorpX in SteamVR mode to use it together with Virtual Desktop. VD only supports SteamVR for PCVR-Streaming, not the native Oculus runtime.
You can switch vorpX to SteamVR in the config app on the ‘General’ page.
Quote from a few posts above yours. :)
Will check this as soon as possible.
The issue has already been located in the meantime actually. Still needs some testing, but if nothing unforseen happens, a new build should be available shortly. Mind the *if* though, sometimes unforseen things actually do happen.
The game recently received a huge update that broke vorpX support. There is a fairly easy way to fix that though:
1. Right click the game’s entry in Steam’s game list
2. Click ‘Properties’
3. Go to the ‘Betas’ page
4. Select the ‘dx11 – non-rt’ beta (which is actually not a beta, but the original game version)Still didn’t have a chance to check this, sorry guys. I’m preoccupied with real life affairs currently (good ones, so nothing to worry about). In a few days I expect to be back at being mainly the vorpX guy. :)
Will check this as soon as possible.
You can install it manually, both the 32 (x86) and 64bit (x64) versions are required:
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
I‘ll check this over the weekend. If the patch doesn‘t mess up things entirely (i.e. changes how mod scripting works) it should suffice to update the CET modding framework as soon as a version for patch 1.6 becomes available.
Just follow the instructions in the link below and *probably* the mod will work again:
https://wiki.redmodding.org/cyber-engine-tweaks/getting-started/installingBetter safe than sorry. :( I haven‘t decided yet how to deal with the matter in the long run though. Actually I wouldn’t have done anything if vorpX (as well as other RDR2 modders) wouldn‘t have been explicitly dragged into the whole mess by one of the involved parties, which somewhat forced me to become extra (probably over-) cautious.
I uploaded a yet another build, which at least for now also works again on Windows 11. Please reinstall using your web installer to get it. Looks as if my earlier concern that this might be some new Windows 11 “feature” is correct… I’ll try to figure out the root cause.
Just to be clear: absolutely nothing that vorpX does is even close to being “potentially unwanted”, malicious, harmful or anything else some AV program may come up with to frighten its users. All it does is injecting itself into other programs similar to many, many other programs, which obviously is necessary for vorpX to work.
To avoid issues like this altogether add the vorpX program folder to the Defender exclusion list. Usually that would be: C:\Program Files (x86)\Animation Labs\vorpX
When I tried the game shortly after release there was some really weird issue with establishing the main hook into the game unfortunately. :( Probably not unsolvable, though. No promises, but I‘ll take another shot on occasion. A lot has changed since back then, so it‘s definitely worth another try.
Still working fine here with the latest version, neither a hook helper nor alternative hooking are required. Just in case: The ‘DX11 Legacy’ renderer is mandatory, that’s the only one that works with vorpX.
If the trouble shooting options don’t help, there probably is some more severe conflict with another program on your PC. The trouble shooting guide on top of this sub forum has more details on the matter.
That’s weird. vorpX does make a few changes to the config file, but they (obviously) shouldn’t prevent the game from launching. Would be great if you could send me your vorpX-adjusted config files so I could check whether I can replicate the issue here.
Please browse to [Documents]\My Games\FarmingSimulator2022. The files vorpX adjusts are game.xml, gameSettings.xml and inputBinding.xml. Please send these (after vorpX changed them!) as an e-mail attachment to support at vorpx com.
What you can try yourself is disabling automatic resolution handling on the DirectVR page of the vorpX menu. With a bit of luck that resolves the issue. Let me know if it does.
As a very last resort you can disable automatic settings changes there altogether. Only do that as a very last resort though. Some of the changes vorpX applies are vital for the profile to work as intended.
Some automation tool might indeed help if the game doesn’t have a way to change the default behavior. I found this Reddit thread where someone talks about using Autohotkey, but I’m not sure whether they were successful.