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

Black screen issue #8

Open
maddogspeighty opened this issue Jun 20, 2016 · 3 comments
Open

Black screen issue #8

maddogspeighty opened this issue Jun 20, 2016 · 3 comments

Comments

@maddogspeighty
Copy link

Hi, will start by saying thanks for the great work your doing.

I just wondered if you have heard of this issue.

I currently use your driver with riftcat software, the issue I have is when I start a motion controlled game after a few minutes the screen goes black, head tracking and leap motion still function correctly if I look at the monitor.

It only seems to happen when the leap motion is in use, any other game seems to be fine.

I am just trying to find out whether it is a riftcat or leap motion. Driver issue.

@cbuchner1
Copy link
Owner

I haven't experienced this yet. Recent versions of SteamVR (beta?) have
switched to using a 64 bit SteamVR server by default. Some compatibility
issues were noted by the maintainer of the (very similar) SteamVR Hydra
driver.

Its maintainer noted: as a temporary workaround create an environment
variable "VR_DISABLE_64BIT_SERVER". The 32 bit version of the driver
apparently doesn't have any issues.

The environment variables can be configured in the System control panel of
Windows, either system wide or per user.

Christian

2016-06-20 9:29 GMT+02:00 maddogspeighty notifications@github.com:

Hi, will start by saying thanks for the great work your doing.

I just wondered if you have heard of this issue.

I currently use your driver with riftcat software, the issue I have is
when I start a motion controlled game after a few minutes the screen goes
black, head tracking and leap motion still function correctly if I look at
the monitor.

It only seems to happen when the leap motion is in use, any other game
seems to be fine.

I am just trying to find out whether it is a riftcat or leap motion.
Driver issue.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#8, or mute the thread
https://github.com/notifications/unsubscribe/AAZb01ZSOrquO4ddxgxkWP3k4cOzjE9kks5qNkFAgaJpZM4I5bVn
.

@maddogspeighty
Copy link
Author

Ok, thanks for the quick reply, I have contacted the creators of riftcat to see if they can shed some light on the issue.

Have you used your driver with vridge at all or do you use it with another device or program.

@NeoToriyama
Copy link

Can you give a tutorial on how to create the environment variable using "VR_DISABLE_64BIT_SERVER". What file do I target when creating the new variable?

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

No branches or pull requests

3 participants