Forum Discussion
SpaceEngineer
8 years agoExplorer
ovr_CreateTextureSwapChainGL() failed
So every tine I attempt to create the swap chains, I got the error code ovrError_InvalidParameter == -1005 with the following message returned by ovr_GetLastErrorInfo(): BindFlags not supported for O...
FOKSlab
8 years agoExplorer
HI,
I encounter the same kind of issue but no way to make "ovr_CreateTextureSwapChainGL" succeed even following the smart advises in this thread.
I checked the BindFlags offset and it is OK (36). But as soon as I set the MiscFlags & BindFlags (0 for both of them) in the swap chain descriptor, an access violation exception is raised. If I do not set them it does not generate the access violation but swapchain is not created, here is the output in this case:
{INFO} [Kernel:Default] [CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT32_1.dll
{DEBUG} [Client] Connected to the server running version (prod = 1).1.24.0(build = 547103) feature version = 0. Client runs version (prod = 1).1.24.0(build = 0) feature version = 0
{DEBUG} [Kernel:Default] [HMDState] Using default profile default
{INFO} [Kernel:Default] IAD changed to 64.0mm
{DEBUG} [SharedMemory] Creating factory
{!ERROR!} [Kernel:Error] OVR Error:
Code: -1005 -- ovrError_InvalidParameter
Description: BindFlags not supported for OpenGL applications.
I am sure Open GL context is OK since I can create textures, shaders, PBO, VAO/VBO before calling libOVR functions.
Where does the issue come from (since it seems not to come from the memory alignment) ? Have you got an idea how I can fix that ?
--- Using Visual Studio 2017 (conversion from Visual Studio 2015 solution and libOVR generated from VS2017) the sample project "OculusRoomTiny(GL)" raises the same exception on ovr_CreateTextureSwapChainGL. No issue using the sample on Visual Studio 2013 (but unfortunatelly I have to use Visual Studio 2017 with my code since I use nanogui).
I encounter the same kind of issue but no way to make "ovr_CreateTextureSwapChainGL" succeed even following the smart advises in this thread.
I checked the BindFlags offset and it is OK (36). But as soon as I set the MiscFlags & BindFlags (0 for both of them) in the swap chain descriptor, an access violation exception is raised. If I do not set them it does not generate the access violation but swapchain is not created, here is the output in this case:
{INFO} [Kernel:Default] [CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT32_1.dll
{DEBUG} [Client] Connected to the server running version (prod = 1).1.24.0(build = 547103) feature version = 0. Client runs version (prod = 1).1.24.0(build = 0) feature version = 0
{DEBUG} [Kernel:Default] [HMDState] Using default profile default
{INFO} [Kernel:Default] IAD changed to 64.0mm
{DEBUG} [SharedMemory] Creating factory
{!ERROR!} [Kernel:Error] OVR Error:
Code: -1005 -- ovrError_InvalidParameter
Description: BindFlags not supported for OpenGL applications.
I am sure Open GL context is OK since I can create textures, shaders, PBO, VAO/VBO before calling libOVR functions.
Where does the issue come from (since it seems not to come from the memory alignment) ? Have you got an idea how I can fix that ?
--- Using Visual Studio 2017 (conversion from Visual Studio 2015 solution and libOVR generated from VS2017) the sample project "OculusRoomTiny(GL)" raises the same exception on ovr_CreateTextureSwapChainGL. No issue using the sample on Visual Studio 2013 (but unfortunatelly I have to use Visual Studio 2017 with my code since I use nanogui).
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
- 3 years ago
- 4 years ago