cancel
Showing results for 
Search instead for 
Did you mean: 

(SDK 0.8) ovr_CreateSwapTextureSetGL() failure

dudeman21
Honored Guest
I am using SDK 0.8 with the latest nvidia drivers (361.43), attempting to integrate the SDK into my own engine. Unfortunately, when running multiple monitors, it seems that ovr_CreateSwapTextureSetGL() always returns -1006 ("ovrError_ServiceError"). If I disable all but 1 monitor everything functions as expected, but when multiple monitors are active it fails every time.

Engaging my google-fu, it seems like I am not the only one to run into this issue, but I have not heard found any official sources to fix it other than "use DirectX instead" or "just use a single monitor." Is this an issue that is already resolved in SDK 1.0?
4 REPLIES 4

thewhiteambit
Adventurer
For me it runs with multiple Monitors, are you using nVidia Sourround when using all monitors?

dudeman21
Honored Guest
No, it's just a simple multi-monitor setup. I should mention, however, that I am running 3 monitors from two separate 980 GTX cards. Even the SDK sample fails on the same call, sadly.

dudeman21
Honored Guest
Just so there's a (semi-)answer here, I went out and bought a few DisplayPort cables so I could hook all of my monitors up to a single card and this function succeeds. If you have multiple monitors output from multiple GPUs, it seems this function will fail every time.

PhM
Honored Guest
Same here with two AMD cards, HD7870 GHz + R9 390 Nitro latest driver 16.3.2. The rift is on the R9, the PC screens on the 7870, this is definitely a bug, it seems that it can't properly figure things out.