Forum Replies Created
-
AuthorPosts
-
BuckleBeanParticipant
Good news: while doing something entirely different incidentally this could finally be replicated. Fix is working here, hopefully it will also work for you guys. Will be in the next update.
Hey, that’s great news! Though, I actually might be too scared to play SS2 in VR :(
BuckleBeanParticipantWhat official review? I only know of Immersive Gamers beta videos that he has access to, its still not ready so we have to wait a bit for (I guess) the 1.0 vorpX
This here is the truth. ImmersiveGamer makes the best vorpx vids around, but he could have done a better job clarifying that the latest version had not yet been released.
BuckleBeanParticipantOP, have you been able to resolve this issue? I realized I’d never have time (or the will) to roll back drivers until I found a stable one. Just curious if you’ve found a solution to the black screen problem. I still have it.
BuckleBeanParticipantThe Witness has unofficial native support. Just put “-vr” in your launch options. Played for 4 hours today and it’s amazing. Don’t get it if you don’t like puzzles. See here for more info: http://www.theriftarcade.com/how-to-play-the-witness-on-the-oculus-rift/
BuckleBeanParticipantI reset my graphics driver 3D settings to default in the nVidia control panel and no luck. I don’t know when I’ll have a chance to try, but I’d be curious to know if rolling back the latest driver fixes it. It’s the only thing I can think of that may have changed since I last booted one of these games successfully.
BuckleBeanParticipantFunny thing, I just noticed this exact behavior with Thief Gold & Thief 2 last night. All 3 games use the Dark Engine, right? Just tried SS2 and yep, I have the same exact problem, so there’s definitely an issue. I want to say they were all working for me quite recently, but I can’t remember when I last booted them up. Could have been prior to the latest vorpx release, but I really don’t think so. What could have changed? I can’t imagine any of these games were updated. Has SS2 worked for you since the latest vorpx update? Only thing I can think of is gfx drivers. On Nvidia by any chance?
Weird stuff.
BuckleBeanParticipantJust chiming in to say I have gsync enabled and have not seen this or anything similar, so I’d guess it’s not related.
BuckleBeanParticipantEven 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.
BuckleBeanParticipantQuick 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.
BuckleBeanParticipantThanks 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!
BuckleBeanParticipantRalf 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.
BuckleBeanParticipantI’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.
BuckleBeanParticipantAfter testing a handful of games with the runtime 0.8 installed, everythings seems to be OK so far.
Thanks a million!
BuckleBeanParticipantOculus updated sdk/runtime: https://developer.oculus.com/downloads/pc/0.8.0.0-beta/Oculus_Runtime_for_Windows/
Expect any issues?
BuckleBeanParticipantI’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.
-
AuthorPosts