error on update

[NotVeryProfessional]

Updated Dialogue System today, after many updates with no issue, this time I get:

The type or namespace name 'SequencerCommand' could not be found (are you missing a using directive or an assembly reference?)

which is weird because I do see the SequencerCommand.cs file right there and it seems to declare properly and I don't get an error on it, so no idea why it doesn't find it.

[NotVeryProfessional]

I apparently fixed this issue by completely deleting all PixelCrushers folders in my project and re-importing it all.

So FWIW, somewhere something doesn't get updated properly, maybe an old instance/script is left behind or something. I couldn't figure out what exactly is causing the problem, but a delete and re-import fixed it.

(I don't know how many releases I was behind, I think the last time I updated was a couple months ago, but not entirely sure.)

[Tony Li]

Hi,

Maybe there was an assembly definition file issue. In any case, I'm glad you got it working.

[catherineomega]

I'm actually having a lot of trouble with this as well--including in a fresh 2022.3 project with only Dialogue System and Quest Machine. Is it possible the integration is what's causing it?

[Tony Li]

Hi,

What errors do you see in the Console window?

[catherineomega]

Hi Tony. I'm embarrassed to tell you that it's now working.

I assume the installer didn't copy something over somehow, since it took a couple tries of deleting and importing. Anyway, thanks for the prompt support!

[Tony Li]

Glad it's working now!

[NotVeryProfessional]

It's definitely not you or your code. I've noticed that with the last few updates, Unity became a lot more brittle with 3rd party packages and I've had a couple errors with other packages as well where I never had errors before.

In my case, it was likely by having moved them to a subfolder so the 50 or so assets don't clutter up my main directory. That wasn't an issue until now, but apparently Unity is now more strict and doesn't like if paths changed.