Forum Discussion
Synthanel
12 years agoProtege
Compiler errors galore. *Pulls out hair.*
So I started out and I am fairly new to unity but found it fairly straightforward and started building with its built in assets. After a while I decided to download some prefabs from their asset store...
drash
12 years agoHeroic Explorer
One gotcha I've come across is that you may have a bunch of errors in the console, but sometimes they are all a side effect of the first error. So, when you have a bunch of errors, focus on the first one in the list first.
Secondly, the compiler errors usually tell you everything you need to know to fix it. If not in the words themselves, but by double clicking on the error in the console and having it open up the exact line of code where something failed. From there, you would need to draw on whatever experience you have to figure it out.
And finally, as others here mentioned, if you have a lot of third party stuff you want to drop in, you probably should build up your scene bit by bit to make sure that everything is working along the way, or you may find yourself overwhelmed with figuring out the more subtle errors.
If you are getting errors even before you've placed anything into your scene hierarchy, then those errors are probably the result of editor scripts (scripts that are intended only for use within the Unity Editor, or scripts that are set up to work in both editing and game modes). A fair amount of third party assets out there worked at one point but simply haven't been updated to keep up with newer Unity versions so beware of that too.
And finally, if you're unable to play because there are compiler errors but you're unable to see any errors in the console, make sure that you haven't filtered out errors (using the little color-coded boxes in the upper right of console window).
Secondly, the compiler errors usually tell you everything you need to know to fix it. If not in the words themselves, but by double clicking on the error in the console and having it open up the exact line of code where something failed. From there, you would need to draw on whatever experience you have to figure it out.
And finally, as others here mentioned, if you have a lot of third party stuff you want to drop in, you probably should build up your scene bit by bit to make sure that everything is working along the way, or you may find yourself overwhelmed with figuring out the more subtle errors.
If you are getting errors even before you've placed anything into your scene hierarchy, then those errors are probably the result of editor scripts (scripts that are intended only for use within the Unity Editor, or scripts that are set up to work in both editing and game modes). A fair amount of third party assets out there worked at one point but simply haven't been updated to keep up with newer Unity versions so beware of that too.
And finally, if you're unable to play because there are compiler errors but you're unable to see any errors in the console, make sure that you haven't filtered out errors (using the little color-coded boxes in the upper right of console window).
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 9 months ago