Skip to main content
MikeMaLytro
New Participant
October 30, 2017

Oculus error: -1015, "WaitToBeginFrame is too far ahead of BeginFrame/EndFrame"

This error happens randomly, it does not happen right away.

This error happens when the frame rate is around 250-260 fps (Do not put the oculus head set on). The error still happens when the headset is on and the frame rate is at 90fp, but it is less frequent. This did not happen a few months ago.

I am currently using nvidia driver version 382.05.

I have tried updating to the latest 1.19 sdk and the error still happens. I have tried replacing ovr_SubmitFrame for ovr_WaitToBeginFrame, ovr_BeginFrame, ovr_EndFrame.


    3 replies

    MikeMaLytroAuthor
    New Participant
    November 1, 2017
    Native implementation.

    We tried with the latest nvidia driver yesterday and the issue still occurs.

    MikeMaLytroAuthor
    New Participant
    November 6, 2017
    The only result codes I get from ovr_SubmitFrame are -1015 and ovrSuccess(0). I never see the ovrSuccess_NotVisible result from ovr_SubmitFrame.

    I have the following code, which the statement "if (result == ovrSuccess_NotVisible)" is never true:
        do
        {
            result = ovr_SubmitFrame(m_session, frame_index, nullptr, &layers, 1);
            DebugPrintf("submitframe result %d", result);
            if (result == ovrSuccess_NotVisible)
            {
                ovrSessionStatus status;
                ovrResult sessionStatusResult;
                do
                {
                    Sleep(6);
                    sessionStatusResult = ovr_GetSessionStatus(m_session, &status);
                    DebugPrintf("session status result: %d  visible %d", sessionStatusResult, status.IsVisible);
                    VALIDATE_MSG(PlayerErrorType_Renderer, sessionStatusResult, "ovr_GetSessionStatus");
                } while (!status.IsVisible);
            }
        } while (result == ovrSuccess_NotVisible);






    MikeMaLytroAuthor
    New Participant
    November 6, 2017
    Also, I never dismiss the oculus health and safety warning, since I do not put on the headset (which does not trigger the oculus display sensor).
    Terms & ConditionsAccessibility statement