Aller au contenu

Photo

Preventlng VO renumbering?


  • Veuillez vous connecter pour répondre
2 réponses à ce sujet

#1
Proleric

Proleric
  • Members
  • 2 361 messages
Does anyone have any advice on preventing conversations from renumbering their string ids?

Weeks ago, I made some conversations, then generated VO and FaceFX.

Today I find that all the string ids have changed, so that they no longer match the VO file names.

Whatever did this was systematic - in the String Editor, all the lines of the conversation appear as a block, at higher string id numbers than before.

AFAIK all I've done to them since then is
  • add localisation and editing comments
  • check in and out

I can't reproduce the problem with these actions. Also, I've ruled out B2B loads as a possible cause.

I can work around the problem, of course, but does anyone have any idea how to prevent it happening again?

#2
mikemike37

mikemike37
  • Members
  • 669 messages
I cant really think of a way your stringIDs would get changed if you exclude builder to builder loads. Unless.. i dont know how strings are handled if you are rolling back/forward a resource to a previous/future version. Did you do this? Or perhaps some activity involving duplicating your resources and removing the old ones? a duplicated resource will have different StringIDs from its original source.



I cant think theyd be something that would flippantly change without some good explanation... at least i hope not... :S



If you wanted a method that gives you a little greater control, though would potentially require even GREATER care... (personally i dont recommend it but offer it since it may be to your taste)



lets say your StringIDs for your module are 0 to 1,000 (for simplicity's sake). Use your first 900 strings for stuff you havent cemented and set your module to only use 0 through 900.



once a resource is entirely finished and ready to be VO'ed, change your module properties to use 900 through 1000 and make the last StringID used 0. builder to builder out the resources then bring them back in, choosing to create new IDs. Once youre done with the safe range, Check in the resources (perhaps leave a comment) and shift back to the fluid range.



Like I say, its a fiddly procedure and I dont recommend it... and heck youre probably MORE likely to cause yourself mischief... but there it is.

#3
Proleric

Proleric
  • Members
  • 2 361 messages
Thanks.

I didn't do either of the things you suggested, so I'm stumped.

Now that I'm aware of the issue,
  • I'll try to finish every detail of a conversation before generating VO (including stuff like stage directions that shouldn't change the string id).
  • If I ever have to touch the conversation again, I'll check the first string id before and after, until I discover why this happens.