Why do the editor fonts turn to poopie??

I was running my scene in the editor and just clicked on a game object in the asset pane and was about to drag it into another game object in the hierarchy pane, when my fonts turned to blocks of white. (see screen shot) I can reproduce this regularly. Using the latest download and OS 10.5.8 on a Mac Mini w/ 2GB RAM and 64MB video memory. It can only be fixed if I restart.

any insights appreciated,
Joe

432873--15041--$Picture 9.png

If you can reliably reproduce this behavior please submit a bug report with the exact steps required to reproduce this bug. Give me the case number of the bug and I’ll take a look at it. :slight_smile:

Hi Shawn,

The bug ID is 382923. http://fogbugz.unity3d.com/default.asp?382923_vslu76gi

If you need any more info, please let me know!
Thanks!
Joe

the 64 meg of video memory seems a subtle clue.

Yeah, I was wondering about that. But it’s not a big project with huge textures or anything like that.

Joe

Okay, this has gotten so bad, I can no longer work with Unity. The requirements state that 64mb of video should work. In fact, they claim that any video card made in this century or something to that effect. Well my Mac Mini is two years old folks! I have tried rebooting, but it did not make a difference. This is just a small project (right now) and it happens with regularity now.

I made the decision to move my project from Java and JMonkeyEngine to Unity and I’m starting to regret it. I cannot afford to get a new computer AND spend $1500 on the Unity license.

Sorry for the attitude, I just know that the reality of these things mean this bug is not going to be a high priority and that means I’m probably back to the world of Eclipse and JMonkeyEngine. :frowning:

Joe

What model of Mac Mini is it?

It’s Mac mini (Early 2009)
MB463xx/A 2.0 Intel Core 2 Duo/1 GB DDR3 SDRAM (PC3-8500)/120 GB HD/SuperDrive/GeForce 9400M/AirPort Bluetooth Built-in

But I added another 1GB SDRAM. Running 10.5.8 OSX.

I hope I can get this to work, I really do not want to go back…

Thanks!
Joe

I’ll see if we can track down that hardware and reproduce it.

Thanks. FYI. I can make the problem go away by reloading the project. I don’t have to start Unity. The problem returns within a minute or two, IF I click into the Project or Hierarchy pane. If I let the project just sit, it doesn’t seem to happen. (10 min was the longest I waited) The project has one scene, one prefab, a primitive and six materials and three textures, the largest being 1024 by 1024.

Thanks
Joe

Yet another bit of information. After completely rebuilding my project from scratch, I had three days of stable work. Then, I imported some .obj files, started tweaking things in the Project and Hierarchy panes, and the problem started up again, albeit not quite as bad. I was able to make it go away after several reloads of the project. Based on my memory of the problem from the start, it confirmed my suspicion that the problem seems to be triggered by importing or working with newly imported .obj files. Once again, I’ll state that this is not a large project at all and the geometry is fairly simple.

Seems related to Intel graphics cards. We have a few other cases of this showing up too. We’re looking into it! :slight_smile:

I’m glad, because it just took a turn for the worse. I imported 10 sounds into the project and bang, the fonts screw up the second I click on the GameObject that contains the AudioSource object that contain one of the sound clips. I can click on anything else including the parent of that object and I’m fine.

Bump!

This is still a problem. I have been working mostly on code for a while but now I need to interact with the Project pane quite a bit and it’s slow going to have to reload the project all the time.