Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Game shows up on moniter, moves with headset, nothing in headset #163

Closed
MastaFoo opened this issue Jun 26, 2017 · 10 comments
Closed

Game shows up on moniter, moves with headset, nothing in headset #163

MastaFoo opened this issue Jun 26, 2017 · 10 comments

Comments

@MastaFoo
Copy link

Hello, I have the latest version, a Vive, Sapphire Nitro+ 480 8GB, FX 8350, 16GB DDR3 RAM, and my problem is as follows:

I boot the game up, enable VR mode, and the game on the monitor splits to SBS3D like it should, and moves with the tracked headset, but in the headset, all i see is black, and my chaperone bounds. It doesnt matter if I use Direct or Extended mode, doesnt matter if i start with the .bat file, and doesnt matter if I start with the Vive turned on or off; the result is the same every time.

@cmbruns
Copy link
Owner

cmbruns commented Jun 26, 2017

After you quit doom, do you see the Vive home room in the headset? Ori is it still black then?

@MastaFoo
Copy link
Author

Home/ VR Landing area on closing doom.

@st45244
Copy link

st45244 commented Jun 26, 2017

having same issue headset moves with game headset black. it goes back to steam home when i exit game
just to add i have xfx ati rx480

@cmbruns
Copy link
Owner

cmbruns commented Jun 26, 2017

What is your video driver version? @MastaFoo

@MastaFoo
Copy link
Author

17.5.1

@gsmsosv
Copy link

gsmsosv commented Jun 26, 2017

I am also experiencing this issue with an R9 390X, driver version 17.4.1. Additionally, once you select a difficulty and start a new game, the headset displays a "hall of mirrors" effect with the chaperone boundaries. This returns to normal upon exiting.

@cmbruns
Copy link
Owner

cmbruns commented Jun 27, 2017

@MastaFoo @st45244 @gsmsosv Could you please try ViveDoom0.5.4 and report back whether this issue is affected?
https://github.com/cmbruns/gz3doom/releases

@cmbruns
Copy link
Owner

cmbruns commented Jun 27, 2017

Presumably fixed in revision 5e91f6e

@cmbruns cmbruns closed this as completed Jun 27, 2017
@gsmsosv
Copy link

gsmsosv commented Jun 28, 2017

Confirmed, issue is fixed in the latest version! Thanks!

@MastaFoo
Copy link
Author

Fixed on my end. Thank you for your awesome work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants