Search Results for 'update'

[Ralf]

If you have any problems hooking one of these games, and happen to be on 24.1.0, please roll back to 21.3.5.

General hint:

When suddenly something doesn’t work that did work before while there hasn’t been any vorpX update, either a game update broke something or a change on your PC did. In this case it’s the latter for sure.

[tjpblue]

First off many many thanks,

The running in the foreground issue was something I had considered, though not exactly sure of the cause and effect. Though frustrated , I’m also amused right now because it did this as after I did the CET update and Microsoft framework update as well. I figured I didnt know what I was doing, reinstalling, rereading one word at a time and making sure I didnt misinterpret or miss anything. In essence it was probably good to go, just perpetuating this weird issue – but I am still incredibly grateful for your standalone update as it allows for me to narrow things down…. and you make good software :)

As far as clicking on the window , Im assuming you mean- the game on the actual desktop , to ensure Cp2077 is in the foreground. Will look into this as well.

Im fanatical about expunging bloatware, and do not over AV my system like at all, but one detail you mentioned caught my attention. I had programmed a steering wheel/pedal setup to work with the game while driving. And I am going to look into this today-Though its not being used at the moment (to simplify troubleshooting) Basically a driver and x360ce which at this moment im targeting as potential suspects.

Though my issue is probably one in a million, if I find out a solution I will post on the off chance someone else struck by a unicorn as well.

Thanks again,
TJP

[Ralf]

You can indeed ignore the version warning. I just forgot to change the version check before uploading the update. Thanks for the heads-up.

Concerning your issue the only two things I can really think of here is that either the game isn’t running in foreground and thus doesn’t have input focus. That could be remedied by clicking into its windows once.

The second, option would be some input releated app running in the background that interferes. Some extra annoying AV programs might e.g. try to protect you from keyloggers for example. So if you happen to use anything else than Windows Defender, get rid of it. Windows Defender will kick in instead. Also maybe some hardware vendor fluff-/bloatware, e.g. from Razer or Logitech might potentially get in the way, although that isn’t very likely.

[tjpblue]

What I’m working with:

QUEST 3, i9, 32gRam, 4070 RTX
– COPY of Updated Vorpx CYBERPUNK Standalone mod dated SEPT 2024
– Copy of CYBERPUNK 2077 2.13 + Phantom Liberty

Everyone remembers what happened the dreadful week of the the infamous 2.13 update drop.
Many solutions were sought. Many things wouldn’t work no matter how closely defined my actions were to the instructions concerning CET and the like.

I was ecstatic that Ralf powered by Vorpx, or rather Vorpx powered by Ralf – was quick to update the stand alone mod and link. In my neck of the woods internet is non existent so after installing and and reinstalling with fixes in different combinations and orders it took forever each time I got exhausted – you have no idea how slow of a connection lol
I looked forward to downloading CP2077 what I thought would be the final time and began to install the new updated standalone {all smiles}.

Unfortunately I was stuck in the game waiting room , with the same message of “my version of cyberpunk being newer” ..etc etc. Realizing it could be a false message (see above if it linked properly) I sought to continue : However I noticed that I wasn’t able to use either the keyboard or Quest 3 controllers to continue. I was able to use the grips to use the vorpx configuration menu ( open and close the menu) – that was it. I changed a few settings in vorpx menu – gamepad back to keyboard etc – Mouse was only working in vorpx menu. upon closing the menu AND after the opening intro movie I would get a message saying {!} CONTROLLER DISCONNECTED Please Reconnect controller.No controller buttons or keyboard would work (other image if posted correctly)- I Never post to Forums, as most threads seem a spiral into condescension to the poster -Among other things Im embarrassed I cant figure this out – and reading comments on videos expressing that it worked first try no fuss no muss – Im pulling out what 3 hairs I have left on my head. Ive tried everything – I, in my heart think its got to be something I’ve overlooked, or accidental setting change.
**Headset selection on The –CyberpunkVR config link — oculus headsets , rift , Quest via Oculus link is selected** (I’ve always used questlink for this game with unfailing great results)

