FOVE SUPPORT CENTER

Headset display not turning on through HDMI

Comments

32 comments

  • Avatar
    Remco

    Hi Marcus,

    After connecting the headset to the HMDI port on your dedicated GPU, and launching the FOVE runtime and Compositor, some logging will have been output to the FoveLog.txt, which can be found in: C:\ProgramData\FOVE\Logs.Could you send us this file?

    And thank you for your compliment! It is nice to see that our hard work is being appreciated!

  • Avatar
    Kelley Hendrix

    Just FYI...  If you are using SLI, I had to disable it before the Fove would display anything.

  • Avatar
    eric b

    I have this issue as well :-(    I've tried two PC's, i have another at home i can try tonight.  My FOVE log is available if you need it, although i see the lines :


    [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

    and that looks no beuno

     

    Edit: Tried the headset on a coworkers machine, nvidia 970 gpu, tried swapping second monitor hdmi for the headset but still no display detected (same error above in the logs).  The FOVE config tool shows me what the headset should be showing (a star scene) and moves around as the headset moves, it also displays the image of my eyes taken from inside the headset. just seems that the hdmi display isn't working. help!

  • Avatar
    Marcus R

    I believe I am getting a different error message:

    ---

    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7F47A0658: 126
    [RNDR] AMD not foud.
    Failed to find direct-mode backend, retrying in 1s.
    New log client 0.9.3 C:/Program Files\FOVE\bin\FoveCompanion.exe
    [RNDR] Acquiring rendering backend...

    ...

    Failed to find direct-mode backend, giving up.
    Compositor could not find HMD display

    ---

    you can read the entire log at http://pasteall.org/224978

    (notice: "[RNDR] AMD not foud." typo)

    Thanks,

     

    EDIT: I only have this PC to try the headset on, I might be able to try it on another if you really need me to.

  • Avatar
    Maz

    Thanks for the log file. We're looking at this issue now. Do you have the latest nvidia drivers? And do you have multiple GPUs in your system? We're testitng different GPU configurations now and seeing if we can replicate the problem.

    I did fix the typo. :P

  • Avatar
    Marcus R

    I am running the newest driver through geforce experience (378.49), I only have the one 660TI. the system is about 7 months old (since last reinstall) and I have done 2 system recoveries (not sure if it matters - I have experienced other driver issues from this).

  • Avatar
    eric b

    i'm trying on 2 different computers, both have the latest drivers (had to update before the FOVE installer would run).  one system has a nvidia 1060, the other has dual 970, and i've tried with AND without SLI mode, no luck.

  • Avatar
    Maz

     

    @Marcus I'll see if we can find a way to replicate the headset screen not coming on with just a single older video card. The fact that it appears as a monitor when you used a dvi adapter makes me wonder if its a DirectMode or HDCP problem.

    @eric could you start a new post in the Troubleshooting section and include your PC specs, and full log and dxdiag output and a description of what you're seeing on that machine, rather than derailing this thread any more. Your problem seems to be different.

  • Avatar
    Marcus R

    I have updated to version 0.10.0, and just to let you know I get the same error from this release.

    Log: http://pasteall.org/226768

  • Avatar
    Marcus R

    Any news on the issue? I am reading peoples positive experiences with the steam beta and I am eager to try it out.. is there anything I can do?

  • Avatar
    Maz

    @Marcus is there any way for you to test it on a pc with a newer nvidia graphics card? We don't have anything 6xx series in the office and I'd like to try and determine if that is the problem. We've also added some more descriptive logging in the compositor startup that might help us debug this problem and that'll go out in our next release in a week or so. 

    Does anything get reported to your event viewer when this happens? i'll keep hunting for the cause of this error message, otherwise just make sure you try the new version of the SDK each time we release it. 

  • Avatar
    Marcus R

    @Maz some time next week I can probably discuss with my schools tech staff to install the driver on my workstation - it has a Quadro 4000, which is newer, but not in the geforce series.

    Otherwise I can wait for the update and try again. I am not sure about the event viewer - I have never used it before. Looking through the events I see a couple that are FOVE-related:

    1a

    1b

    2a

    2b

    3a

    3b

    These are what I could find, I have a couple of security events as well happening around the time, though I am not sure if any of this is delicate info.

  • Avatar
    Arno

    I have the same Problem.

    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveConfigurationTool.exe
    Initialising config tool.
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    Starting runtime...
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveServiceHost.exe
    Service started. Initialising FoveVR
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    FoveVR ctor
    Loaded module PositionTracking
    Loaded module EyeTracking
    Connected to headset with fw50
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveConfigurationTool.exe
    Creating FVRHeadset object (000001E997412C40)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(7, Gaze, Orientation, Position)
    Launched FoveCompositorApplication.exe
    Launched FoveCompanion.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompanion.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF65E6A81A8: 126
    [RNDR] AMD not foud.
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (00000220C8644430)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    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
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    Destroying FVRHeadset object (00000220C8644430)
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompanion.exe
    Creating a compositor client (000001BF338A1470) of type 131072
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FFFF9F8ECD0: 126
    [RNDR] AMD not foud.
    Creating FVRHeadset object (000001BF3363FB10)
    ClientCap final: ClientCapabilities(2, Orientation)
    Creating FVRHeadset object (000001BF33641680)
    ClientCap final: ClientCapabilities(7, Gaze, Orientation, Position)
    Trying to connect to service as bf5e6f21-895f-49f8-8a00-00bf1cd03fe5
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Launched FoveCompositorApplication.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    [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
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (000001485A4CDC00)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(2, Orientation)
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    Destroying FVRHeadset object (000001485A4CDC00)
    Trying to connect to service as 49e96b5c-3ac3-4f12-8957-ccf318d5ce82
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Trying to connect to service as 653b042c-63b1-401f-b8ff-6efdb2246036
    Launched FoveCompositorApplication.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    [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
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (000001C1D5B6D3C0)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(2, Orientation)
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    Destroying FVRHeadset object (000001C1D5B6D3C0)
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Trying to connect to service as 0d5cfaf5-0829-46ae-ac4c-6774560be017
    Launched FoveCompositorApplication.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    [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
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (000002BFD66400C0)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(2, Orientation)
    Destroying FVRHeadset object (000002BFD66400C0)
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Trying to connect to service as 36a612f0-6785-45ed-91fc-9a7cf985eec7
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Launched FoveCompositorApplication.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    [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
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (000002AA39BFC9E0)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(2, Orientation)
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    Destroying FVRHeadset object (000002AA39BFC9E0)
    Trying to connect to service as 7f1bd636-06cc-4711-a38b-8d4aabe09984
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Trying to connect to service as 0e0d2698-cbb1-4e43-8108-10d3aaf970a5
    Launched FoveCompositorApplication.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    [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
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (000001AAD6720C40)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(2, Orientation)
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    Destroying FVRHeadset object (000001AAD6720C40)
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Trying to connect to service as 7570ebae-d3fc-407e-9a77-b7b3c0edfd50
    Launched FoveCompositorApplication.exe
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia API found
    Unable to load 00007FF7466BD328: 126
    [RNDR] AMD not foud.
    [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
    Unable to set Nvidia high priority hint.
    Unable to initialize D3D swap chain.
    Initialize("HMD View") failed
    Fatal error attaching window to HMD
    New log client 0.9.2 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Creating FVRHeadset object (000001D3E91FB450)
    Loaded config file at C:\ProgramData\Fove\FoveVR.config
    ClientCap final: ClientCapabilities(2, Orientation)
    Destroying FVRHeadset object (000001D3E91FB450)
    REPORT: Did not receive response, starting new connection
    InitiateConnection: Unable to send heartbeat
    Stopping runtime...
    Service sent a STOP signal from the OS
    Terminate messaging thread.
    Terminate SDK state monitor.
    Trying to connect to service as 19f32643-354b-4b47-9a09-a05333690a17
    FoveVR destroy
    Disconnecting from headset
    FoveVR stopped
    FoveVR over and out!
    FoveVR dtor

  • Avatar
    Arno

    after installing 10.0 the Display works.

    thank you

  • Avatar
    Marcus R

    I am very excited to hear that, I will try version 0.10.0 later today, thanks for reporting

     

    EDIT: I realize now that the newest 0.10.0 was what I tested almost two weeks ago, which is the version that does not work - for me.

    Happy that Arno was helped by the release though.

  • Avatar
    Maz

    @Marcus

    The new runtime should have added additional logging to find the cause of the case where the nvidia API was failing silently. Please paste us a new Fove log.

    Also, what is your configuration with monitors? Specifically, what resolution monitor plugged into what kind of port on the video card and whether you are using adapters for each connection.

    We've found that any adapter in the way of the Fove's HDMI connector can cause these problems and that we needed active DP to HDMI adapters. If possible, try the fove connected directly to a HDMI port with one monitor connected (so you can see what you're doing).

    Let me know.

    Maz

  • Avatar
    Kevin Vanderkley

    I also have this issue with no screen displayed - Maz any luck with your issue? It Is a pain having this for weeks with nothing working! - I notice many other VR devices have similar issues.

    IN reply to :

     

    Remco (FOVE)

    Mar 2, 14:56 JST

    Hi Kevin,

    The FOVE box should come included with instructions that direct you towards http://getfove.com/setup If those were missing, a mistake was made at assembly. My apologies.

    Sorry to hear you are having trouble getting the headset to work. It seems like our compositor is unable to enable direct-mode on your system. Could you try running the headset in extended mode? This can be achieved by changing the Fove settings file (Turn off the FOVE runtime, and press the 'Edit Config File' button under the 'Configuration' sub-menu). In the settings file, please add the following line:

    COMPOSITOR_DISPLAY_MODE=1

    This should enable extended mode. Are you seeing the starry sky inside your headset? Or maybe a windows background?

    Kind regards,

    Remco

    I couldn't get anywhere, so I gave the headset to my IT Guy, Scott,  to try on his computer to see if it might be my computer, or my lack of knowledge. His computer is listed at the start to the config file edit log.

     

    (Keep in mind my computer was even faster than his, and I updated my video card to a faster one than his also to see if that would help previous to giving him the headset to try, and it didn't help me.)

     

    The display has never lit up at all. - either the hdmi cable is not working or I'm missing something. Should there be anything visible at any time - I would of thought even a no connection screensaver or something would be on it, like when a monitor is unplugged?  (the camera in the HMD works, and the locator camera picks up the white position sensors in the HDM to sense the location of the HDM. - these have been visible at times on the viewing section on the software.) SO usb cables are working and power is to the HDM - I would assume at least something would be visible on the HDM screen in the Headset. Never even a flicker of light.

     

     

    If I try it without the configuation edit I get this:

     

    Starting compositor...

    Stopping compositor...

    Starting runtime...

    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveServiceHost.exe

    Service started. Initialising FoveVR

    Loaded config file at C:\ProgramData\FOVE\FoveVR.config

    COMPOSITOR_DISPLAY_MODE: 0

    FoveVR ctor

    Loaded module PositionTracking

    Loaded module EyeTracking

    Connected to headset with fw50

    Launched FoveCompositorApplication.exe

    Launched FoveCompanion.exe

    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe

    Loaded config file at C:\ProgramData\FOVE\FoveVR.config

    COMPOSITOR_DISPLAY_MODE: 0

    [RNDR] Acquiring rendering backend...

    [RNDR] Nvidia API found

    Unable to load amdlvr64.dll: 126 The specified module could not be found.

    [RNDR] AMD not found.

    Failed to find direct-mode backend, retrying in 3s.

    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveCompanion.exe

    Companion starting

    Loaded config file at C:\ProgramData\FOVE\FoveVR.config

    COMPOSITOR_DISPLAY_MODE: 0

    Creating a compositor client (000002320E32F7E0) of type 196608

    [RNDR] Acquiring rendering backend...

    Creating FVRHeadset object (00000232101BB880)

    ClientCap final: EFVR_ClientCapabilities(2, Orientation)

    Trying to connect to service as eec0a82e-2fae-4133-bdf1-2aa557fac810

    RemoteRequester(tcp://127.0.0.1:8307) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Destroying compositor client (000002320E32F7E0) of type 196608

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    RemoteRequester(tcp://127.0.0.1:8307) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    InitiateConnection: Unable to send heartbeat

    Destroying FVRHeadset object (00000232101BB880)

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    No calibration data exists for profile: 0

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Critical error in companion: Unable to send heartbeat

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    [RNDR] Acquiring rendering backend...

    [RNDR] Nvidia API found

    Unable to load amdlvr64.dll: 126 The specified module could not be found.

    [RNDR] AMD not found.

    Failed to find direct-mode backend, retrying in 3s.

    Service sent a STOP signal from the OS

    Stopping runtime...

    Terminate messaging thread.

    Terminate SDK state monitor.

    FoveVR destroy

    Disconnecting from headset

    [RNDR] Acquiring rendering backend...

    [RNDR] Nvidia API found

    Unable to load amdlvr64.dll: 126 The specified module could not be found.

    [RNDR] AMD not found.

    Failed to find direct-mode backend, retrying in 3s.

    FoveVR stopped

    FoveVR over and out!

    FoveVR dtor

     

    I made the change to the config file and get the starry sky on my normal monitor, but the headset is still dark. Here is the log file, the key issue (I think) is highlighted:

     

    PC: Win10 Pro x64, i7-4770K, GTX980, latest drivers as of 25th Feb.

     

    Launched FoveCompositorApplication.exe

    Launched FoveCompanion.exe

    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe

    Loaded config file at C:\ProgramData\FOVE\FoveVR.config

    COMPOSITOR_DISPLAY_MODE: 1

    [RNDR] Acquiring rendering backend...

    [RNDR] Nvidia API found

    Unable to load amdlvr64.dll: 126 The specified module could not be found.

    [RNDR] AMD not found.

    Creating FVRHeadset object (0000011989991DA0)

    ClientCap final: EFVR_ClientCapabilities(2, Orientation)

    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveCompanion.exe

    Companion starting

    Loaded config file at C:\ProgramData\FOVE\FoveVR.config

    COMPOSITOR_DISPLAY_MODE: 1

    Creating a compositor client (00000225E5710180) of type 196608

    [RNDR] Acquiring rendering backend...

    Creating FVRHeadset object (00000225E70B6F80)

    ClientCap final: EFVR_ClientCapabilities(2, Orientation)

    Trying to connect to service as 889839f4-89ff-4e0e-b322-7f2c89557ee1

    Compositor could not find HMD display

    RemoteRequester(tcp://127.0.0.1:8307) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Destroying compositor client (00000225E5710180) of type 196608

    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

    Vsync wait object invalid, skipping frame sync callback thread.

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    REPORT: New client accepted 889839f4-89ff-4e0e-b322-7f2c89557ee1

    Connection to service succeeded!

    Destroying FVRHeadset object (00000225E70B6F80)

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General

    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server

    Critical error in companion: Unable to send heartbeat

    No calibration data exists for profile: 0

    Marking client stale: 889839f4-89ff-4e0e-b322-7f2c89557ee1

    REPORT: dropping stale client: 889839f4-89ff-4e0e-b322-7f2c89557ee1

    Stopping compositor...

  • Avatar
    Marcus R

    I seem to be getting the same error message as Kevin; Unable to load amdlvr64.dll: 126 The specified module could not be found.

     

    you can find my entire log at http://pasteall.org/279729

  • Avatar
    Kevin Vanderkley

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/ce5960b1-98be-487c-9263-c08cf22a825b/loading-dynamic-dll-issue-with-error-code-126?forum=visualstudiogeneral

     

    Hi Marcus and support staff.

    Whilst googling this error I found this thread - I have no idea if it is related or helpful?

    Also I don't suppose booting in safe mode might be worth a try?  I didn't try it.

    As far as I'm aware, other people have their headsets working on the NVidia cards, so I can't understand why they don't work on ours.

     

     

     

  • Avatar
    Remco

    The error: Unable to load amdlvr64.dll: 126 has no further implications for NVIDIA users. While trying to acquire direct mode we try both nvidia and amd cards. This error happens when we can't find the appropriate AMD drivers. For the next release, we removed this error for NVIDIA users.

    Marcus, could you try setting COMPOSITOR_DISPLAY_MODE=1 in the Fove config file? There is an option in the FOVE tray menu, when the service is disabled, to do so.

  • Avatar
    Marcus R

    I opened the foveVR.config in notepad++ and this is the content:

    EYE_TRACKING_EYES=3
    KEEP_COMPOSITOR_ALIVE=FALSE

    I added the line and ran the fove client, still no light in the HMD this is the log: http://pasteall.org/282949

  • Avatar
    Kevin Vanderkley

    When you say for the next release, I assume the next release of the install software. When are we expecting that?

  • Avatar
    Marcus R

    So I have ben following the forums the past 2 months, really not much happening lately, I am concerned.

    Version 0.11.4 did not fix the issue, log: http://pasteall.org/367905

     

    I hope this issue can be fixed, though I have now finally decided to pack away my headset after it lying useless on top of my PC for 3 months.

    Summer break is coming up, having the headset working would be amazing.

  • Avatar
    Kevin Vanderkley

    Hey Marcus, 

    Remco logged onto my computer remotely and tried to find a solution on my headset with no luck. 

    It should work but he couldn't figure it out why it wouldn't. He was going to go back to the head engineers and try and figure something out. 

    My headset worked on another new freshly built top end gaming computer, so the device is physically ok. 

     

    Walked past another brand one in the shop yesterday and was tempted to buy that, but abstained.

    Can only wait unfortunately.  

     

  • Avatar
    Remco

    Hi Marcus,

    The problem seems to only occur on specific devices. NVIDIA drivers are not reporting that the FOVE 0 is connected to an HDMI port, and as a result our compositor can't connect to the display.

    We are investigating why this is the case, but so far to no avail.

  • Avatar
    Kevin Vanderkley

    Any progress on this issue yet Remco? 

     

  • Avatar
    Remco

    Hi Kevin,

    We are actually in the process of QA'ing a built that potentially solves some problems for systems that e.g. use NVIDIA optimus (systems with both an integrated and external GPU), but not all problems have been solved yet. I know it is taking a long time, but some issues are very difficult to reproduce for us on this end.

    My apologies for testing your patience.

  • Avatar
    Alexander Irvine

    I am also having a problem connecting using a Quadro Graphics Card (K420). Connects the cameras and to orientation sensors fine, windows recognises as a monitor, but does not produce any light in either direct or extended mode. The log mentions a hearbeat error. Geforce Experience says the system is 'VR Ready'.

    The HMD works on an old laptop with a poor geforce graphics card, in extended mode, but nothing can push frames to the compositor. I should get a more powerfull gaming card, but I will be using it for eye tracking research displaying static photos (so not a great investment).

    I'm assuming the Quadro error is probably a similiar driver related issue? Would be great if I could get a fix for this?

  • Avatar
    Alexander Irvine

    Hi Any updates/time estimate on that build? Just trying to weigh up whether I should get a new graphics card or not. I'm not doing any intense gaming with the Fove so didn't think it would be strictly necessary!

  • Avatar
    Kevin Vanderkley

    Still got the Fove sitting in the box waiting on a solution.

    I may get a new build computer once we move offices, so could possibly then get it working, but in the meantime

    I just ordered the DJI VR Headset to use for my Phantom 4, which I can also use for gaming, watching movies or other uses. Hopefully that will have less issues. I guess it wont depend on the hardware in the computer.

     

Please sign in to leave a comment.