Sweet ( the message I have entered is too short – but not anymore )

total guesswork here – but wouldn’t standard pblock2 access apply? (not to any variables stored, but the parameters?)

uhh… err… no – no idea you could try using the node event system… painting triggers this node event sequence on in a while: — @ N = timestamp, […

your question was answered? Unless you want somebody to provide the complete code for you, of course. write a Max File archiver. You could use max…

you’ll also have to write your own max file archiver, unless I missed a max file archive command outside of “max file archive” that lets you specify t…

they’re probably just .NET treeviews and listviews – the MaxScript docs contain sample code on how to create them, set them up, etc.

I’d imagine all of the answers are available from the developers, but it should just be a simple check for the version and toggling names based on tha…

persistent globals are far less ‘ick’ than having to track another file (2010’s asset tracking enhancements might make that slightly more feasible – b…

yep, something like that

shouldn’t be an issue to make it per-maxfile if it loops over e.g. .controls, get the control type, then gets/sets its value accordingly. only ‘probl…

I think one of the problems with a persistent global was that if you started to load a file, but then didn’t actually load it (or merge it), then your…

why not store them in a custom attribute block (set on the sceneroot object (has issues in older max versions), or a track view node, or anywhere that…

hooray for backfacing (or lack thereof)!

aw :\ fn getFacesByAngle obj faceIndex angleThreshold:10.0 ignoreBackfacing:true = ( local numFaces = obj.numFaces local faceNormals = for i = 1 to…

of course – only with minimal testing, though… again, parameters weren’t really meant to be in a floating dialog myAttribs = attributes test ( rol…