Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Bug Upgrade to UITK to preview 11 and all editor windows that use UITK are now blank.

Discussion in 'UI Toolkit' started by Chris-Trueman, Nov 15, 2020.

  1. Chris-Trueman

    Chris-Trueman

    Joined:
    Oct 10, 2014
    Posts:
    1,256
    After upgrading to preview 11 every editor window, inspector and property drawer that uses UITK now renders blank. Okay well not everything, the gradient that is shown in a color field is rendered. It seems like everything still reacts to input, but you're flying blind. I didn't test it at runtime to see if that was affected. I had to go into the manifest to remove the package and revert it back to preview 9.
     
  2. etienne_unity

    etienne_unity

    Unity Technologies

    Joined:
    Aug 31, 2017
    Posts:
    102
    Hi @Chris-Trueman

    This is not expected :) Which version of Unity are you using, and on which platform?

    If you can, please report a bug, and we'll look into this.
     
  3. andrew-lukasik

    andrew-lukasik

    Joined:
    Jan 31, 2013
    Posts:
    239
    Same, `2020.1.13f1` / Win10 here.

    EDIT: Yes, I'm using new Input System.
     
    Last edited: Nov 16, 2020
  4. Chris-Trueman

    Chris-Trueman

    Joined:
    Oct 10, 2014
    Posts:
    1,256
    2020.1.11f1 on Windows 10. When I get some time I try to get a repro project going.
     
  5. Chris-Trueman

    Chris-Trueman

    Joined:
    Oct 10, 2014
    Posts:
    1,256
    So I tried to create a quick repro of the issue and cannot. I get 7 warnings about TMP_ContextMenus trying to to be created buy already existing every time the project is open.

    Another problem, no indication of what you did with this version. No release notes, no indication that you guys even put out an update.
     
  6. Kirsche

    Kirsche

    Joined:
    Apr 14, 2015
    Posts:
    120
    It was just unlucky timing because the update came out right before the weekend. They'll address it soon.

    For me it worked on 2021.1.0a4 with all the new features (finally RichText support <3) but you can't use the new InputSystem with it yet (Cyclic Reference Exception).
     
  7. Chris-Trueman

    Chris-Trueman

    Joined:
    Oct 10, 2014
    Posts:
    1,256
    Ah that explains the problem, I'm using the new Input System. Damn it Unity WHY?!?!?!?!?
     
  8. antoine-unity

    antoine-unity

    Unity Technologies

    Joined:
    Sep 10, 2015
    Posts:
    733
    We're working on the communication :)
     
  9. MattM_Unity

    MattM_Unity

    Unity Technologies

    Joined:
    Aug 18, 2017
    Posts:
    45
    Hello @Chris-Trueman @andrew-lukasik ,

    I'm on Windows 10, and tried to repro this issue on 2020.1.14f1. I ran an internal project entirely made with UITK, containing all sorts of custom Editor windows. I first set the preview version to 9, opened everything to made sure there was no blank window. I then upgraded to preview 11 and everything was displaying as it should.

    Could you please give me a bit more infos?

    - Are you still having those issues? If yes, could you download 2020.1.14f1 and tell me if it still happens?
    - What graphics API are you using? (you can check through Edit > Project Settings > Player > Other settings)
    - What color space are you using? (you can check through the same path as above)
    - What is your GPU?

    Thank you!
     
  10. antoine-unity

    antoine-unity

    Unity Technologies

    Joined:
    Sep 10, 2015
    Posts:
    733
    Can you guys confirm you're both using the Input System package? Our best guess is that the windows going blank is a consequence of the cyclic dependency error.
     
  11. b4gn0

    b4gn0

    Joined:
    Jul 26, 2019
    Posts:
    119
    I have the same problem, how long do you think it will be needed before it gets fixed?
     
  12. antoine-unity

    antoine-unity

    Unity Technologies

    Joined:
    Sep 10, 2015
    Posts:
    733
    We are working on preview.12 release as we speak, it should be out the door tomorrow morning at the latest.

    Updating your TextMeshPro package version to 3.0.3 will make these warnings go away.
     
  13. andrew-lukasik

    andrew-lukasik

    Joined:
    Jan 31, 2013
    Posts:
    239
    Thank you. preview 12 fixed the issue for me.
     
  14. Chris-Trueman

    Chris-Trueman

    Joined:
    Oct 10, 2014
    Posts:
    1,256
    @MattM_Unity The issue goes away after upgrading to preview.12. I believe it was the InputSystem incompatibilities causing the issue.

    Thank you. I thought I had everything up to date on the project I was working on, this fixed the warnings.
     
  15. MattM_Unity

    MattM_Unity

    Unity Technologies

    Joined:
    Aug 18, 2017
    Posts:
    45
    Great! Happy those issues are gone :)