Forum Discussion
Has Oculus removed the ability to run C++ console exes?
Issue summary: It appears Oculus Home is no longer allowing C++ console exes to connect to the HMD OR is expecting an additional prompt to allow dismissal of the "Please Wait" screen after the Health and Safety warning has been acknowledged. Any input about possible causes behind this issue would be appreciated.
Okay, here are the details on our issue:
We've put together a simple C++ / Qt console program which interfaces with the Oculus HMD but projects no video -- it only provides accompanying audio in response to user head gestures and controller input. The app connects to the HMD, reads the device orientation to detect head nods, device taps and the like and is designed to work alongside Oculus movies and games.
All was well through to Runtime v0.8.0 but, on v1.3.2, after dismissing the Health and Safety warning the app is left to hang at the "Please Wait" screen, as if Oculus Home is expecting to hear something else from the app.
When left at that "Please Wait" screen the app runs by itself without issue, but that "Please Wait" screen then makes it impossible to start anything else from Oculus Home.
The expected behaviour when using our app would be:
User opens Oculus Home.
User starts our exe from Windows.
User opens up their game, move, experience and our exe continues to operate alongside it.
That is how things operated under the v0.8.0 runtime and earlier.
The behaviour we're seeing now is:
User opens Oculus Home.
User starts our exe from Windows.
User is left waiting at the "Please wait..." screen after dismissing the health and safety warning.
For another use case:
User opens Oculus Home.
User starts their game or experience (e.g. open up Farlands and sit at the deployment screen)
User starts our exe from Windows.
User is presented with the health and safety warning again and, on dismissing it, is left at the "Please wait..." screen on the HMD even though the game/experience remains loaded and displayed in a window on the PC.
All is well to run our app solo, all exes are digitally signed, and the Oculus Home "Unknown Sources" "Allow apps that have not been reviewed by Oculus to run on my Rift" option has been toggled on.
It seems that things are being blocked somewhere else, as if the Oculus is no longer capable of working with C++ console exes.
Is it now no longer possible to run a C++ exe with an Oculus HMD, or must an extra action be sent to the HMD after the health and safety warning is dismissed in order to get past the "Please Wait" screen?
Okay, here are the details on our issue:
We've put together a simple C++ / Qt console program which interfaces with the Oculus HMD but projects no video -- it only provides accompanying audio in response to user head gestures and controller input. The app connects to the HMD, reads the device orientation to detect head nods, device taps and the like and is designed to work alongside Oculus movies and games.
All was well through to Runtime v0.8.0 but, on v1.3.2, after dismissing the Health and Safety warning the app is left to hang at the "Please Wait" screen, as if Oculus Home is expecting to hear something else from the app.
When left at that "Please Wait" screen the app runs by itself without issue, but that "Please Wait" screen then makes it impossible to start anything else from Oculus Home.
The expected behaviour when using our app would be:
User opens Oculus Home.
User starts our exe from Windows.
User opens up their game, move, experience and our exe continues to operate alongside it.
That is how things operated under the v0.8.0 runtime and earlier.
The behaviour we're seeing now is:
User opens Oculus Home.
User starts our exe from Windows.
User is left waiting at the "Please wait..." screen after dismissing the health and safety warning.
For another use case:
User opens Oculus Home.
User starts their game or experience (e.g. open up Farlands and sit at the deployment screen)
User starts our exe from Windows.
User is presented with the health and safety warning again and, on dismissing it, is left at the "Please wait..." screen on the HMD even though the game/experience remains loaded and displayed in a window on the PC.
All is well to run our app solo, all exes are digitally signed, and the Oculus Home "Unknown Sources" "Allow apps that have not been reviewed by Oculus to run on my Rift" option has been toggled on.
It seems that things are being blocked somewhere else, as if the Oculus is no longer capable of working with C++ console exes.
Is it now no longer possible to run a C++ exe with an Oculus HMD, or must an extra action be sent to the HMD after the health and safety warning is dismissed in order to get past the "Please Wait" screen?
11 Replies
- I neglected to include a code sample to allow a reader to duplicate this issue. Here it is.
Compiling this minimal exe and running it will bring about the situation I mentioned above:
-----8<----------8<----------8<----------8<----------8<----------8<----------8<----------8<-----#include <OVR_CAPI.h>
-----8<----------8<----------8<----------8<----------8<----------8<----------8<----------8<-----
#include <thread>
#include <iostream>
int main()
{
if (ovr_Initialize(nullptr) == ovrSuccess)
{
ovrSession session = nullptr;
ovrGraphicsLuid luid;
ovrResult result = ovr_Create(&session, &luid);
if (result == ovrSuccess)
{
// We're connected to the HMD at this point.
// Let's watch the HMD orientation.
ovrTrackingState ts;
ovrPoseStatef tempHeadPose;
ovrPosef tempPose;
ovrQuatf orientation;
while (true)
{
ts = ovr_GetTrackingState(session, 0, true);
tempHeadPose = ts.HeadPose;
tempPose = tempHeadPose.ThePose;
orientation = tempPose.Orientation;
// We can do stuff here, but the HMD remains stuck at the
// "Please wait..." screen forever.
// For an example, we'll just output the x orientation value.
std::cout << orientation.x << std::endl;
std::this_thread::sleep_for(std::chrono::milliseconds(500));
}
ovr_Destroy(session);
}
ovr_Shutdown();
}
return 0;
}
The HMD orientation is polled and output to console. In the meantime, the Oculus HMD remains stuck at the "Please wait..." screen after the health and safety warning has been dismissed.
Multiple instances of this simple exe can be run at the same time, so it appears the Oculus is waiting for an acknowledgement message of some sort to dismiss that "Please wait..." and is not restricted to running one application at a time.
Thoughts? Any insights would be appreciated. - Because that forum is crap for code quote : http://pastebin.com/d48zzBBw
They need to improve the forum for dev purpose ! I can't help you much for your problem, they introduce "ovr_GetSessionStatus" with a "IsVisible" value to query the focus status of your application, so they probably have the idea several apps can run in parallel, but as your app is kind of the borderline compared to a regular one, i bet they will have to work on that based on bug report and devs feedback :) Thank you for that, Galopin.
I appreciate the pastebin link.Oculus must have considered the possibility of applications
running in parallel and I'm sure I'm just missing something new for working
with the latest runtime. However, what
that magic might be for continuing past the HMD’s “Please wait…” prompt is a
mystery at the moment.- I'm having a problem that would be explained by this. I can't get past ovr_Initialize. Every time I reach this point in the code (in a console app that sets up an OpenGL Window), Oculus Home launches and nothing happens after that, ovr_Initialize never exits.
- have you found solution for problem?
- It'd be nice to get an update on this, I'm running into the same issue.
- You need to use the Invisible flag when calling the Oculus SDK for any non-visual app.
- hey,
I count on which you are the use of home windows. Uninstall previous installation of codeblocks, you could need to delete the code blocks folder from C:/customers/"YourName(Admin)"/AppData/Roaming (you can make this record visible by way of going to home windows search->folder alternatives->View-> show hidden documents, folders and drives). Now, attempt downloading the "codeblocks-thirteen.12mingw-setup.exe" from the code blocks down load page) and deploy fresh. ensure the tool chain executable(settings -> compiler->worldwide compiler settings) indicates Linker for dynamic and static libs. quality needs.
regards
charlie - hey,f you're coming from a background in home windows computing device programming in C++, you may likely find that some factors of writing apps for the UWP are acquainted, but other components require a few gaining knowledge of.what's the same !you can use the STL, the CRT (with some exceptions), and another C++ library so long as the code does now not attempt to name windows features that are not handy from the home windows Runtime environment.if you're conversant in visual designers, you could nonetheless use the designer constructed into Microsoft visible Studio, or you can use the extra full-featured mixture for visible Studio. in case you're familiar with coding UI by way of hand, you may hand-code your XAML.you are nevertheless creating apps that use windows working gadget kinds and your own custom sorts.you are nevertheless the use of the visible Studio debugger, profiler, and other improvement gear.you're nevertheless creating apps which are compiled to native machine code by way of the visual C++ compiler. UWP apps in C++ don't execute in a controlled runtime environment.
regards
jayesh - So did anyone find a solution to this problem ? I read something about an Invisilbe flag, but couldn't find any more info on it.
