I can’t comment on the books since I’ve never read either one, although I’m glad to see there’s a new one out. But I would highly recommend the MaxSc…

Yeah, I totally agree. I mainly just think that the system variables, like “objects”, “lights”, and “geometry” are cool. Plus, for the specific purp…

Just thought I’d chime in here with a alternate way of getting the scene extents. Assuming that you only need the extents of the mesh objects in the …

Can you give me some more information on the “scene diameter”? When does MR calculate it, where it the number found normally, what exactly is it calc…

I haven’t tried this myself, but it might help: Look in the Tutorials section.

If you’re using Max 8, you can make use of the new Limit Controller. Otherwise, I’ve never found a good way to do this. But if it’s mainly for use o…

Pretty slick. I should have paid more attention in math class.

Yep, that’s what I’ve had to do in this type of situation also. Here’s the script I use, nothing amazing but it gets the job done: fn zeroPad num = …

It’s called hiddenDosCommand. I couldn’t find it on the webboard, so I’m attaching it here.

I haven’t touched this in a while, but this is the script I use… macroScript PMT_removeEdgesAndVerts category:”HaywoodTools” ( fn getVertsUsingEd…

Yep, I did this to. But they’ve made it even easier for Max 8, just use the command, <Edit_Poly>.remveEdgeCtrlKey, to take advantage of the ne…

In Max, Z is up and down, not Y. All you’re Z values are zero. But it’s best to set the position of an object directly rather than using the Move co…

Real quick, I can help you with 1 and 4. box wirecolor:green macros.run “macroCategory” “macroName”

Ah, I see. Well, it’s going to take a smarter man than I to help you with that one.

I could be way off, but since you always know where the viewport grid is, do you even need to test for it? What exactly are you trying to do?