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

Crashing on Startup #41

Open
JorenRapini opened this issue Jun 13, 2018 · 6 comments
Open

Crashing on Startup #41

JorenRapini opened this issue Jun 13, 2018 · 6 comments

Comments

@JorenRapini
Copy link

Reinstalled Robo Recall and Robo Revive, anytime I try running the game from the shortcut I get a UE4 crash report. No helpful info on it either, just "You do not have any debugging symbols required to display the callstack for this crash."

@CrossVR
Copy link
Member

CrossVR commented Jun 13, 2018

Looks like Robo Recall was updated, I'll take a look.

@Jeanmds
Copy link

Jeanmds commented Aug 1, 2018

I have a WMR headset (lenovo). ROborevive was the best way to play this game in a 1060, but it stopped working after the steamvr update (1532733603) - Hotfix. The revive dashboard (reviveoverley) no longer worked for me, started and stopped working, had to format the pc and the revive (remixed) came back to work. The image is excellent But the bugs in music and crash and the performance in the remixed in this demanding game are bad. Is there any possibility of release a roboremixed ?? Performance and image quality would be amazing in this game.

@CrossVR
Copy link
Member

CrossVR commented Aug 1, 2018

@Jeanmds RoboRemixed is fundamentally impossible, as there is no WMR plugin for UE4.

@Jeanmds
Copy link

Jeanmds commented Aug 1, 2018

Sad to know that. Thanks for the great work done on the revive and remixed.

@thomashaselwanter
Copy link

Also getting this UE4 crash report on startup. It starts and works just fine through Revive but crashes with RoboRevive. RoboRecall v1.6 and RoboRevive v1.1. Any ideas or pointers?

@thomashaselwanter
Copy link

Going to the old issues it seems that @CrossVR released v1.1 specifically to fix the startup crash for Robo Recall v1.5. Looks like v1.6 has us crashing again. Any chance this will get fixed or should I just stick with playing this through non-native Revive?

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

4 participants