ive posted over on cgtalk about this but it’s slow over there, just wondering if anyone over here has had a similar problem as me:
Hi all,
I have setup some stuff with custom attributes but sometimes I run into small glitches. I’m finding it very tricky to work out why these things are cropping up. Let me explain.
Originally, before I knew better, I had got into a pickle where in several max scenes there were (unknown to me due to my ignorance) different definitions with the same parameters etc. I had stupidly not included a classid so each time I applied what I thought was ‘the’ attribute def, i actually added ‘a’ version of the attribute def.
Once I found out what a fool I had been I fixed this and reprocessed all necessary max files replacing and muddle of defs with a single class-id-ified consistent definition, or so I thought.
My defs are loaded in my startup script file which lives in stdplugs/stdscripts, so should get loaded before anything else. Despite this, occasionally when loading a max file the defs get blatted over by an older version. I can only assume that the max file contains an older version somehow and loading it causes the proper latest version to be replaced.
I’d like for my defined attribute set to be pervasive, and if I load an old scene with defs applied in the past for them to update.
My question to you experts is - have i just done something silly, or to get the desired behaviour will I have to delve into some callback related stuff to refresh the attribute defs script on scene load? I feel this would work but if I am missing a trick I’d rather do it a proper way.
Many thanks in advance for any help which can be granted,
cw
