koobas.hobune.stream
Pretty In Pink... Not!
When I install Unity 4.5 / 4.6 on high-end Win7 Nvidia-670m laptops and load a demo project (after conversion), some materials fail to import and as many as 10-30% are colored pink. What's really baffling is if I install Unity on low-end laptops running XP-SP3 everything works fine!!! Logically, you'd expect the reverse.
I've looked at the imported materials but I can't see any clues as to why the material build / import / compilation is failing. I've ruled out machine related issues as I've confirmed the prob on a 2nd production laptop, and all boxes work fine for UDK / UE4 projects. Any advice appreciated, cheers!
Ok, but why would this only occur on a high-end machine? Both low-end and high-end have the latest graphics drivers by the way. I'm inclined to think this has more to do with Unity's project converter than anything else... That's as far as I can reason this...
Usually, gameobjects in the scene turn pink when there is a material missing from it. This explains why it would be pink, but not why some of them are missing. Just thought I would say that.
It's a very strange issue. I've had it where duplicate, missing, or unsupported shaders (scripts) caused the problem. The frustrating part is that there's no way to really tell where the problem is co$$anonymous$$g from, and not much documentation on the issue itself. Check the log for warnings, and try deleting shaders you see there (if any). It worked for me many times. Remember to back-up!
This could be for a plethora of reasons, so, like tanishimi said, we need to see exact error details. :)
You said it occurs on high-end Win7 Nvidia 670 laptops. $$anonymous$$aybe those laptops are Intel machines, and they happen to be running Unity with the CPU's integrated HD Graphics ins$$anonymous$$d of the discrete Nvidia card? If so, there could be shaders that aren't supported by that GPU.
Unity's Project Conversion is not seamless and can take a bit of work to fix new incompatibilities. Is there errors appearing in your console?
Try adding the "-force-d3d9" command line argument (or "-force-d3d11", try both).
I've had graphics problems with the editor in the past despite a high end graphics card, though I don't think its ever been a failure to import textures. Are they really large textures or in an unusual format or something?
