Hard to explain (and it was mostly still playable, at least for some people). The judder problem was more that if moved your head quickly around, the view would feel like it was both snapping + lagging behind. I'll be monitoring this forum thread and the Reddit post for anyone having issues with the new version. If you get an MSVCRT_.dll error when launching, you may need the VC++ 2013 redistibutables from.If not using Oculus controller support, steering wheels / pedals / etc are filtered out, and you can choose what XInput device you want to use at the initial startup screen. (The only thing a keyboard should be needed for is cheat codes, basically.) You can save a game without using the keyboard. Start + Back will open the menu when you're already in game The XBox controller should work better in the menus:
Using Oculus controller APIs, so the Oculus Remote also works in menus / in-game Custom async timewarp removed, since the SDK supports it natively.Tested with a DK2 and CV1 on Windows 8.1 and Windows 10 (with a GTX 970). Use the ones included in the newest version, then customize those if needed. If upgrading from an earlier version, don't try to reuse your cfg files to start with. (DK1 is supported in earlier versions of DukeVR) DukeVR (Duke 3D for the Oculus Rift) has been updated to Oculus SDK version 1.3, and works with the CV1 and DK2 Oculus HMDs.
0 kommentar(er)
