Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Resolved "Attempting to determine the size of an unknown feature type Id [-1]." while using MockHMD

Discussion in 'XR Interaction Toolkit and Input' started by Alixar, Dec 14, 2020.

  1. Alixar

    Alixar

    Joined:
    Mar 13, 2019
    Posts:
    50
    Shameful cross-post from the general forum.

    I get hundred of thousands of errors, like shown below, when I run the game in play mode with Mock HMD. They're fired so often that Unity stutters and flickers, up to the point that I had to remove the MockHMD.

    I can't pinpoint exactly why it is happening, would you know how to fix it?
    I'm on Unity 2020.1.13f1 and URP.

    Code (CSharp):
    1. Attempting to determine the size of an unknown feature type Id [-1].
    2. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)
     
  2. hemangmaan

    hemangmaan

    Joined:
    May 30, 2020
    Posts:
    1
    I'm also having the same issue
     
  3. Alixar

    Alixar

    Joined:
    Mar 13, 2019
    Posts:
    50
    Could you figure out where it's coming from?
     
  4. showstopper-1

    showstopper-1

    Joined:
    Dec 16, 2020
    Posts:
    1
    Same issue, unfortunately. Did you manage to find a solution?
     
  5. VReynaert

    VReynaert

    Joined:
    Feb 8, 2017
    Posts:
    2
    Same issue too :/
     
  6. Alixar

    Alixar

    Joined:
    Mar 13, 2019
    Posts:
    50
    @showstopper-1 nothing yet, I think it's on Unity's end to fix this one. :(
     
  7. Matt_D_work

    Matt_D_work

    Unity Technologies

    Joined:
    Nov 30, 2016
    Posts:
    202
    please raise a bug on this. cheers!
     
  8. jthiess

    jthiess

    Joined:
    Nov 5, 2018
    Posts:
    31
    having the same issue
     
  9. Alixar

    Alixar

    Joined:
    Mar 13, 2019
    Posts:
    50
    @Matt_D_work I've created a repro project and submitted the bug!
     
    Matt_D_work likes this.
  10. bjennings76

    bjennings76

    Joined:
    Jun 15, 2013
    Posts:
    6
    In case it helps anyone, I found I'll get this error when my HMD isn't connected to my computer.

    I'm on Unity 2020.2.4f1.
     
  11. RobShocks-XR-Guide-Youtube

    RobShocks-XR-Guide-Youtube

    Joined:
    Mar 29, 2016
    Posts:
    3
    Having the same issue on Mac Unity 2020.2 when adding MockHMD
     
  12. RobShocks-XR-Guide-Youtube

    RobShocks-XR-Guide-Youtube

    Joined:
    Mar 29, 2016
    Posts:
    3
    May have found a solution by going to Project Settings > Player > Active Input Handling - Both instead of New. Fixed for now.
     
  13. jhabaa

    jhabaa

    Joined:
    Feb 15, 2021
    Posts:
    1
    Doesnt work for me. It's weird....
     
    jdoranZeltech likes this.
  14. hoanort

    hoanort

    Joined:
    Dec 8, 2019
    Posts:
    1
    Having the same issue on Mac Unity 2020.3 when adding MockHMD
    Haven't they repaired this error? Is there really no a solution... :(
     
  15. felipemolinari874_unity

    felipemolinari874_unity

    Joined:
    Oct 29, 2018
    Posts:
    1
    I'm having the same problem...
     
  16. OcularCash

    OcularCash

    Joined:
    Sep 8, 2012
    Posts:
    4
    Robshocks answer worked for me. Switching to both instead of new fixed it immediately after rebooting unity from the changes.

    Using Unity 2020.3.4f1in bootcamp

    edit: nvm, no errors after the first launch after reboot but reverted back to errors on the launches after that. Weird
     
  17. p20266677

    p20266677

    Joined:
    Oct 26, 2018
    Posts:
    3
    I am also experiencing this, and cannot use the Mock HMD on 2020.3.0f1
     
  18. kumar_191851

    kumar_191851

    Joined:
    Mar 4, 2021
    Posts:
    1
    I am also facing this error. tried both for input, still, the problem occurring with 2020.3.0f1.
     
  19. danilofaugusto

    danilofaugusto

    Joined:
    Jun 9, 2020
    Posts:
    1
    Hey man, could you share the ticket so we can follow its status?
     
    Lipoly likes this.
  20. Nayanajith89

    Nayanajith89

    Joined:
    Sep 30, 2021
    Posts:
    1
    I have tried this (robshocks solution ) but no luck. I am using Unity 2020.3.7f1 (64-bit) and MockHMD. Any other solution worked
     
  21. p20266677

    p20266677

    Joined:
    Oct 26, 2018
    Posts:
    3
    Also experiencing this issue... Please Unity, post us an answer.
     
  22. Lyje

    Lyje

    Joined:
    Mar 24, 2013
    Posts:
    169
    I updated from the legacy VR to the XR plugin system and had this issue.
    If that's what you guys did, I'm pretty sure the issue is legacy settings - which are hidden once you switch to the new system - breaking unity behind the scenes.

    Here's what fixed it for me.

    Close Unity.
    Open ProjectSettings/ProjectSettings.asset.
    Find
    m_BuildTargetVRSettings:
    and remove that entire entry (i.e. that line and everything indented beneath it).
    Open Unity.
    Hoooooopefully your project now works.
     
  23. IgnisIncendio

    IgnisIncendio

    Joined:
    Aug 16, 2017
    Posts:
    223
    That didn't work for me, unfortunately.
     
    Last edited: Feb 2, 2022
  24. unity_andrewc

    unity_andrewc

    Unity Technologies

    Joined:
    Dec 14, 2015
    Posts:
    218
    This should only be an issue in 2020.3 - a fix landed recently in 2020.3.27. Please let me know if either thing I said here disagrees with what you see so I can look into it further. Thank you!
     
    IgnisIncendio likes this.
  25. pverburg

    pverburg

    Joined:
    Mar 27, 2019
    Posts:
    1
    Has been fixed for me after upgrade! Thanks Andrew :)
     
    unity_andrewc likes this.
  26. elrojo98

    elrojo98

    Joined:
    Dec 11, 2020
    Posts:
    1
    Go to Project Settings > XR Plug-in Management > Providers and deselect everything. I have the 2020.3.15 version and in my case it worked.
     
  27. bintangsonda27

    bintangsonda27

    Joined:
    Jan 13, 2022
    Posts:
    1
    try to change the render mode to the multi pass instead of single pass