And with animations of objects rather than mesh deformations we’ve got a system to bake out the animation to keyframes to an xml file instead of a pointcache file.
Is there any particular benefit to using the App over the UserDefined properties?
another reason…
any dull can easy delete/change a user-defined property…
for many years i don’t use the user-defined properties. it’s some sort of garbage can where everyone wants to stick something.
Is this the correctly written way to then store information on the rootnode of a scene file?
Would it be more effective to us the genID to create the initial integer for the data_ProjectInfo?
data_ProjectInfo = 1
setappdata rootnode data_ProjectInfo (with printallelements on #("Materials","Donuts","Lights") as string)
ProjectInfo = try (execute (getappdata rootnode data_ProjectInfo)) catch(#())
Full xrefs replacement (?), sounds as very fastidious task for mxs project.
What about XRef_Material? Just hint though.
Xref Materials are w*nk… they are, as with all xref’s in max, a 1 way control solution, and are a pain to do anything with scripts. I want a two-way connection… but unfortunetly short of creating a live-database tracking all changes made in max, the only solution I can see is to save the materials outside of the scene and load and save this on file open and close.
Agreed.
That is the problem with all of the max xref tools. It is a one way street. One that does not include much control through the default max interface and much of any control through maxscript itself. So custom systems are the only way to really go for any kind of proper production pipeline.
ok, i see, we have disparate preferred bonds.
the two-way connection is not urgent for me.
the profit of xrefs is – edit single source – updates multiple scenes.
Yes but what would be nice is if you could edit the contents of you xref in one scene and have those changes propogate to the other scenes as well, without having to open the original xref file as well. I believe this is what containers were designed to do but they’re crap as well…
D
That sounds very dangerous in terms of project management.
Sometimes too much freedom make things worse.
That’s just my 2 cents.
Hence why my system requires you to publish your changes… so it keeps a log of who did what to what and there’s an automated backup system so if we need to revert to an older setup, we can do this easily.