Pixel Crushers Forum

Hello!

I've written multiple conversations for my game, and they all have worked great. I recently upgraded desktops, and while previous conversations still work great, every single new one I've tried to create throws this error for every single node:

Dialogue System: Lua code 'return Conversation[X].Dialog[Y].SimStatus' threw exception 'Lookup of field 'SimStatus' in the table element failed because the table element itself isn't in the table.'

Where X is every new conversation ID I make, and Y is each associated node ID as I hit them in the conversation. When looking, the (uneditable) IDs appear to exist just fine (it's not like I edited the Y IDs such that they no longer exist).

The strangest thing is that the conversation plays just fine, and you wouldn't notice anything is off, aside from being spammed with these unsightly errors.

Any ideas on what could be causing this? Appreciate any help!

Hi,

If you're not using SimStatus or the Dialogue Manager's Input Settings > [em#] Tag For Old Responses, you can turn off SimStatus by unticking the Dialogue Manager's Other Settings > Include SimStatus checkbox and settings Input Settings > [em#] Tag For Old Responses to None.

If you are using SimStatus, try ticking the Dialogue Manager's Persistent Data Settings > Initialize New Variables checkbox.

Thanks for the speedy reply! I am indeed using SimStatus, so I can use the the [em#] tag to track previously chosen dialogue options and grey them slightly. The initialize new variables checkbox is also ticked. Interestingly, most of my old conversations still work (including using the SimStatus), it's just the newly created ones that throw the error.

Hey Tony - no need to worry about this one (we can probably delete). Looks like it had something strange to do with how I have my slotted save games set up (using EasySave3 mixed with the Dialogue System Saver) - launching within the scene appears to be doing something wonky when loading in my DialogueSystem data, which appears to have resulted in the issue seen. When I come in from another scene, the dialogue launches without error.

Thanks for helping me narrow down that it was due to persistent data settings!

Alright, glad you were able to get to the bottom of it.