Yeah I don’t think anyone here is trying to pretend MAX is a bugfree program
But with that said, the crashes and weirdness I experience doesn’t seem to be the same “kind” as the ones InQ has. I’ve used QuickSlice extensivly, never had any grief with it. And I certainly know I’ve detached polygons (to element and not), and I don’t recall a single issue with it somehow just not working.
The same kind of response with the list of bugs you’ve written InQ, though there are some I haven’t tested much, like normal mapping and whatnot. But, for instance, I don’t recall a single time where I’ve had to press the Edit button twice… and so on and so forth. They may indeed be bugs, something Discreet can go “whhoops, sorry, a patch is enroute” to and everyone is happy again. But I don’t recognize most of the errors described… meaning I can’t help but think that it’s perhaps not as much the software, as it is some other (local) factor.
I do actually recall MAX being very slow some times when started up, but that was like back on NT4 or Win98, with some crappy-ass drivers.
Anyway, I also have my own little list of MAX bugs I belive I’ve found, but they’re nothing like the ones presented here. If you seriously can’t Detach a polygon without a 100% successful trackrecord, then obviously something is wrong. But I still say it’s not a case of “what a stupid MAX bug!, that’s it!, stupid Discreet; I’m moving to XSI”. InQ, I’m sorry to hear you’re having these problems. I can see that from the sounds of it all the experience you have in this points to the software being flawed, so I can see where you’re coming from. It’s opposite for me, my experience tells me that it sounds like a computer-specific problem, or some other local variable that’s messing with MAX…
Bah, damn computers and the software we’re running. So many hours wasted hunting down peculiarities.
I think you should call Discreet, for what it’s worth. It sounds like something serious is up, maybe they can provide some sort of answer.