Answer by jashan
This is most likely due to the much more restrictive handling of Mono in Unity 3. There's now different profiles and not all of the profiles support all the Mono features. In particular, Web players...
View ArticleAnswer by AngryAnt
Path 1.0 is not Unity 3 compatible. I'm currently working on a 1.1 release which will address this and many other things.Some background: Unity 2.x allowed assemblies to link to UnityEditor and still...
View ArticleAnswer by lukos1986
Is anyone found solution for that. I'm experiencing same problem with UniLOD on Unity 3.1
View ArticleAnswer by alexsan75
You can try to change API Compatibility Level: to .Net 2.0. choose Edit->Project Settings->Player, then follow this link...
View ArticleAnswer by jashan
This is most likely due to the much more restrictive handling of Mono in Unity 3. There's now different profiles and not all of the profiles support all the Mono features. In particular, Web players...
View ArticleAnswer by AngryAnt
Path 1.0 is not Unity 3 compatible. I'm currently working on a 1.1 release which will address this and many other things.Some background: Unity 2.x allowed assemblies to link to UnityEditor and still...
View ArticleAnswer by lukos1986
Is anyone found solution for that. I'm experiencing same problem with UniLOD on Unity 3.1
View ArticleAnswer by alexsan75
You can try to change API Compatibility Level: to .Net 2.0. choose Edit->Project Settings->Player, then follow this link...
View Article
