Pixel Crushers Forum

Thank you! I preferred not to go with the first option for one reason: KickStarter.speechManager.scrollSubtitles changes the Speech Manager asset itself, not its runtime value. I could still do that if I made sure to change the asset's value back every time the game is launched, but it feels a bit m...

The AC menu I use to display narration is different from the one I use for speech lines, and yes, I could assign the dummy Narrator NPC to it. The problem is that sadly the option for scrolling text in AC is a global setting, not a per-menu setting, so all we have are two checkboxes: "Scroll te...

Hi Tony, I was wondering if you could help me out with an issue I'm having with the AC integration. I keep all my dialogue in Dialogue System, but I run all the lines through an AC speech menu using ACSpeech(entrytag)@0.6. I wanted to write narration text in DS as well, but it doesn't seem to allow ...

My quests have these fields: https://i.imgur.com/qEvbuyS.png The idea is that the 'Group' field is only used for sorting the order of the elements (and thus a 'Group pt-br' field could be useful, but only if the developer wanted a different order in the localised version; this is sometimes useful to...

Tony Li wrote: ↑Fri Dec 22, 2023 9:42 am [*] Improved: When exporting localization spreadsheets, can now specify entry sort order.

Thank you for implementing this so quickly!

Thank you! I really appreciate it.

Thank you for the fix! Upon further investigation, I've realised that I wasn't clear re: what I am trying to achieve. Your suggestion that I use a Key Field wouldn't work because, as far as I can tell, a Key Field replaces Conversation/Entry ID as a reference when running a Localisation import/expor...

Hi Tony, I was revisiting this idea and I think I've run into a bug. Your suggestion above sounds good! I was trying to figure out how to assign LocIDs in the same way Dialogue System reorders Conversation IDs when you tell it to (using depth first or an alternate method), but before I got too far, ...

Yes, that would be perfect for conversation IDs! It would make it much easier to find a specific conversation at a glance. Unrelated to the above, but still about IDs: something a bit more complicated that I'm foreseeing about dialogue IDs (rather than conversation IDs) is the order they are display...

I use a lot of conditions like Conversation[1].Dialog[1].SimStatus ~= "WasDisplayed" . The problem is that when you have a lot of conversations and rename them, it becomes really tricky to remember what conversation the ID in the condition refers to (you need to click the conversations one...