Forum Discussion
Schnigges
12 years agoHonored Guest
Oculus not detected after SDK update to 0.4.2
When I first got my DK2 a few weeks ago, I only had the time to test a few of the awesome demos provided on this website. However, after finishing some of my projects, I now wanna get started with Oculus development.
Today, I downloaded the latest SDK version 0.4.2 and tried to get the OculusTinyRoom sample project to run. Unfortunately, my DK2 is only detected when I'm running the project from the previous SDK 0.4.1.
When trying to integrate the SDK code in my program, the same error occurs and the DK2 is not detected. I'm trying to use the following method:
In my VS2012 project, I'm including the two directories "LibOVR\Src" and "LibOVR\Include" as well as the "LibOVR\Lib\Win32\VS2012" library path + all the libraries from the OculusTinyRoom example.
Strangely, the Oculus Config Tool detects the DK2 just fine. Any ideas what could be the problem?
EDIT:
I just tried to use paths to the 0.4.1 SDK and then it seems to work just fine. Any idea what is necessary to make 0.4.2 work as well?
Today, I downloaded the latest SDK version 0.4.2 and tried to get the OculusTinyRoom sample project to run. Unfortunately, my DK2 is only detected when I'm running the project from the previous SDK 0.4.1.
When trying to integrate the SDK code in my program, the same error occurs and the DK2 is not detected. I'm trying to use the following method:
void InitializeOculusRift()
{
std::cout << "Initializing Oculus SDK ..." << std::endl;
ovr_Initialize();
int hmdCount = ovrHmd_Detect();
std::cout << "Found " << hmdCount << " connected Rift device(s)" << std::endl;
for (int i = 0; i < hmdCount; ++i)
{
ovrHmd hmd = ovrHmd_Create(i);
std::cout << hmd->ProductName << std::endl;
ovrHmd_Destroy(hmd);
}
ovrHmd hmd = ovrHmd_CreateDebug(ovrHmd_DK2);
std::cout << hmd->ProductName << std::endl;
ovrHmd_Destroy(hmd);
ovr_Shutdown();
std::cout << "Initializing Oculus SDK finished" << std::endl;
}
In my VS2012 project, I'm including the two directories "LibOVR\Src" and "LibOVR\Include" as well as the "LibOVR\Lib\Win32\VS2012" library path + all the libraries from the OculusTinyRoom example.
Strangely, the Oculus Config Tool detects the DK2 just fine. Any ideas what could be the problem?
EDIT:
I just tried to use paths to the 0.4.1 SDK and then it seems to work just fine. Any idea what is necessary to make 0.4.2 work as well?
1 Reply
- cyberealityGrand ChampionCan you list the error messages you are getting?
It may just be an issue of your paths pointing to the wrong place.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 6 months ago
- 2 years ago
- 10 months ago
- 6 months ago