Skip to main content
Up and Coming
July 19, 2016

[Oculus Staff] Steam Builds not working

Hey guys, I have a quick question for you regarding Oculus under Steam.

I have a Oculus game made with unity that is compiling and running just fine (both with DK2 and CV1), it is set for Runtime 1.6 and all is fine and dandy.

However when I build it for Steam, the only way to launch the game is directly though the .exe on the folder, any of the Steam launchers won't work (returns "Headset not compatible" error).

Now, I know you guys have nothing to do with Steam's shannanigans, but:
  • Are there any issues between Oculus builds and Steam I should be aware of?
  • Is this a documented situation by you guys? Is there a procedure for this on your end?
  • Does anyone found any similar situations?
Thank you in advance for the help on this!

And please let me know if there are further questions.

8 replies

Up and Coming
July 22, 2016
No ideas or suggestions on this?
Inspiring
July 22, 2016
I'm not sure about this. Maybe some issue with SteamVR?
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Up and Coming
July 22, 2016
I'm not using SteamVR components at the moment, this is a simple Unity Oculus build. It works OK if I just click the .exe, however if I try to lauch the app via Steam, all hell breaks loose :(
Up and Coming
July 25, 2016
Any ideias or suggestions on what can be causing this or how to fix it?
Inspiring
July 25, 2016
If the exe runs by itself, then the Oculus SDK should be working. If you get some sort of error message when launching from Steam, that sounds to me like a Steam issue. Where does it look like the error message is coming from?
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Up and Coming
July 26, 2016
On my opinion it seems like something related with the Steam Launcher or whatever wrap they make to executables. I have configured everything on their end, paths, frameworks, that it should use on launch (Oculus), etc., no dice. I also have no error logs on Unity as well. This is really baffling :(
sh0v0r
Up and Coming
August 2, 2016
I haven't had this issue however I don't use SteamWorks DRM.
Up and Coming
August 25, 2016
So, thank you all for the help. Turned out it was a steam setup issue, it is fixed now :)

Mods, feel free to close this one down please ;)