Pixel Crushers Forum

Hi Tony,

I managed to identify the assets that were giving thousands of errors after switching to Force Text, and they were all inside a big folder of materials and textures I really didn't use, so I've deleted it and not a single error was shown then.

I also noticed a backup scene I had, that it was giving more errors on its own, so I also removed it.

Well, the thing is that I upgraded with no evident issues this time, but when I went to load a savegame, I got this...:



And for some reason, the Main Title screen remains on top of everything.

I thought this could be some kind of problem with older saves not being compatible anymore with DS2 (not a big deal), so I started a new game (no problem there), saved the game, quit to the Main Menu and loaded that savegame... and got the same result as before.

Then, if I load the game from inside the game (no exiting to Main Title), there's no Main Title screen on top, so I can control the character, but the error still shows up in the Debug log.

Also, when I started an Adventure Creator action (taking a shower) that, at some point, initiates a DS conversation, I get a different kind of empty reference error...:



...and the ActionList seems to stop executing.

So, I suspected some problem with the save/load system integration with AC, so I checked both Persistent Data Settings and the Adventure Creator Bridge config...:




...and that the Remember Dialogue System script config was the same as before the upgrade:



All seems good to my understanding, but it looks like AC is having a tough time working with DS.

Is there a minimum AC version requirement for DS 2.1.1 integration? I have AC 1.60.7, which is not the latest, but I always prefer to be conservative around plugin updates.

Also, I found a weirdness related to the previous shortcuts garbled text, but this time here...:



...in the Default Sequence field. I removed that just in case, and it doesn't seem to be related to the main issue here, but sure it is worrying that after doing everything supposedly well, that is still happening.

Anyway, if I can't get this to work I'll need to stay in DS 1.x forever. Or at least while I continue developing this game, which will probably take 3-4 years more.

At this point, I don't mind losing savegame backwards compatibility. Any ideas?

I'm more than willing to upload the whole project if you want to take a look, btw.

Thank you!

Abelius wrote: ↑Wed Jan 30, 2019 7:03 pmIs there a minimum AC version requirement for DS 2.1.1 integration? I have AC 1.60.7, which is not the latest, but I always prefer to be conservative around plugin updates.

I can't imagine why. Sorry about the headaches updating your project. Many dozens of projects have updated to 2.x without issues, and those are just the ones I'm aware of. So this is a puzzler. Rather than speculate, I'll download the project (thanks for sending it) and let you know what I find.

I think the minimum supported AC version is something like 1.55, or the last time AC introduced an API change, which hasn't been for a while. So you're good there.

Darnit, expect a version 2.1.1.1 to arrive on the Asset Store very soon. There's a small bug on a single line of code in version 2.1.1 that affects reloading SimStatus in certain circumstances. This patch should fix it:

DialogueSystem_2_1_1_patch20190130.unitypackage

It came about because I recently spent a lot of time optimizing saving & load SimStatus. On large dialogue databases, it's more than 100x faster now. FWIW, the bug would have also been present in the upcoming version 1.8.9, but it's now fixed there, too.

Pheeww... that patch made the trick! Thank you for your support. You're unhumanly responsive, as always.

And I'm happy to help to smash annoying bugs. It seems that uploading the project was the most sensible approach, although I'd feel bad if the issue would have ended being related to something outside DS. You already have a lot on your plate.

So, thank you so much!

Glad to help! I'm just happy that it's working now.

Now that you're on 2.x, I recommend skimming through the 2.x release notes in case there are any changes that would affect your project. A quick search for the word "changed" turns up these that might possibly be relevant:

• Group nodes now run their OnExecute events.
• To show alert messages without auto-hide, specify negative duration value.