Skip to main content
MichaelNikelsky
Up and Coming
August 28, 2015

0.7 SDK sleeps in submitFrame

Hi,

I just updated to the 0.7 SDK from the 0.6 SDK and now the submitFrame just sleeps. When doing nothing it will just sit and wait forever, the only way to make it leave the submitFrame is by clicking on our programs menubar which is kind of funny since our application is not running the UI in a separete thread.

We had this issue with another library already and it depends on something being triggered by a windows event why probably is not triggered when using Qt.

Is there a fix for this? Anyone knows what we can do tell the oculus lib to actually not sleep?

Kind regards
Michael

    16 replies

    Show previous replies
    cybereality
    Inspiring
    September 10, 2015
    Yes, that is a real issue and will be fixed in the next release. Thanks for the report.
    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
    MichaelNikelskyAuthor
    Up and Coming
    September 11, 2015
    Yes, that seems to be the same issue for me, I am getting a lot of QPaintEvents during the submitFrame.

    Thanks for figuring that out.

    Looking forward to the next release :)
    Constellation
    Up and Coming
    October 16, 2015
    Is this related to this issue: viewtopic.php?uid=13535&f=34&t=26067&start=0#p293679 ?
    cybereality
    Inspiring
    October 16, 2015
    Yes, it's probably the same issue, and it's fixed in 0.8.
    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
    thewhiteambit
    Inspiring
    October 19, 2015
    Is is propably not the only bug related, I started a little composition:

    viewtopic.php?f=20&t=26848

    Any timeframe for the 0.8 release? Why dont we get a hotfix as 0.7.0.1 Runtime or something? This is so urgent and Oculus VR wastes months of time from developers investigating in this! It is not even mentioned somewhere in the release note for known bugs. None of the developers tortured can even update to Windows 10, since 0.7 is the only one working for Windows 10. This will delay quality products for the final Oculus Rift, or will bring other incopatibilitys for Windows 10. It is nearly two months from the desired release date of 0.7 and still no fix and also no workaround!!!
    cybereality
    Inspiring
    October 19, 2015
    Yes, I understand. The next release is not that far away, and should (hopefully) resolve this issue.
    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
    Terms & ConditionsAccessibility statement