Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Synthanel's avatar
Synthanel
Protege
12 years ago

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, as soon as I downloaded one of their demo packs I was getting 88 compiler errors without changing anything to my prodject.

I tried to get rid of it the add ons and got frustrated and uninstalled everything and reinstalled and the compiler errors were there. I then went and unistalled and tried to delete every single unity file I could using search and after reinstall still getting compiler errors.

I am sure I will figure out what it going on eventually unfortunately my level design knowledge was coming back faster from memory than what limited coding knowledge I have.

Thanks very much for your time taking a look.

4 Replies

Replies have been turned off for this discussion
  • Could you share a few examples of the compiler errors? Is it the same one or two errors repeatedly? Did any of the prefabs you used have a large number of gameobjects? If you create a new project, you should have a clean slate to start with (hopefully saving you another reinstall). Maybe try starting the new project with the bare minimum assets you need and pick and choose what you add from there.
  • I am stuck at work at the moment but I will try to do just that. I was thinking that a new project should do that but they were initially still showing up, but I could have done something wrong. I did grab a fair amount of prefabs and tried to delete them.

    I will definitely give it a go when I get off from work. Thanks very much for the information.
  • drash's avatar
    drash
    Heroic 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).
  • Thank you very much for all the info. After scratching my head for a bit I started deleting assets till I was down the the minimum, and the compiler errors were there with a new project. So I deleted all my assets and re imported them and they seem to be working now.

    Thanks a lot, your input was greatly appreciated. =)