Forum Replies Created
-
Posts
-
The only real implementation issue that I see is that disabling the gamepad override does actually disable it, which is what brought me here in the first place. If I run a DirectVR scan and then disable the gamepad override everything works okay (minus head tracking rotation), but requiring the scan first is counter-intuitive. Not performing the scan leads to a situation in which it apparently switches on/off the override based on directvr data, which may not exist.
As far as head-tracking rotation, it’s great when it works, but I’ve seen it invert numerous times and switching the invert on/off in vorpx doesn’t appear to do anything. On one occasion it rotated the camera (or the world) 90 degrees. So, I disabled the override and found that it only made things worse.
If it was vorpx sending the keystrokes, then it was doing so regardless of whether the override was disabled or not.
Well, at this point I feel like a total idiot. My initial assessment was correct – it was the Oculus Client messing things up, not Vorpx. I realized this after the problem occurred again last night and I tried to repair it with the game console, which failed miserably because it was already gamepad-enabled.
For some reason the Oculus client was hiding the controller and sending keystrokes and mouse inputs (sounds a bit far-fetched on the keystrokes, but I opened up the console, moved the left stick around, and saw it fill up with WASD’s). I checked some other games (Bioshock Infinite for example) and they also had the same problem, while other’s didn’t (Borderlands 3 and Witcher 3). Even some native VR apps had this problem, whereas Virtual Desktop was unscathed.
Anyway, I had to re-install the Oculus software 3 times and re-pair the controller a gazillion times before it took, so I’ll be getting a new hmd soon. If you’ve got any recommendations for anything that doesn’t have Oculus or Facebook written on it…
So…I was really having fun in Skyrim – I’d lost interest in the game before Vorpx, but now I’m back at it again. Vorpx was what I got my headset for, I just didn’t realize it at the time, so thank you very much (I found that with few exceptions that native VR games are {expletive deleted}, IMO).
Whatever directvr is doing, it has the effect of setting bGamepadEnable to false in SkyrimPrefs.ini. That’s not native support, it’s the opposite, and a controller that was once working fine suddenly becomes useless in the middle of the game. All of your input prompts get changed from xbox icons to keyboard prompts even though the keyboard is disabled, controller buttons no longer work or are remapped to different functions, and the mouse cursor is suddenly back even though the mouse input is disabled.
I’ve renamed vorpscan64.exe, and tried the steamvr client instead of oculus, and while both attempts worked initially, the controller still gets remapped sooner or later.
I’ll use my Virtual Desktop workaround if you aren’t going to fix the buggy implementation – I get better fps at the cost of image quality, but that’s better than trying to play the game with the limited controller support that vorpx keeps insisting on, when it should just leave things alone. Disabling the gamepad override in vorpx should actually disable it.
No one (except you maybe) plays Skyrim with a controller in the emulated keyboard mode you call native. It is a horrendously bad, default configuration. Maybe I can find a mod that will undo the stuff that vorpx is doing – I dunno.
I reset the profile, did a directVR scan, and insured that the override was enabled. The net result of that is it goes into the emulated mouse/kb mode that I was complaining about. That is NOT native gamepad support; it is a mode where it recognizes that a gamepad is plugged in and provides limited support, but to get true controller support bGamepadEnable must be set in SkyrimPrefs.ini. The difference in functionality is fairly obvious – when set, the game will no longer accept keyboard input at all (except for the console key) and the controller map is enabled.
I can work around the issue by setting vorpx to output to the generic display and using Virtual Desktop to send it to the headset. I don’t want to do that because there’s a small impact on image quality and fps, but apparently what vorpx thinks is native controller support is not really native support at all, and I don’t see why it can’t just pass things through without interfering.
On the topic of DirectVR, it always ends with fov success and rotation success or failed. I can set the fov with a console command and rotation will never work when the gamepad is truly enabled because there’s no mouse control, so a directVR scan is rather pointless.
I was going to send you a troubleshooting zip file but the crash hasn’t occurred in the past day or so I’m guessing that it was something in my environment. I updated my c++ redists for an unrelated reason, perhaps that fixed the crashing – no way to know for certain.
I don’t have any av other than defender. The crashes appear to occur when I start a game. It doesn’t stop the hooking from occurring and vorcontrol64.dat starts back up immediately. Maybe the watcher isn’t getting suspended after the hook occurs?? Anyway, it isn’t an anti-virus thing and doesn’t appear to have any impact, other than putting entries in the event log.
Well, as it turns out, Riva Statistics tuner was interfering, even with the OSD turned off. It hadn’t been an issue before with SkyrimSE, but shutting it off appears to have fixed the problem.
Well removing that dll didn’t fix the problem, not permanently, it was just coincidental. Vorpx will occasionally attach to SkyrimSE, but most of the time it ends with the hook helper dialog popping up.
The log file says not hooking swapchain due to VORPX_DXGI_SWAPCHAIN_HOOK_MODE_METHODS_ONLY setting.Anyway, I was playing the game last night and after this update it won’t hook. I’ve tried toggling fullscreen, different resolutions, SteamVR instead of Oculus and it hooked a couple of times but without a consistent pattern.
Nice update. I had to remove a file named “-dxgi.dll” from my Skyrim game folder because apparently vorpx doesn’t like that name, even though it’s harmless since I renamed it, and is a left over of when I was playing Skyrim on my desktop. And I know that my dinput.dll is actually a dll loader but the new warning is nice, I guess.
Just did a quick test and it works okay unless I have my desktop extended to the second monitor, at which point the context menu goes away.
BTW, the game is incompatible with tridef and superdepth3dvr because of the dx9c functions it uses. Good luck finding that compatible vorpx profile, if it exists.
Forget that I tried to help. I have a copy of the game and it runs fine for me when I dropped a copy of dgvoodoo’s d3d9.dll into the game folder- vorpx complains, but it hooks fine.
Whatever.
You need the d3d9.dll file. The others are irrelevant. Vorpx will complain but it’s safe to ignore it.