Pixel Crushers Forum

I had been using markup tags normally up until recently. I tried changing the Emphasis 2 setting from the color red to white, but for some reason, it still continues to show up as red.



This is the tag being used in the dialogue node. And this is how it's showing up in game.


Am I possibly overlooking something or is there a button to apply the changes to the EM settings?

Hi,

Are you perhaps editing the wrong dialogue database, such as the auto-backup copy?

Nope don't seem to be. Strangely enough, the auto backup still has the EM marker as red. However, the scene isn't using the autobackup version either.

Is the auto-backup assigned to the Dialogue Manager?

It looks like this so I don't think so? Unless there's maybe a different place to assign it from?

That's the place. Click the Edit button, and on the Database page verify that the [em] colors are what you want.

If it's still not working, are you changing scenes? Maybe a Dialogue Manager in an earlier scene has a different database assigned to it.

Went down the list and checked that all scenes are using the same database. The Autobackup one was updated and now reflects the proper color but the text still shows up as red.

Not really sure what else to try so I'm going to see if updating the engine and dialogue system does it.

Is it possible that the "speaker" of that dialogue entry has a custom color? For example, is it associated with a GameObject that has a Dialogue Actor component that sets a subtitle color?

Ok I found the issue!

I am using multiple databases and the scene has a character that has the Extra Databases component attached. For some reason, the markup text is referring to that database's settings instead of the current one.

The weird thing is that for this particular interaction, that database isn't being used at all and is just existing within the scene. Everything else is contained within the master database. The conversation is within the masterDB, yet pulls EM settings from the other ExtraDB?

I'll probably end up merging these together to use a single one as I continue working but this was a strange issue to track down.

When you add a new database (e.g., using Extra Databases), it uses the [em] settings in the added database.

If you don't want to merge, you could just set the [em] settings the same in both databases.