what do I use to find which objects in the scene do not have any material applied to them. For instance I draw some boxes, they come up in random colors. These do not have any texture/material applied to them, what is the ask function to find these particular objects?
I believe that:
for oNode in objects do (
if oNode.material == undefined then (
format "% is naked!
" oNode.name
)
)
should work…
Shane
I think it’s an option to turn of the memory output in the listener after you allocate some variables etc… Turning it off an rebooting Max shows that the memory output disappears
EDIT: Damn… not sure , can’t reproduce now …
Why this got an extra UI while other new things are’nt reflected in the UI is beyond my understanding though…
Found it :
it’s just an exposure of the maxscript command “options.showGCStatus”
When set to true , the message “MXS GC” will be displayed in the status bar during MAXScript Garbage Collection.
When set to false , no message will be displayed.
The setting is stored in the 3dsmax.ini file in the [MAXScript] section.
Available in 3ds Max 8 and higher.
So Vincent is right…
I’d love to know what the Max team’s prioritising system is, for new features, changes and bug fixes.
Couldn’t agree more. I think they hit rock bottom with 2012 with the “Stylized” viewports (Graphite, Ink and stuff)…
thanks…
that means the user can an option to turn of that annoying output about “MXS allocates additional memory blah-blah-blah” but to stay with no idea why the system suddenly got glitching.
useful.
i think they hit the height with caddies… it’s worst addition for the last years.
Both of these seem like features that were added because they sounded cool to a marketing executive, not because any user said “If only these dialog boxes were more rounded”.
they sounded cool to a marketing executive
or they saw it in another app a decided that they must have it even though they’ve never created so much as a box in max.
caddies is a sample of how developers are far from the real user. not they look just unprofessional but they are functionally designed as if designer never worked in max and never intended doing it.
It’s a shame, because they add some features which have the potential to be great, but get left by the wayside – ones like containers. They could have been great, but due to their bugs and their… erratic behaviour, I couldn’t recommend ever using them in production. Unfortunately, it’s now gotten to the point where I actually don’t check to see if they’ve fixed them, because I have other things to do and I just put them on a shelf with Boolean, Meshsmooth and using Groups on Backburner via MxS – the “stay away” shelf.