Author Topic: BUG: Label text not showing NGUI 3.11.3 Unity 5.4.2  (Read 4268 times)

fretnoize

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 16
    • View Profile
BUG: Label text not showing NGUI 3.11.3 Unity 5.4.2
« on: May 26, 2017, 01:53:56 AM »
I can't seem to get labels to display text (I've only tried Unity fonts)
using: NGUI 3.11.3 and Unity 5.4.2

steps:
-Create a new project
-Import NGUI
-Press alt-shift-L to make a new label
-Choose arial (or any other font)
Results: no text...

I cleared out the NGUI folder and replaced it with an older version from another project (I forget the version) and then I loaded the project and label text shows up.  I'll just use this version, so it's not a road block for me.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: BUG: Label text not showing NGUI 3.11.3 Unity 5.4.2
« Reply #1 on: June 05, 2017, 03:25:19 AM »
When I try this it works as expected. Do you have any more details?

fretnoize

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 16
    • View Profile
Re: BUG: Label text not showing NGUI 3.11.3 Unity 5.4.2
« Reply #2 on: June 05, 2017, 11:07:42 AM »
I don't really have much more info... I was having trouble getting the text to show up in labels in my project, so I thought maybe I messed up something with NGUI... accidentally deleted a file or something, for example... So, I decided to start a new project and import NGUI just to be sure... and it was still happening... then I tried another new project, and this time I dragged in the NGUI folder from a previous project instead, looks like it was 3.9.9 and that worked... so i removed the NGUI folder in the project I'm really working on and brought that 3.9.9 folder into the project and loaded it up, and all the text for the labels appeared.

not sure how relevant it is but:
Using win 10 on a mac book pro 2012 retina

If this doesn't help, I can try repeating it at some point, maybe a reboot cleared things up or something. It did seem solidly reproducible on my end though, which is why I reported it. hmm.