Skyrim and other Bethesda games disable the mouse when the ingame gamepad handling is active, which also disables vorpX’s head tracking.
Hence the need for another solution if you want to play with a gamepad. This is the main reason why a gamepad emulation exists in vorpX in the first place.
But why do we need the gamepad handling at all? Skyrim has native xinput support which means it works flawlessly with an Xbox 360 controller out of the box.
I need to turn off the gamepad handling without the tracking on everything breaking which is what seems to happen at the moment.
Disabling ambient occlusion in the nVidia control panel does not disable Skyrim shadows normally. The native Skyrim shadows have nothing to do with the nVidia ambient occlusion.
The ambient occlusion that can be enabled in the nVidia driver is not a genuine Skyrim feature at all, it is applied as a post process in the nVidia driver, hence it does not work with vorpX.
I understand. I will only report bugs with a completely Vanilla install of any game I play while following all of your recommendations. Which is why I mentioned this one as I wanted to turn off Nvidia 3d vision but it made Skyrim unplayable lol. So now I can follow the guide properly. Thank you for your help. I will disable Ambient Occlusion and turn of Nvidia 3d vision before I attempt to post any concerns. :)
Okay so I just tried this and it is true that it was caused by ambient occlusion. That being said, would it then make sense to enable Nvidia 3d vision the way I said above if someone wanted to have ambient occlusion while playing? The frame rates didn’t change much for me as that’s the only other issue I’m having with skyrim in geometry 3d for now. Is there any other glitches happening related to having Nvidia 3d vision on?
Ralph,
First of all. Just bought Vorpx. Awesome work! I’m looking forward to everything coming from you guys in the future! I’m blown away so far and expect this will continue. :)
This all being said, I also had this shadow flicker issue in Skyrim and what fixed it for me was to actually ENABLE nvidia 3d vision in their control panel and just make sure it’s off in the game (but still enabled). It stops the flicker immediately and once it’s no longer enabled in the control panel, the shadows start flickering again. This also happened with Vireo Perception. So whatever is causing this is universal it seems. There are those out there who are trying everything with no avail. The solution I found is to turn on nvidia 3d vision and make sure to hit “apply”. Once the game starts if you need to, turn off the 3d with the Nvidia shortcut “ctr + T”.
Ralph, again this is MILES ahead of Perception and well worth the money. I’m very happy with your teams work and am looking forward to much more from you guys in the future! Thanks for helping us all enjoy our oculus substantially more than expected!! :)
Note : I have a DK2 so perhaps this specific shadow flicker issue is DK2 specific. Never had the DK1 so can’t say it happens with it.
When you disable the gamepad in Skyrim and disable the the internal gamepad handling in vorpX, you should be able to use an external gamepad tool without problems.
The weird vorpx menu you mention is actually a pretty useful, but often overlooked feature called VR Hotkeys. When you press and hold [SHIFT]+[MIDDLE MOUSE BUTTON] or in your case the left thumbstick, you can simulate key presses by looking at one of the 16 pads and then releasing the button.
This way you can execute keyboard shortcuts without having to look at the keyboard. For Skyrim a few useful shortcuts are preconfigured, but you can freely configure all 16 pads in the vorpX ingame menu to your liking.
Iv been having the same issues as you when trying to get the gamepad to work properly. The way vorpx handles gamepad imputs doesnt alow for deep customization which is fine since there are programs like xpadder that fill that need. However the problem still persists because the internal gamepad seems to have inputs for buttons that simply cant be remapped and it seems to be causing problems with xpadder. When I start a game the gamepad works flawlessly but as soon as I hit the left thumbstick it brings up a weird vorpx menu with numbers that dont seem to serve any function and after I close that all my buttons are messed up. I cant run anymore, sheathing weapons makes me run forward indefinitely and the start and select buttons do other random things.
As a side note, these issues seem to only affect skyrim and farcry 3 as apposed to bioshock infinite, borderlands 2 and COD MW3 which work flawlessly.
Yo.
Skyrim is pretty fantastic with VorpX in DK2. The bare functionality works great. I’m having a few issues with VorpX though.
1. As soon as I disable the internal handling of the gamepad, all head tracking support breaks. It sort of spazzes to the left every now and again but otherwise doesn’t work.
2. For some reason with gamepad support on, when I walk forward my character will start walking backwards or in other directions with no input. This is extremely frustrating.
3. I also have flickering graphics, whether these are shadows or not I can’t be sure. Primarily seems to be in snowy areas. Looking at the mountains in the distance, flickering can be seen – this may not be a VorpX issue since I had the same with VireIO, but I don’t think I have the issue with the game on a 2D monitor.
I cannot get it to work at all. I disabled 2 out of 3 monitors, and i cant get the menu to pop up in skyrim at all. everything is crammed right up against my face, so i cant even play. on top of that whenever vorpx is enabled, windows get randomly moved to the rift. really pain. any suggestions? not really able to search through the forum
If you want to get a sharper super sampled image and smoother lines you can create a custom resolution for the rift display of 2650×1440 @75hz. In the nvidia control panel it’s under change resolution > customize > create custom resolution (not sure how for other cards) then edit the config file of the game to render at 2650×1440 or select it if available in game and launch it with the rift as primary display. Tested it for Skyrim, MW3 and Arma 2 with vorpx and it also works for those few games with native DK2 support like Elite Dangerous & live for speed. It also has the added benefit of bringing the menus more in view for some games.
SKYRIM – I managed to get Skyrim operating in my DK-2
I made sure to delete the 9x.ill file from my SkyRim folder. ( these are the mod files that conflict with VorpX ) I’m not 100% sure the exact name of the file but there’s loads of threads in this forum that explain that you need to remove any mod files..
I made sure that Dk2 is my primary monitor. & I dragged the task bar over onto my laptop monitor so I can still click icons in the task bar.
In VorPX’s confiuration I set Display/Monitors – to Use “System Settings”
(not show only Rift )
I set the Oculus Profile to the profile I created in the Oculus Configuration Utility.
I make sure to when launching SkyRim to set the Display settings correctly.
IN-GAme – to get the screen to show all UI elements I simply middle mouse wheel roll & the game screen edges zoom in & out till I can see all.
I can do up to 1920×1200 on main monitor. So yeah 1920×1080 is available in Skyrim. I’ll try to make DK2 main monitor and see if that helps.
Mmmh, that doesn’t sound right. Normally setting the game (actually any game) to the native res of the Rift is exactly the way it should work with vorpX. Other resolutions often aren’t displayed correctly.
The only explanation I would have for the behaviour you describe is that maybe your main monitor might be a bit older and doesn’t allow 1920×1080, which would make the resolution unselectable in the Skyrim launcher. Nothing vorpX could do about that, but you might be able to set 1920×1080 manually for Skyrim with an .ini tweak. That would at least be worth a try.
The other way around that would probably be to use the DK2 as primary monitor and set vorpX to “Use system settings” display wise (see the vorpX setup guide for details).
Got Skyrim to work but only in 1680×1050. 1920×1080 is not scaled and wrong stereo. I didn’t try running DK2 as primary monitor yet, its quite a pain.