*A:M User* Roger Posted July 8, 2011 *A:M User* Share Posted July 8, 2011 Ok, so I made a change to a model and it propagated backwards through all my previous versions of the project file. I have backups, but am afraid that if I open them on the machine w/ the affected files they will be affected also. Does it work that way, or will I be safe if I open them from my back up jump drives? From now on I am working with .cho files, seems like it will be much less dangerous. Quote Link to comment Share on other sites More sharing options...
*A:M User* Roger Posted July 8, 2011 Author *A:M User* Share Posted July 8, 2011 Well I have useable backups. Going to need to redo a little work but at least I don't have to start over completely. Quote Link to comment Share on other sites More sharing options...
John Bigboote Posted July 8, 2011 Share Posted July 8, 2011 Seems like you solved your prob... I have always wished that you could 'nest' choreographies...like you do in After Effects. So, you would make a new chor... setup a whole bunch of stuff... make a 2nd chor... delete the camera, ground and lights- and drag chor 1 into chor 2 having it simply showing in chor2 as an element named chor1. I think it works, but you have to save it as a .cho file... and when you import it it just dumps all the stuff from chor1 into chor2... so you see each and every item. Kinda defeats the purpose. Nesting comps in AE has long been seen as one of it's strongest features. Quote Link to comment Share on other sites More sharing options...
Bruce Del Porte Posted July 8, 2011 Share Posted July 8, 2011 It sounds like you pointed to a separate model file rather than embedding the model in the project. When you do this, yes when you save the project, the model file is also updated by overwriting the .mdl file. Previous project versions will then point to this updated model file. The workflow fix is to embed model files in the project. Models in previous project files will not be updated. Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted July 9, 2011 Hash Fellow Share Posted July 9, 2011 I presume this means you saved the changes over the old model name? Don't do that. Increment your model names when you make changes. From now on I am working with .cho files, seems like it will be much less dangerous. that's a good reason to work in chors. They will load all the assets they need, even if they are not in a PRJ. Quote Link to comment Share on other sites More sharing options...
*A:M User* Roger Posted July 9, 2011 Author *A:M User* Share Posted July 9, 2011 No, I incremented the model name so I still have the original model ( that needed some fixing). I need to redo the leg rig on the penguin (since that was one of the things that got wiped out) but now that I know what I'm doing with that, it shouldn't be as bad. Quote Link to comment Share on other sites More sharing options...
mouseman Posted July 9, 2011 Share Posted July 9, 2011 I presume this means you saved the changes over the old model name? Don't do that. Increment your model names when you make changes. ... or frequently commit to Subversion. Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted July 9, 2011 Hash Fellow Share Posted July 9, 2011 No, I incremented the model name so I still have the original model ( that needed some fixing). I need to redo the leg rig on the penguin (since that was one of the things that got wiped out) but now that I know what I'm doing with that, it shouldn't be as bad. If the new model had a new model name, old PRJ and old CHORs that referenced an old model name won't be loading the new model name. So something else happened. Quote Link to comment Share on other sites More sharing options...
mouseman Posted July 9, 2011 Share Posted July 9, 2011 If the new model had a new model name, old PRJ and old CHORs that referenced an old model name won't be loading the new model name. So something else happened. Maybe he was making the old models have the incrementing numbers? Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted July 9, 2011 Hash Fellow Share Posted July 9, 2011 An incremented number is a new name. A change of even one character is a new name. Quote Link to comment Share on other sites More sharing options...
*A:M User* Roger Posted July 10, 2011 Author *A:M User* Share Posted July 10, 2011 Here is what I have been doing: project files get saved with different names whenever substantial changes have been made. From project file to project file, however, the model names of the models inside the .prj files do NOT change, they stay the same. That might be why a change could affect a model across multiple projects (that all contain the same model). That's the only thing I can think of. I have not been conciously embedding the models in the project files, unless that option is turned on by default. If having non-embedded models would account for this behavior, that might be what is going on. Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted July 10, 2011 Hash Fellow Share Posted July 10, 2011 Here is what I have been doing: project files get saved with different names whenever substantial changes have been made. From project file to project file, however, the model names of the models inside the .prj files do NOT change, they stay the same. That might be why a change could affect a model across multiple projects (that all contain the same model). If the models have been "saved" (you intentionally saved them to a spot on your hard drive), yes. That's the only thing I can think of. I have not been conciously embedding the models in the project files, unless that option is turned on by default. If having non-embedded models would account for this behavior, that might be what is going on. Yes, that is what is going on. You can tell with 100% certainty if a model is embedded by looking at its icon. If it has the little floppy icon on it, it is saved separately and not embedded. Quote Link to comment Share on other sites More sharing options...
NancyGormezano Posted July 10, 2011 Share Posted July 10, 2011 If it has the little floppy icon on it, it is saved separately and not embedded. Is this new? I normally don't embed models but I had never noticed this "floppy thang" until now! I like! I like! If I wasn't sure, I had always inspected the file info property of the model, material, cho, etc to see if it had a filename/path or if it said it was embedded. Me guste mucho! Quote Link to comment Share on other sites More sharing options...
Hash Fellow robcat2075 Posted July 11, 2011 Hash Fellow Share Posted July 11, 2011 If it has the little floppy icon on it, it is saved separately and not embedded. Is this new? It's 20th Century. I think it came in during the Clinton administration. I normally don't embed models but I had never noticed this "floppy thang" until now! I like! I like! If I wasn't sure, I had always inspected the file info property of the model, material, cho, etc to see if it had a filename/path or if it said it was embedded. Me guste mucho! Roger, now you know you don't have to feel bad about not noticing this. Nancy's been doing CG since before John Lasseter knew what pixel was, and she hadn't noticed this feature either. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.