Only assembly reference errors on import?

[solex86]

Hi there,

Unfortunately on my first import into a relatively clean and new project (2018.4) I cannot get past a load of assembly reference errors. Google only seems to provide answers to 2012-2015 problems that are not applicable to my situation. I've tried re-importing but it gives the same result. Hope anyone here can help me because I'm a bit confused.

Cheers

 

[Justin]

Have you tried importing into a fresh project? There may be a namespace conflict with another asset (see https://opsive.com/support/documentation/ultimate-character-controller/getting-started/importing/).

Beyond that the only time I have seen UI related errors is if you are using an alpha/beta version of Unity.

 

[solex86]

Thanks for your reply Justin!

Other assets I am using in this project are:

- Vegetation Studio Pro
- Enviro
- Lux Water
- Microsplat (with modules)
- SECTR Complete

I'll check for a namespace conflict there, is any of these known to cause issues? I can't imagine it's good practise to start editing updated scripts every time, or is there a way to catch this in a more reproducable way?

 

[Justin]

Those are more popular assets so I would have expected them to be in a namespace but I don't personally have any of those so I haven't tried it out. I would first get a fresh project working and then build up from there.

 

[solex86]

Those are more popular assets so I would have expected them to be in a namespace but I don't personally have any of those so I haven't tried it out. I would first get a fresh project working and then build up from there.

Sounds like a good idea. I'll give that a go since I can then import my terrain etc. Thank you!