Forum Replies Created
-
Posts
-
Really? Damn, that’s odd, I can get decent framerates even on ultra, 90 in many places and it rarely drops below 50. I guess a CPU bottleneck is a possibility, but the 1800X is only slightly less powerful than the Intel flagship at the worst (at least in terms of gaming benchmarks), so it’d be surprising if that were the case. Could it be that Vorpx is poorly optimized for AMD architecture or something? How are your Nvidia settings? You don’t have AA cranked, do you?
steph12, my i7 7700K @ 4.9GHz never went over 50% usage and often dropped much lower than that, and my 1080 Ti maxed out at 80% usage but probably averaged something like 65%. Few games will max out either your CPU or GPU, and with VR in particular, I think usage averages are supposed to be lower than you’d normally get for whatever reason (although this doesn’t mean that better hardware won’t give you better performance, it obviously does).
On the 1080 I had before I replaced it with the Ti, I was able to get a steady 90fps on medium settings with the shadows on low @ 1600×1200 with an internal resolution of 1.5. Note, though, that my framerates were terrible until I disabled fluidsync, as mentioned above.
I’d also suggest updating your nvidia drivers if you haven’t done that already.
Not sure if you ever got this fixed baggyg, but what worked for me was uninstalling both of the Nvidia 3DVision entries from add/remove programs. This had been causing a bug where vorpx would detect all d3d9 games as having a render area of 1×1, which produced exactly the behavior you described. No issues since applying this fix.
I’m having the same issue–Skyrim was working absolutely flawlessly, but it seems that after the latest Oculus driver update that’s no longer the case. Exactly as the OP describes, the DirectVR scan no longer works–instead of showing the overlay with its various status bars, the image will just freeze for a few seconds, and then when it’s moving again, the geometry of the head tracking is still completely skewed like you’re using the z-buffer setting instead of the geometry setting. This is so depressing because as obnoxious as Oculus is, I don’t think there’s any way to roll the driver back, and you aren’t even able to use Oculus home unless you do update. ugh.
Ralf, please update VorpX as soon as you can, I really want to play Skyrim again.
For some reason I can no longer see my second post so here it is again:
“Never mind, I’m an idiot, I should have read more of the existing posts—disabling fluidsync immediately resolved the issue. If anything it seems to work better than on the DK2, I’m getting rock-solid 90fps with the internal resolution set to 2 and the game resolution set to 1600×1200. I’m completely blown away, this is completely and utterly incredible.
One more issue though—zooming in and out from the cinema mode, I realize that the actual FOV showing on the rift is very small compared to what’s being rendered. So, as a test, I walk up to a mantle in the Riverwood Trader until it fills my field of vision on the Rift, save, disable vorpX, and then load the game right back up. Tinkering with the fov console command it seems that, from that distance, the mantle only fills up an FOV of 70—and in cinema mode it looks like the game is being rendered with an FOV of 110, as it should be. I also notice that, apparently unlike with the DK2, the “zoom” feature does not at all affect the FOV, and instead just alters the size of a letterbox that appears around the visible area and gets smaller as the zoom is decreased.
Can anybody explain what might be going on here? In spite of how great everything looks the FOV does feel a little claustrophobic, and my experimentation seems to show that it’s a mere 70 degrees without any means of increasing it.”