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

Having multiple problems, RC3, everything I do takes 10X as long.

Discussion in 'UGUI & TextMesh Pro' started by ForceVFX, Nov 29, 2014.

  1. ForceVFX

    ForceVFX

    Joined:
    Jan 21, 2011
    Posts:
    611
    I am pulling my hair out here,
    Win 8.1 64 bit Unity Pro..same project I have been on for 8 months..
    Updated to latest version RC3(I skipped RC1/2)..Some internal process was added, some new background thread, what ever it is, unity editor, just sits there frozen,for long periods of time, then reacts,
    • I select a scene object, the inspector now takes 5 secs to display the components,
    • When I open my projects, it takes 3-5 min..
    • When I rebake/bake 3 1024 UI texture atlas.2 mins..when I hit play..up to 4 minutes..of nothing..then normal play and frame rate...
    • Every time I hit save scene, the editor fires all my public UI Methods (all my buttons get an OnClick event- causing editor errors,every time, all day, every day-it gets really annoying fast (my player is spawned and does not exist in edit mode, even when I just come back from another window).ie:
      NullReferenceException: Object reference not set to an instance of an object
      PlayerUIControls.engine_off ()
    • I get this error every 5 mins...and I know those files are deleted:Refresh case sensitivity failure. Asset: Assets/Models/Textures/Thumbs.db ; Metafile: Assets/Models/Textures/Thumbs.db.meta
    This is not the same software I used last week., something is very wrong..after 2.5 years, never has it been this slow..how could I be the only one?? My Machine-the same, the project-the same..I will have to go back to an earlier version, to actually work with unity..I am stuck, I have dropped 3 gigs out my project, thinking that might be the problem, nope..Same exact behavior

    (my machines specs and performance are all the same, the only change was Unity 4.6 RC3)
    p-
     
    Last edited: Nov 29, 2014
  2. phil-Unity

    phil-Unity

    Unity UI Lead Developer Unity Technologies

    Joined:
    Nov 23, 2012
    Posts:
    1,226
    if someone could report a bug that would be helpful. after so long in open beta and over a year in closed beta we haven't had anyone report this sort of slow down.
     
  3. Ostwind

    Ostwind

    Joined:
    Mar 22, 2011
    Posts:
    2,804
    What, are you kidding? he means the built in bug reporter feature and not forum posts which could attract trolls.
     
    phil-Unity likes this.
  4. ForceVFX

    ForceVFX

    Joined:
    Jan 21, 2011
    Posts:
    611
    It is the Canvas Scaler component, introduced in Unity 4.6 latest build, RC3..it is trying to create font atlas sprites for all my text, all 18 languages...all the time..this requires a lot of ram, the less ram available, the slower unity editor response, also, Sprite Packer will also, grab huge amounts of ram., the more sprites, the more it has to go thru the virtual list, causing the editor to 'freeze' (it is just thinking!! - solution - turn off sprite packer, buy Texture Packer Pro, it just faster..period..
     
    Omaek likes this.
  5. phil-Unity

    phil-Unity

    Unity UI Lead Developer Unity Technologies

    Joined:
    Nov 23, 2012
    Posts:
    1,226
    Interesting, Canvas Scaler shouldn't have anything to do with creating font atlas's so i'm not sure why you'd be seeing that behaviour.

    As for the sprite packer i believe there has been work done to it in 5.0 which i dont think ever made it to 4.6. although if you're noticing it to just freeze the editor please report a bug and the correct people will dig into it as that not something we want. As a FYI the packer should only run when you hit play or when you build so again if you're seeing it doing things outside those two cases we would like to know about it..
     
  6. ForceVFX

    ForceVFX

    Joined:
    Jan 21, 2011
    Posts:
    611
    I just had to get some feedback, to make sure it was worth 'Bug' status...still not sure, but pretty sure it close to this: Canvas Scaler component, introduced in Unity 4.6 latest build, RC3..it is trying to create font atlas sprites for all text, and is not playing nice with Sprite Packer - 'On' all the time setting..
    Code (CSharp):
    1. ArgumentOutOfRangeException: Argument is out of range.
    2. Parameter name: index
    3. System.Collections.Generic.List`1[UnityEngine.UI.ICanvasElement].get_Item (Int32 index) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/List.cs:633)
    4. UnityEngine.UI.CanvasUpdateRegistry.PerformUpdate () (at C:/BuildAgent/work/d63dfc6385190b60/Extensions/guisystem/guisystem/UI/Core/CanvasUpdateRegistry.cs:107)
    5. UnityEngine.Canvas.SendWillRenderCanvases () (at C:/BuildAgent/work/d63dfc6385190b60/artifacts/EditorGenerated/UICanvasBindings.cs:152)
    6. UnityEngine.Canvas.ForceUpdateCanvases () (at C:/BuildAgent/work/d63dfc6385190b60/artifacts/EditorGenerated/UICanvasBindings.cs:153)
    7. UnityEditor.DrivenRectTransformUndo.ForceUpdateCanvases () (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/DrivenRectTransformUndo.cs:17)
    8. UnityEditor.Undo.Internal_CallWillFlushUndoRecord () (at C:/BuildAgent/work/d63dfc6385190b60/artifacts/EditorGenerated/UndoBindings.cs:152)
    And I can not get out of this loop!! I deleted 1 sprite..and now the virtual sprite atlas, is corrupted..breaking my UI and hours of work..on a final release..
    Code (CSharp):
    1. Trying to add Damage_Panel (UnityEngine.UI.Image) for graphic rebuild while we are already inside a graphic rebuild loop. This is not supported.
    2. UnityEngine.CanvasRenderer:RequestRefresh()


    p-
     
    Last edited: Dec 4, 2014
  7. phil-Unity

    phil-Unity

    Unity UI Lead Developer Unity Technologies

    Joined:
    Nov 23, 2012
    Posts:
    1,226
    Yea i'm not sure how the Canvas Scaler would be related but it sounds like a pretty major issue which we'd love to take a look at if you're able to find the time to break it out into a bug. If you like PM me with a repo link / access and i can take a look.