search

LibreVR / Revive

Play Oculus-exclusive games on the HTC Vive or Valve Index, scroll down for downloads and installation instructions.
Other
3.62k stars 332 forks source link

Lost, Henry and Mythos of the world axis not working "Video driver crashed and was reset! Make sure your video drivers are up to date. Exiting..." #119

Closed koribian closed 8 years ago

koribian commented 8 years ago

Dreamdeck, Farlands and Luckys Tale are working fine. My video divers are up to date.. Any idea what could cause the problem? GTX 970, i7-2600k, 16GB Ram

LibreVR commented 8 years ago

I've never seen this error before, no idea what the problem could be. Looks like a driver crash, I'll keep an eye out for any DirectX errors that could cause that.

Mad1723 commented 8 years ago

Same problem here.

Every other game works, but Henry just crashes as soon as you start the story itself. The little introduction works, but not once you get into the rendering part.

i7-6700k, GTX970, 16GB RAM, Win 10 x64

gonedns commented 8 years ago

Same here, Henry crash after fisrt intro... thx a lot for the EXCELLENCE work

i5 3570k, GTX 980ti, Win 7

Arigator commented 8 years ago

(30/05/2016) I have the same problem with Henry and Lost (Invasion, Dreamdeck etc. works). AMD Phenom II X4 965 Processor, 8 GB RAM, GTX 970, Windows 10 I recently updated my Nvidia graphics driver and Revive, unfortunately around the same time, so I don't know which caused this.
Thanks for your hard work!

Update (03/06/2016): So far I tried:

Unfortunately 'Lost' and 'Henry' still crashed everytime with the same error: "Video driver crashed and was reset! Make sure your video drivers are up to date. Exiting..."

patch24 commented 8 years ago

This was just a problem for me too. On a titan x with latest drivers. Still haven't been able to see Henry or Lost. Although Henry does get through the initial introduction with hand drawn plates...then...crash.

TenaciousJai commented 8 years ago

I'm running a 980ti with Runtime 1.4 and geforce driver version 368.22. I was able to get Lost to load in Vridge and play all the way through, though the colors were very Sepia tone heavy which from what I read is because I lack positional tracking. None of the files are set to run as admin. I'm using 0.6.0 release files. I did NOT load steamvr first - that may make a difference - instead I used the drag and drop loading method.

I wonder if the reason Vridge is successful where an actual vive is not relates to the positional tracking difference between the 2 setups?

LibreVR commented 8 years ago

No, the difference is likely due to the different OpenVR headset drivers.

Brody79 commented 8 years ago

I also have this problem, it worked in the past (using Revive 0.6 and older) but not anymore. Downgrading the Oculus software to 1.3 and using old Revive versions didn't help for some reason. I even tried older versions of Henry and Lost (I made backups of those from end of April) with the same effect. Very strange.

Arigator commented 8 years ago

I can report that having connected more than one monitor is not the reason for the error. I have a multi screen setup (PC monitor, TV, graphics tablet and the Vive) and just disconnected all displays except the PC monitor and the Vive and rebooted, but 'Lost' and 'Henry' still crash with the same error.

Thanks, LibreVR, for your thoughts on the matter and thank you, wissper, for the tip with 'Vridge'. I just googled it, but to my understanding 'Vridge' helps getting to display VR content on an Android device, but would not offer me an alternative possibility to display, for example, 'Lost' on my PC, right?

LibreVR, could you give us some more advice how we could try to troubleshoot the problem (if you deem it possible at the moment)? For example, you mentioned DirectX above, dou you think it could be worth a shot to reinstall it or downgrade it, if possible? Or do you know if 'Lost' and 'Henry', ReVive or Oculus background processes produce log files which could be of use to pinpoint the problem? Thank you again for your awesome work!!

LibreVR commented 8 years ago

As long as I cannot reproduce this problem, I also can't fix it. You'll need to experiment yourself and see if you can find the steps necessary to reproduce it.

Neither Revive nor Oculus have logs that contain information about the graphics drivers. The only way to debug this problem is with a graphics debugger.

Thanks, LibreVR, for your thoughts on the matter and thank you, wissper, for the tip with 'Vridge'. I just googled it, but to my understanding 'Vridge' helps getting to display VR content on an Android device, but would not offer me an alternative possibility to display, for example, 'Lost' on my PC, right?

I would never recommend anyone to use VRidge with Revive. I often ask people whether they are using that application so that I know their issue is not caused by Revive.

DanielSnd commented 8 years ago

