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

AirMech Command #961

Closed
LuckDragon82 opened this issue Apr 12, 2018 · 11 comments
Closed

AirMech Command #961

LuckDragon82 opened this issue Apr 12, 2018 · 11 comments
Milestone

Comments

@LuckDragon82
Copy link

the Steam VR shows the game as flashing between playable and unresponsive. Inside the headset it flashes between the game and the loading screen.

Out of curiosity are games supported on steam still going to receive support on here? Thank you for this awesome program.

@CrossVR
Copy link
Member

CrossVR commented Apr 13, 2018

Can you try that latest version (1.3.0) of Revive?

@LuckDragon82
Copy link
Author

I updated to latest everything (even reinstalled oculus home and revive to be sure). Still doesn't seem to work. It alternates between the game and an error that says the rift is disconnected please reconnect.

@CrossVR CrossVR added this to the 1.3.1 milestone Apr 15, 2018
@CrossVR
Copy link
Member

CrossVR commented Apr 15, 2018

Which headset are you using?

@LuckDragon82
Copy link
Author

HTC Vive (not the pro)

@CrossVR
Copy link
Member

CrossVR commented Apr 18, 2018

This is interesting, there's some sort of race condition here that causes AirMech Command to skip a frame and then submit the same frame twice. So it will submit frames in this order:

1, 2, 3, 5, 5, 6, 7, etc.

I'm not sure whether this is a bug in the game or whether Revive should be forcing the game to run slower. In any case the tracking in that game is a bit jittery due to the frame skip.

@LuckDragon82
Copy link
Author

Hmm. On mine its more than just jittery. In the vive it flashes between the loading screen and the game constantly. On the computer monitor it flashes between the game and the error saying it can't find an occulus rift. How odd. Wonder if something specific to my setup.

@CrossVR
Copy link
Member

CrossVR commented Apr 18, 2018

Oh sorry, forgot to mention that I also reproduced that error, but it was an easy fix, it's related to the frame submission order though.

I actually figured out why it happens though. This game relies on the fact that a call to ovr_GetSessionStatus takes 0.027ms with the original Oculus Runtime. However because I spent a lot of time optimizing Revive that call now takes 0.009ms with Revive causing the game to desynchronize.

That indicates bad programming on the part of the game. There are plenty of other issues with this game too such as getting the new headpose before the runtime finished submitting the frame. This adds a lot of latency and makes the experience uncomfortable.

Fixing this game completely will require some game-specific hacks.

@CrossVR
Copy link
Member

CrossVR commented Apr 18, 2018

Fixed in these commits: 7f4093a...9eab91c

Will be part of the 1.3.1 release.

@CrossVR CrossVR closed this as completed Apr 18, 2018
@LuckDragon82
Copy link
Author

ah ok, I guess I'll keep an eye out for a steam sale :) Thanks for looking into it. Thanks for revive too!

@LuckDragon82
Copy link
Author

oh awesome. I just saw the fix. Thank you

@CrossVR CrossVR modified the milestones: 1.4.0, 1.3.1 May 8, 2018
@CrossVR
Copy link
Member

CrossVR commented May 8, 2018

New version has been released, please test it.

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

2 participants