However, there are a few small details which I'd like to fix if possible, or at least report/ask whether they are normal.įirst, I've noticed that the near clipping plane isn't changed by a certain mod anymore does Vireio overwrite that at some point? If yes, is there a way to edit the value of that near clipping plane? Thank you so much for working on this driver. Hello, I recently received my DK2 and after a bit of work and Vireio 2.0.6 got Skyrim with about 90 mods to run on it pretty well. Generic PnP Monitor NVIDIA GeForce GTX 680M (CLEVO/KAPOK Computer) I'm planning to upgrade to a desktop in the near future.ĮDIT: I forgot to mention, I've upgraded to the latest nVidia drivers (344.48) I know it's an older (laptop) video card. I've also tried renaming TESV.MTBS, which didn't seem to have any effect. Do the new versions of Vireio require the DK2 to be plugged in? Also, I installed the newest Oculus Runtime (0.4.3). I don't have my DK2 yet, so maybe it's as simple as that. In all cases, I've set tracking to "none" With Vireio 2.0.6, everything works fine if I set it to "DIY Rift" instead of Oculus. With Vireio 2.0.4, everything starts up fine in stereo mode. Vireio 2.0.5 and 2.0.6 both crash Skyrim upon startup. Currently, I'm having an issue where Vanilla Skyrim crashes immediately upon startup with Vireio active.
I've got a DK2 on the way, so I decided to get a head start on getting Skyrim set up with Vireio and to try to see what kind of performance I can get out of my computer.
0 kommentar(er)
