FOVE SUPPORT CENTER

Calibration crashes WIN10

Completed

Comments

7 comments

  • Avatar
    Lochlainn Wilson

    Hi Patrik,

    Can you please provide some output from the config tools log?

    Please update your SDK to the latest version, if it is not already. 

    I want to clarify, this is the initial calibration and you are not using any content at the time that this happens? Sorry for the delay.

    Best Regards,

    Lochlainn

    0
    Comment actions Permalink
  • Avatar
    Patrik Mrázek

    Hello again,

    no problem I am glad I can get a support, I am also aware there is a big time shift between us :)

    My SDK is currently at version 0.10.0 as this is the latest I found.

    I am not using any content when trying to calibrate and Oculus services are all disabled.

    The very first initial calibration failed as all others did (if this is what you mean) so these calibration attempts are started from the tray menu with "Restart Calibration" option. 

    Here's the log and thank you again for any help.

    New log client 0.10.0 C:/Program Files\FOVE\bin\FoveCompanion.exe
    [RNDR] Acquiring rendering backend...
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    EYE_TRACKING_EYES: 3
    KEEP_COMPOSITOR_ALIVE: TRUE
    Creating a compositor client (00000264A8D72CE0) of type 131072
    [RNDR] Acquiring rendering backend...
    Creating FVRHeadset object (00000264A8D71CC0)
    ClientCap final: ClientCapabilities(2, Orientation)
    Creating FVRHeadset object (00000264A46EB930)
    ClientCap final: ClientCapabilities(7, Gaze, Orientation, Position)
    Trying to connect to service as e5928ec0-0456-4f58-80ec-7ae796f11497
    Connection to service succeeded!
    REPORT: New client accepted e5928ec0-0456-4f58-80ec-7ae796f11497
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    REPORT: Did not receive response, starting new connection
    Compositor client heartbeat error: Unable to send heartbeat
    Launched FoveCompositorApplication.exe
    New log client 0.10.0 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    EYE_TRACKING_EYES: 3
    KEEP_COMPOSITOR_ALIVE: TRUE
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF6C9CF2928: 126
    [RNDR] AMD not foud.
    Creating FVRHeadset object (000002DE7CF220E0)
    ClientCap final: ClientCapabilities(2, Orientation)
    [NVDA] No displays found for vendor ID: 25170
    [NVDA] No displays found for vendor ID: 25170
    [NVDA] No displays found for vendor ID: 25170
    Compositor could not find HMD display
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    0
    Comment actions Permalink
  • Avatar
    Lochlainn Wilson

    Unfortunately there is not enough information in our log to understand the issue.

    We will do a public release shortly that may resolve this issue. I am sorry for the inconvenience. As it is silently crashing, we will need the new versions improved logging to understand why.

    I am sorry for the inconvenience.

    Best Regards,

    Lochlainn (Fove)

    0
    Comment actions Permalink
  • Avatar
    Lochlainn Wilson

    In the mean time can you show us any strange output in your event viewer -> windows logs -> application window?

    It looks like this.

    A quick intro here just incase: https://www.digitalmastersmag.com/magazine/tip-of-the-day-how-to-find-crash-logs-on-windows-10/

    0
    Comment actions Permalink
  • Avatar
    Patrik Mrázek

    Let's wait for the new version than. Thank you for your support for now and here's the requested information




    0
    Comment actions Permalink
  • Avatar
    Lochlainn Wilson

    Has your issue been resolved?

    0
    Comment actions Permalink
  • Avatar
    Patrik Mrázek

    Yes, the last update fixed it. Thank you, good job, guys!

    0
    Comment actions Permalink

Please sign in to leave a comment.