Forum Replies Created
-
Posts
-
Even after resetting the profile, the separation in Z-normal & Z-adaptive is set to 0.0. Increasing it in Z-adaptive seems to work, but in Z-normal, it’s that IPD-like adjustment bug you mentioned. Makes my eyes go crazy. Weird stuff. But if you can’t reproduce it, and since no one else is reporting anything, I wouldn’t spend too much time on it. Just wanted you to be aware.
Quick update: reinstalling the director’s cut didn’t help. The non-director’s cut DX11 version had the same sub-30fps issues in Z3D and even with 3D completely disabled. The DX9 version of the non-director’s cut seems to be the most stable in my limited testing.
But check this out, both version have a weird bug: when selecting Z3D, the 3D separation defaults to 0.00. When I adjust it, it changes the IPD! This does not happen with Z-adaptive or G3D (G3D is totally unplayable, though). Crazy, right?Something is definitely up here. For all I know it could be something on my end, I’m not above user error. But this behavior is just too weird.
Thanks for the reply and for confirming that the performance drop seems off. I have no AA on and most other settings turned down. It’s just unusual behavior, so I figured it’d be worth mentioning. I should note, I’m not seeing this with other games. Perhaps I’ll try reinstalling the game or giving the non-director’s cut version a try. Ultimately, it’s not a big deal for me because I’ve already played through the entire game with vorpx and it was incredible. Still, I like to revisit that world from time to time.
Thanks again!
Ralf is 100% correct. Additionally, nothing’s stopping you from using DSR with a 8:9 resolution if you want a crisper picture. Crank it up beyond 4K if your system can handle it. It’ll always give you better performance than a relative 16:9 resolution – see Ralf’s #3.
I’ve noticed the default settings are sometimes out of whack for some games. If you’re seeing a big monitor even with cinema mode deactivated, check your edge peek settings (deactivate it). Also, check your zoom settings. I noticed in some games the zoom setting defaulted to appear as a big screen. Set it to 1.00 and was back to normal.
After testing a handful of games with the runtime 0.8 installed, everythings seems to be OK so far.
Thanks a million!
Oculus updated sdk/runtime: https://developer.oculus.com/downloads/pc/0.8.0.0-beta/Oculus_Runtime_for_Windows/
Expect any issues?
I’m running windows 10 with oculus runtime 0.5.0.1, latest nvidia drivers. Vorpx works as expected. Downside is direct mode won’t work, but extended mode does and thus, so do most rift apps, minus the very latest. It’s a compromise, but vorpx will support 0.7 in a couple weeks, so no big deal.
0.7 was delayed to mid-october: https://www.vorpx.com/forums/topic/vorpx-0-9-slight-delay/
Yeah, 0.6 works for a lot of people, but me & others had some trouble. Problem is right now, you need to find the right combination of Windows + gfx drivers + runtime. Running windows on a Mac with bootcamp could also introduce compatibility issues. Tough to say.
Have you tried oculus runtime version 0.5.0.1? This has been the most stable for me. 0.6 gave me trouble, too.
Thanks! Good advice & I’ll be keeping my fingers crossed. I’ve been sticking with 0.5.0.1 because it’s been more stable with other apps.
Another “thank you” for continued support for 2D edge peek. While I prefer 3D for cut scenes, games like Dishonored, Deus Ex, & Thief have a ton of written materials & it’s much easier to read notes & emails & such with 2D edge peek.
Can’t speak to your first question or to ENB, but you might be able to use Raedon Pro to inject Sweetfx, even with an Nvidia card. This works with vorpx activated. I’ve tested with Dishonored, Thief (2014), & Bioshock Infinite. Unfortunately, I’m unable to provide instructions. Someone on the oculus forums posted a youtube tutorial. You may want to search there. In addition, you may have luck with google searching for Radeon Pro/Sweetfx/Nvidia (in the event you have an nvidia card).