|
I'm getting loads of error messages that say
I dug into the Editor logs and the precise message is
They stop if i delete the terrain, but persist even with a new terrain in a new scene. I'm sure I could work around this, but I'm curious now and want to track down why this is breaking. I have updated the project from pre-Unity3 to the current version, but wasn't getting this error before. Alternatively, does anyone have a way to hone in on materials/prefabs/assets that are causing problems within a project without moving or disrupting the whole project? Can you selectively disable them or something? Thanks for your help dylan
(comments are locked)
|
|
Rebooting my computer usually fixes this error, not sure what causes it but this looks to be a Unity bug (of course this is assuming that you do infact have the _MainTex property defined in your shader as I did). If your computer crashed, you might want to manually delete the Temp folder from your project to make sure nothing is surviving the restart, maybe forcibly reimporting all assets in your project will be enough to fix this too, I have not tried though. In some cases when you switch between different applications that access / write / read an asset it can occur that Unity can't access an asset while reimporting since the file got locked. This usually leads to an "empty" file in Unity. Usually reimporting of the file should fix it.
Dec 16 '12 at 10:20 PM
Bunny83
(comments are locked)
|
|
check the appropriate include in shader file for example include "UnityCG.cginc"include "AngryInclude.cginc"etc
(comments are locked)
|
|
Its all dependent on the shader you are using. I started with OpenGL ES1.1, then changed to OpenGL2.0. After i switched i noticed i was still getting the error. I had to change the graphics emulation properties under the edit menu to OpenGL ES2.0 and now the problem is gone. Im not sure if its a complete fix or not, but i dont get the error anymore. Hope this helps.
(comments are locked)
|
|
After a crash in Unity I got exactly the same message. Anyone found a fix for this?
(comments are locked)
|
|
It's probably named something else in your shader.. or your shader doesn't have a _MainTex Check your shader for a line like this: restarting unity worked for me. http://answers.unity3d.com/questions/126458/material-doesnt-have-a-texture-property-.html
Oct 20 '12 at 06:56 AM
Jozxyqk
(comments are locked)
|

please add your sample script which case this error
are you building for Android or iOS?