Forum Replies Created
-
Posts
-
Mainly because they downgraded (made less visible) the raster shadows. I saw a video a few days ago where someone compared the prior version to the new one with and without raytracing. There was hardly any difference between the old version and the new one with raytracing, but a huge difference between new with/without raytracing. Whether they did that intentionally to make the difference more apparent is impossible to tell, but it’s a weird coincidence for sure…
Anyway, let’s hope it’s just a bug and gets fixed soon.
Please double and triple check whether you really have selected ‘SteamVR’ in the config app. The error message you see under normal circumstances can’t be shown in SteamVR mode at all. It is only displayed during Oculus init if no Oculus device is found.
Did you check the FAQ post on top of this sub-forum?
My activation key cannot be verified.
Please double check whether the request code in the license dialog is the same as in the key e-mail. If not, send us your new request code. Also please make sure to enter the data in the name field correctly. It has to look exactly like in the key e-mail. Use copy and paste to avoid typos. The key e-mail has an example image attached that illustrates how it’s supposed to look.
I’m not sure yet whether I can get DX12 working before the update. If not, I’ll try again later. Looks like instead of natively updating the renderer to DX12 CDPR used Microsoft’s D3D11On12 DX11>DX12 wrapper and then implemented the DX12 exclusive features on top of that. That’s probably also the reason for performance being worse compared to Cyberpunk, should clearly be the other way around. Unfortunately this method is not only fairly ineffecient, but also clashes with hooking DX12.
Most improvements of the update are also available with DX11 luckily, pretty much the only important thing missing is raytracing, which istn’t really a good option anyway for VR because of the performance impact.
This can’t be solved on the forum. Please send an e-mail to support at vorpx com or use the contact form. Allow some time for a reply.
Not entirely true, even for pro-users like you there may be one or the other thing you haven’t discoverd yet. :) For user profiles there are two additional options that may work under certain circumstances:
- TrackIR head tracking for any game that supports TrackIR input. vorpX displays according hints if TrackIR is detected.
- Gamepad emulation via head tracking: although quite laggy, and thus not ideal, this should work for most games that let you look around with a gamepad stick. Most sim games for example fall under that category. The method is worth a shot if no mouselook is available. Set ‘X-Box Gamepad Override’ to off and then enable ‘Head Tracking As Gamepad’. Best used in immersive screen/cinema mode, which makes the lag less annoying, but also works in FullVR mode.
Contrary to your naive batch file suggestion back then vorpX adjusts some values based on information only known while a game is running, hence your idea wouldn’t work. And even if that wouldn’t be the case: having to deal with extra launch scripts/batch files/whatever is hardly more user friendly than being able to just normally launch a game from Steam and pressing a button to revert settings if necessary in the first place.
Sometimes things aren’t done the way you believe they should be done because others are more stupid than you are, but because there are actual reasons for doing them how they are done. :)
That’s a good idea. Won’t make it into the next update, but I’ll put that on the list for the next maintenance release after that. Should be fairly simple to provide some flag evaluation value similar to how button presses are handled currently in the API.
On a sidenote: during the Cyberpunk mod development I made some changes to the API, which will also come to the next regular vorpX build. I tried not to break anything, but you will at least have to recompile your mod/project for the next build.
If you coded a binding for a different language and transferred the VPX_PROP_… defines in vorpAPI.h for that, you will also have to update those. Just in case. Normally they are only used internally, but if you did something out of the ordinary, they have to match the changed ones. There was at least one bug with a duplicate value which had to be fixed, and I also might have changed two or three others.
If PowerDVD can output to side-by-side, you could try to create a profile based on the ‘SBS 3D Base’ profile that I added to the cloud a few weeks ago. Should work with pretty much everything that creates an SBS image using DX9-12 or OpenGL.
- Download the ‘SBS 3D Base’ profile from the cloud in the config app.
- Make a copy of the downloaded profile.
- Assign the main PowerDVD .exe to the newly created profile.
No guarentee that it will work, but provided PowerDVD actually can output SBS (quite likely), your chances are good. Caveat: may not work for content with DRM though. In that case you’ll probably just get a black image even if hooking the app works correctly.
An alternative option would be the vorpX desktop viewer, which can also be configured to process side by side input (on the image page of the menu).
Does this happen with both gamepad and keyboard/mouse? The auto hide detection depends on key/button presses and only works correctly with the default key/button mappings in the game options.
Just in case: did you by any chance change the motion controller mode to keyboard/mouse? if so, please reset it back do gamepad. Steering should feel quite natural normally. When a keyboard is emulated however, steering is pretty much digital. Just as steering with an actual keyboard.
General hint: be careful as far as tinkering with settings in the vorpX menu is concerned. As the tutorial message says, there shouldn‘t really be any need to tinker with vorpX settings aside from the resolution quality (and potentially the 3d method if you don‘t like the AFR 3D).
Ah, I see. Unlikely that memory scanner tracking works correctly in a user profile. Memory scanner settings are *very* game depependent. There is a certain chance that memory scanner settings may work between games, hence there is an option to keep them when creating a user profile, but that’s just not very likely.
Stick to mouse based tracking then and generally only assume memory scanner tracking to work correctly in the official profiles that it was set up for originally.
Are you sure that head tracking does anything at all? Sometimes the brain may trick one into thinking it’s inverted although it actually doesn’t do anything. If mouse base tracking is actually working at all, either changing the mouse invert setting in the game or the tracking invert setting in vorpX must have an effect too.
Only other (rather unlikely) issue I could think of is that maybe some input/mouse related utility gets in the way. That’s a long shot though. Still worth a try to check that if you happen to use any mouse related tool. Gaming mice for example may come with stuff like that.
Glad you found the culprit.
On a sidenote: didn’t running vorpX as admin help in that case? It should normally. That’s one of the one-click trouble shoot options directly shown in the ‘can’t hook’-dialog.
If nothing works at all, there almost certainly is something getting in the way. if you happen to use any other antivirus than Windows Defender, get rid of it. Regardless whether it played nice on your prior system or not. If you have any tools/utilities running in the background, try without. Regardless whether they played nice on your prior system or not.