Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

<RI.Hid> Failed to create device file:

Discussion in '2018.2 Beta' started by georgeq, May 22, 2018.

  1. georgeq

    georgeq

    Joined:
    Mar 5, 2014
    Posts:
    662
    I've been working with 2018.2.0b4 for few days and this is the frist time I see this:


    <RI.Hid> Failed to create device file:
    2 El sistema no puede encontrar el archivo especificado.

    0x0000000141519A98 (Unity) StackWalker::GetCurrentCallstack
    0x000000014151FFD6 (Unity) StackWalker::ShowCallstack
    0x00000001413F036B (Unity) GetStacktrace
    0x00000001408A1AB0 (Unity) DebugStringToFile
    0x000000014158BAA5 (Unity) win::RawInput::HidDevice::Open
    0x0000000141584736 (Unity) win::RawInput::AddDevice
    0x0000000141589854 (Unity) win::RawInput::OnDeviceChange
    0x000000014158AE80 (Unity) win::Input::OnMessage
    0x000000014158EF12 (Unity) ProcessInputMessage
    0x00000001415A760E (Unity) ContainerWindow::ContainerWndProc
    0x00007FFFECC6B85D (USER32) CallWindowProcW
    0x00007FFFECC6B54C (USER32) CallWindowProcW
    0x00007FFFECC7F52D (USER32) EnumDesktopsW
    0x00007FFFED8D3F94 (ntdll) KiUserCallbackDispatcher
    0x00007FFFE9EA10A4 (win32u) NtUserPeekMessage
    0x00007FFFECC802ED (USER32) PeekMessageW
    0x00007FFFECC80156 (USER32) PeekMessageA
    0x00000001415CAB8E (Unity) MainMessageLoop
    0x00000001415CD0A8 (Unity) WinMain
    0x00000001423FD0FA (Unity) __scrt_common_main_seh
    0x00007FFFECFA1FE4 (KERNEL32) BaseThreadInitThunk
    0x00007FFFED89F061 (ntdll) RtlUserThreadStart

    When this event occurred, I had another instance of Unity open (2017.4.3f1) and the same message appeared on both projects. I cannot tell for sure, but it seems it appeared at the same time on both.
     
    Last edited: May 22, 2018
  2. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,609
  3. georgeq

    georgeq

    Joined:
    Mar 5, 2014
    Posts:
    662
    You are right, however in my case it occurred inside the editor.