If anyone can Help, I would owe you my soul.

Thanks in advance,

TJP
A Tenacious enthusiast even after a wrong turn or two

[Zel1984]

I just tried to start VorpX & suffered the same problem so looks like i was wrong, downloading & repairing using the link you provided did not fix my problem, i think there was a recent oculus/meta driver update, maybe that has something to do with it.

[bjr84]

UPDATE!!!

GOT IT RUNNING NICELY with the FF7 Remake cloud profile (the one noted as ‘DO NOT USE’).

Looks glorious!!

Best,

Ben

[Zel1984]

After a windows update when i tried to start VorpX (24.1.0) my screen would just go black, no error messages or anything & i would have to restart my computer, just installed the x86 & x64 versions linked by Ralf above & it is working again so the culprit seems to be a recent windows update that was causing the issue for me.

[Ralf]

An updated installer including the latest Cyber Engine Tweaks modding framework for Cyberpunk 2.13 compatibility is now online. Download link as usual in the first post of this thread.

[Spinelli]

Ralf wrote:

Sorry for the spam detection troubles you encountered. The alternative to having spam detection on in the forum software would be a 3:1 spam:content ratio unfortunately, extra bad since the beautiful invention of drivel bots like ChatGPT etc.

Your actual issue:

Maybe some weird issue related to Pimax’s software that puts itself in between vorpX and the headset. Reversed eyes are conceptually impossible with vorpX’s G3D method (at least unless the profile author intentionally inverted them, which obviously isn’t the case here).

Possibly related to the time vorpX hooks into the game (before or after Pimax initializes its stuff). Enabling alternative hooking in the config app may be worth a shot. That aside maybe check whether there is some stuff in the Pimax software you can turn off. Haven’t checked a Pimax headset in a long time, but a few years back they had some custom reprojection that could change the IPD and make things appear cross-eyed occasionally.

vorpX does not change the power plan. Some VR runtimes do howewer. At least the Meta (Oculus) runtime does. Not sure about Pimax.

OK, update.

Starting Game Consistently

It looks like I have VorpX, rFactor, and SteamVR consistenly playing good with eachother. I just try to start them in the following order: PiTool, VorpX, SteamVR, and reversed order for closing, and also I make sure to always close SteamVR (not Steam as a whole) once I’m out of any game along with starting the games from PiTool (which automatically opens SteamVR). Some of those steps may not be neccessary but the formula seems to work every time. I also make sure not to alt-tab out of the game. This caused issues last time with the SteamVR grid-environment being superimposed in the rFactor game and led to other issues too (had to end up closing game from task manager and then restarting all VR-related programs/services).

Parallel Projections

I forgot that Pimax’s Parallel Projections is a requirement for VorpX. It says right in the VorpX Pimax guide (which I’ve read multiple times). 3D is fine now

Remaining Issues

1. I still can’t get the head-movement to work without the entire game’s screen being locked to my head (unless I run in 1 of the interactive movie screen modes or whatever which). If I enable head-tracking, the entire screen is still locked to my head but, mixed with that, there’s a teeny, tiny but of proper head movement relative to the locked screen but it’s like 3% of the entire head movement compared to the locked-screen’s head movement.

If I enable the game’s mouse free-look setting, the camera / driver’s head suddenly looks upwards while spinning and falling to the ground.

If the game supports TrackIR / head-tracking (like rFactor and all games based on it’s engine), do we just rely on VorpX’s head-tracking being enabled? Or is the game’s mouse free-look setting supposed to be activated instead (via a game’s hotkey)? Or are they supposed to simultaneously be enabled/activated?

