Pixel Crushers Forum

...

...

Think I found a weird issue with the conversation trigger.

I had originally duplicated my database file and scene file - I'm in the process of making all names and such generic.

Say I have Scene1 + Database 1 and Scene2 + Database2 where the later are direct replicas of the former. Duplicated through the menu: Edit -> Duplicate.

If I open scene 2, reconnect all the components to the Database2 file and then save and open Scene1 everything is the same except all of the conversation triggers are now connected to Database2. If I connect them to Database1, press save and open Scene2 all of the conversation triggers are assigned to Database1.

I should add that none of the objects in my scene are prefabs.

I've now tried this on two systems and I get the same behaviour.

Nathan

Hi Nathan,

Thanks for reporting that! I'll make sure it's fixed in 2.0. The Conversation Trigger inspector caches a reference to the database to populate the dropdown menu of conversation titles. The reference isn't used at runtime. Version 2.0 will refresh the cached reference to the database so it points to the right one.

Ok, that makes complete sense. Thanks for that.