Powerful and frightening, photoshop stuff already misleads a lot of people, like he said, "if this technology gets into the wrong hands"; there's no "if" about it.
I'm almost certain it's real time, or as close to real time as makes no difference for this purpose. The Journal manual strongly suggests this too (but as with a lot of FD info it's not explicit) and it's an offshoot of the network log which definitely writes "live" because I used to monitor it with SnakeTail during play.Is that file saved every (few) frame(s)? If its only saved on exit that wont work well.![]()
Eh, Star Citizen has fully voiced pirates and it gets old fast.
Eh, Star Citizen has fully voiced pirates and it gets old fast. I'd rather they spend the time and effort on voice acting for special NPCs like engineers or heads of powers, or others that move the story forward.
I agree that voice messages could get old/repetitive very quickly. Perhaps the low-volume, distorted voice comms you get around stations would be better. If there are lots of NPCs around, you can hear voice comms even if you can't make out exactly what they're saying. It'd give the feeling of a populated universe, without the endless repetition.
I'm gonna boil you up!
I agree that voice messages could get old/repetitive very quickly. Perhaps the low-volume, distorted voice comms you get around stations would be better. If there are lots of NPCs around, you can hear voice comms even if you can't make out exactly what they're saying. It'd give the feeling of a populated universe, without the endless repetition.
Because NPC communications are now recorded to the Journal e.g...
This is well beyond my meagre string-slicing skills but it seems like an ideal project for an enthusiastic coder to give it a shot if FD don't want to. Hell, if someone's already done it please let me know; I would love such a feature and a donation from my PayPal account stands ready...Code:{ "timestamp":"2017-01-16T19:28:23Z", "event":"ReceiveText", "From":"$npc_name_decorate:#name=Chris Armstrong;", "From_Localised":"Chris Armstrong", "Message":"$BountyHunter_HunterHostileSC_Relevant03;", "Message_Localised":"There you are! That bounty makes you today's meal ticket.", "Channel":"npc" }
...it should be possible to write a program to parse the file in real time, extract the actual dialogue and send it to a text-to-speech engine. If you wanted to be clever you could compare each NPC name with a database of gender-weighted names and allocate a male or female voice accordingly. If you wanted to be really smart you could use a hash of the NPC's name as a seed for picking from a selection of voices, thus ensuring that the "same" NPC had the same voice each time you encountered them.![]()