2. The 3D is basically perfect – the ISImotor (commonly referred to as the ISI GMotor) engine that rFactor runs on has always been one of the best native Nvidia 3D Vision games anyways so I’m not surprised – however there’s one issue. Lots of the vehicles’ in-car dash’s gauges (or on the car’s dash, steering wheel, etc.) are almost impossible to look at as they’re being rendered in only 1 eye but not the other (or sometimes only partially in the other eye). It’s extremely disorientating and headache inducing even if you don’t look at it.

This issue used to only occur with games running on the ISImotor engine if the particular game didn’t have a 3D Vision profile assigned to it. The fix is incredibly easy. With Nvidia Inspector in the Stereo section, make sure “StereoProfile” is set to “Yes” and “Stereo TextureEnable” is set to “0x00000001 COMMON_STEREO_TEXTURE_ENABLED”. After that, all the games’ cars’ dashes, gauges, display screens, etc. were fixed and PERFECT.

The problem is, there’s no more “StereoProfile” setting in Nvidia Inspector, and the “Stereo TextureEnable” setting only has literally one option to choose from: “0x00000001” (no writing after it). I know Nvidia removed 3D support from their drivers but I thought simply enabling these “bits” in Nvidia Inspector would still be available.

[Ralf]

Just a heads-up that G3D for the new WoW DX11 renderer will work with the next vorpX version. Required quite a few changes to the vorpX codebase, so no way to address this with just a profile update.

Until the next vorpX gets released, WoW G3D support is limited to WoW Classic, which as of today still has the ‘DX11 Legacy’ renderpath.

[Military_freak]

I’ve been working to get VorpX working with Star Citizen by following the path started by Chachi_Sanchez and his discord. However, I’ve run into a wall due to Star Citizen crashing while attempting to hook to VorpX. The error itself presents as a 0xc0000142 error, and looking it up in the Windows Event Viewer, I see the faulting application is vorpControl64.exe or vorpControl64.exe and the faulting module path is ntdll.dll in system32.

Attempting to run Star Citizen without a hook helper allows Star Citizen to launch properly, but does not hook to VorpX and therefore doesn’t launch in VR. Running Star Citizen with a hook helper installed through VorpX, though, causes the 142 crash.

I’ve attempted to re-register the dll, I’ve updated C++ dists, I’ve even done a Windows 11 re-install and reinstalled Star Citizen, but the error still remains.

Does anyone have insight that might help?

Thank you in advance for any assistance.

[bravekat]

I cant use the official Vorpx Starfield profile in vorpx 24.1.0 because the Z3D turns OFF/ON when close to objects, so I made a vorpX 21.3.5 Starfield profile from Resident Evil Village that works in Cinema mode/3rd person view. You could downgrade your vorpx version to 21.3.5 and try that profile to see if it works.

Beware though once you downgrade/upgrade Vorpx versions, you wont be able to install the beta again.

I also have a new problem with Starfield since the new update, unrelated to vorpx, in which I can not see planet textures. Hopefully this will be fixed in a future patch.

[dellrifter22]

Ralf, any chance you’ll be looking at this one?

RE8 seems to be the best dx12 profile tested for stable Z3D, but the depth effect seems to be a bit off center and not aligning correctly with the character/objects. I’ve tried multiple aspect ratios, window/fullscreen and DLSS/AA variations, but it wont shake the problem.

On a side note: I came back to Stafield after their big update, but the Z3D seems to cut out quite often in interior spaces. I was using the latest vorpX profile. Hopefully that might be fixable as well. The RE8 profile used to work great until Bethesda patched in DLSS.

[Ralf]

If the D3D11 Legacy option had been removed, you’re out of luck for the time being. At least as far as Geometry 3D is concerned. The other D3D11 renderer doesn’t play nice with vorpX. I’ll take a look at it for the next vorpX update, but no promises.

[SugoiNL]

Thank you for reply. I am only using Windows Defender and haven’t used anything else recently.

It looked like it happened somewhere after a windows update, so I was kind of worried that it might actually be Windows Defender messing things up. But if that would be the case, I would expect many more reports of this kind of issues.

I have no idea what else to try, so I’m open to any suggestions.