Got the exact same issue happening here :(

Arigator commented 8 years ago

LibreVR: Where did you see that 'tip'? I would never recommend anyone to use VRidge with Revive.

Vridge was mentioned by wissper, but I mentioned you and him in the same sentence. Sorry for the misunderstanding.

Brody79 commented 8 years ago

I got Henry and Lost working again: you need Oculus runtime 1.3 and this old RevivePatch. Just copy the files from the patch into the folder with the ...-shipping.exe (...\Binaries\Win64) and you are set.

LibreVR commented 8 years ago

Very interesting, then it may just be an issue with the DRM patch. Hopefully it will be fixed in future versions of Revive.

noodle1009 commented 8 years ago

I have to admit that I'm new to Oculus Home (and Revive as well), but I managed to get things working on my Vive with the patch Brody79 posted alone. I've only got 1.4 - I don't think I have 1.3 (I don't have a 'swap' folder where it is located usually?). I actually tried to find the 1.3 runtime after Brody made his post, and when I couldn't, figured 'what the hell, I'll just try it with the patch', and it worked just fine for me.

LibreVR commented 8 years ago

@noodle1009 It works fine for most people, but there is a group of people who run into this issue.

Arigator commented 8 years ago

I got Henry and Lost working again: you need Oculus runtime 1.3 and this old RevivePatch. Just copy the files from the patch into the folder with the ...-shipping.exe (...\Binaries\Win64) and you are set.

Wow, I had the crash problem before but your method worked for me for both 'Henry' and 'Lost'! Like noodle1009, I could use it with the most current Oculus Home version 1.4. I copied LibreVr's ProjectCars RevivePatch files which you linked to both -shipping.exe folders and could start them without a problem from the ReVive Dashboard! Thanks a lot, Brody79, for posting this solution and thank you again, LibreVR, for creating ReVive and also for providing links to the older patch files which made it possible for Brody79 to find this solution!

LibreVR commented 8 years ago

That doesn't make much sense, the ProjectCars patch will attempt to inject the Revive library, which the injector already did. It really shouldn't affect anything.

Mad1723 commented 8 years ago

I can confirm it indeed works.

LibreVR commented 8 years ago

@Mad1723 Does it still work if you only use the xinput1_3.dll and not the Revive DLLs?

Mad1723 commented 8 years ago

Let me try this out, I'll report back in a few minutes.

Mad1723 commented 8 years ago

With the normal "installer" files, the game crashes.

With just xinput1_3.dll , it doesn't launch.

With the PCars patch files all there, it launches and goes through the whole sequence without issues.

noodle1009 commented 8 years ago

I get the same result as Mad1723, fwiw.

jespertheend commented 8 years ago

I was having the same issue. I still couldn't get it to work using the PCars patch. But I fixed it by adding both the files from the PCars patch as well as the regular files (ReviveInjector_x64 and then dragging Shipping.exe to ReviveInjector_x64) Just using ReviveInjector causes a crash and a graphics driver error once the story starts. Using just the PCars patch causes an error right at the beginning saying "unable to find HMD" but using both patches fixes it for me.

LibreVR commented 8 years ago

If you want to use that solution you should just use the RevivePatch, it's the same as the ProjectCars patch but with an updated Revive library. If you use that one then there's also no need for the injector.

jespertheend commented 8 years ago

Ah I see, I'll use that next time. Thanks!

LibreVR commented 8 years ago

Can anyone re-test this issue with the latest version of Oculus Home and Revive?

jespertheend commented 8 years ago

I tried running Henry using both the RevivePatch, the ReviveInjector and through the revive steamvr overlay, but they all give me a crash once the actual story starts saying "Video driver crashed and was reset! Make sure your video drivers are up to date. Exiting..."

LibreVR commented 8 years ago

It's difficult for me to pin this one down without being able to reproduce it.

jespertheend commented 8 years ago

Yeah, I understand. Well at least the project cars patch is still working. Let me know if I can help

LibreVR commented 8 years ago

I'll try running Henry through a graphics debugger soon, I'll see if there are any warnings about API usage.

MasterMNB commented 8 years ago

For me Mythos of the World Axis is crashing without a Message. But Henry and Lost are working.

Revive 0.7 and 0.62 GTX 980 driver version 368.39 Oculus Version 1.5.0

LibreVR commented 8 years ago

Hey guys, can you test out version 0.8.1? I've made a lot of bug fixes which may affect your issue.

noodle1009 commented 8 years ago

Henry and Lost now work without issue (for me)!

Mythos of the World Axis gives me a UE crash... logs.zip

not sure if that helps or not. Thanks for your continued hard work on this!

LibreVR commented 8 years ago

Great to hear! Looks like checking for API errors paid off, thanks for the feedback.

Mythos seems to be an unrelated issue, if you can submit a separate issue for that then I'll mark it for the 0.9 milestone so it'll be fixed in the next version.