the Sim Settlements forums!
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
- Messages
- 420
Yeah i noticed that. Then again, it is only a small issue
They're just following in Bethesda's footsteps.
- Messages
- 5,182
Now having done a handful of quests, I can tell you exactly why these issues happen (probably by Bethesda for the same reasons). I probably won't fix them, just because it's a dark rabbit hole I don't want to go down.
- We start by having a writer flesh out a quest idea, and get the writing down.
- Next an editor cleans it up and makes sure it all makes sense, it's not too lore breaking, and is largely grammatically correct and spell checked.
- Then it's given to our director who will cast a VA.
- The VA will often submit multiple takes of each line so we have some different readings to choose from.
- Then it's sent to our sound team for processing to improve the audio quality and cutting out the mistakes.
- Next it goes back to our directing team who pick the best takes and send it back to the implementation team (in this case me).
- At implementation time, we simply copy paste the lines that were turned in from the editor into the CK and set up all of the necessary triggers. Then we grab all of the final audio lines, and pray that they were labeled correctly and that the audio file order matches the written order. We do a bunch of processing to get the files super tiny, generate facial movements, and other things to ensure it works. (the point being, this step is very time consuming)
- Then we send it for testing and fix any bugs in the scripting, or mismatched audio files.
So a lot of hands have to touch it, and there are chances for the lines to be changed at various points. For example, the VA might improv a bit, or misread a word, the director might suggest the VA change a word after hearing it aloud and realizing the script sounds a bit unnatural, the sound team might have cut what appeared to be a mistake, but was actually a word in the script.
So rather than trying to go back and actually transcribe what was said, we just hope that the lines turned in by our editor are pretty darn close to what was actually used.
- We start by having a writer flesh out a quest idea, and get the writing down.
- Next an editor cleans it up and makes sure it all makes sense, it's not too lore breaking, and is largely grammatically correct and spell checked.
- Then it's given to our director who will cast a VA.
- The VA will often submit multiple takes of each line so we have some different readings to choose from.
- Then it's sent to our sound team for processing to improve the audio quality and cutting out the mistakes.
- Next it goes back to our directing team who pick the best takes and send it back to the implementation team (in this case me).
- At implementation time, we simply copy paste the lines that were turned in from the editor into the CK and set up all of the necessary triggers. Then we grab all of the final audio lines, and pray that they were labeled correctly and that the audio file order matches the written order. We do a bunch of processing to get the files super tiny, generate facial movements, and other things to ensure it works. (the point being, this step is very time consuming)
- Then we send it for testing and fix any bugs in the scripting, or mismatched audio files.
So a lot of hands have to touch it, and there are chances for the lines to be changed at various points. For example, the VA might improv a bit, or misread a word, the director might suggest the VA change a word after hearing it aloud and realizing the script sounds a bit unnatural, the sound team might have cut what appeared to be a mistake, but was actually a word in the script.
So rather than trying to go back and actually transcribe what was said, we just hope that the lines turned in by our editor are pretty darn close to what was actually used.