It was just a matter of curiosity as to what’s causing the slowdown, but naturally you should write your tool to accomodate this issue.
I would simply write the scene to a single file.
I have used this.
To write
…
at time j setIniSetting xformFile “Transform” tmpFrame (obj.transform as string)
…
To read
…
local xformFromCache = getIniSetting cacheFileIni “Transform” tmpFrame
animate on
at time i
obj.transform = execute xformFromCache
…
I have been working for me.
Would this be a “bad” way?
why are you surprised? the result is absolutely expected. never use method #1, always use #2
@lo I have a couple of worries about the single file solution. It’s harder to delete/add/rebake objects from the file etc. If an artist needs to delete a cache file for example, he can just delete it with extra UIs etc.
@gandhics Thanks, Nice to know, even though we are still in 2013. In terms on how you save the files, yep, it’s not a good way. Read the thread from the beginning and you know why. lo explained very nice. Try saving in binary like lo suggested. I way better!
@denisT I wasn’t surprised at all. I always use the second method. With this example, I was just trying to prove my point to lo.
yep, that’s exactly what I’m doing right now.
It’s not wrong, it’s just less accurate and slower.