Quick question about macros, probably the SAY macro in particular.
If I replace the "$a:$b" part in the SAY macro with just some "string" then that’ll be the output. But if I supplant it with a function that returns "string" it doesn’t seem to work. I wonder if I might be missing something obvious?
That is, something like:
#macro SAY($a,$b) function_name($a, $b)
And the function along the lines of:
function function_name($a, $b) {
// processing would go here ;-)
return "string"
}
(Alternatively and more easily I could just write some Bash/Lua/Python/whatever to generate a translation. I was just curious about doing it in-engine.)
The issue is the SAY macro is digested at compile time, so it often doesn’t know about your function_name and even if you got it to work, it’s probably not what you want due to function_name being run once at compile time and won’t ever be run again.
I would override the TR() function for that… You’d then have the benefit is adding your text to already translated text. If you only want to add it to text that is spoken, put it in _startSayline().
I just tried to record a video showing it off, but the video didn’t turn out very well. I took my laptop into the bedroom because it’s nice and quiet, but I suppose only my desktop has the power to create properly smooth 60 fps recordings.
So I just downloaded FMOD Studio Tool, and it doesn’t scale very nicely. Luckily you can force an integer scaling factor as detailed here. It’s reasonable enough at 2.
Recording the cats will be a bit more difficult, but first I suppose I should figure out if I can create a soundbank and load it.
Hm, the engine says “Can only load one bank (for now).” That’s unfortunate. Another obstacle is the apparently the version. I simply downloaded the most recent one (2.01.01).
