tomlowe Posted November 9, 2018 Share Posted November 9, 2018 Why doesn't ProBoolean work anymore!! Is it broken or am I broken? Link to comment Share on other sites More sharing options...
Jose Negrete Posted November 15, 2018 Share Posted November 15, 2018 Hey Tom, not sure what version you're on or what you're trying to boolean but I do sometimes have to do a boolean operation in version 2016 (Currently using version 2019.1.1) Link to comment Share on other sites More sharing options...
Jesper Pedersen Posted November 24, 2018 Share Posted November 24, 2018 Hi Tom, We have always found booleans/pro-booleand twitchy and would save before we begin any boolean work in max (but Autodesk are only small so how can we expect them to catch all the bugs, right? ..hmm) I'd agree with Jose, the version of Max you are using could be the issue. We're still on 2016, despite having 3ds max on subscription. Jose, how are you finding 2019 in term of glitches/ general stability? I've been looking for a post on this but it's promising that there doesn't seem to be a flood of posts complaining about the release. Regards Jesper Pedersen http://www.pedersenfocus.ie Link to comment Share on other sites More sharing options...
tomlowe Posted November 24, 2018 Author Share Posted November 24, 2018 Thanks Jose and Jesper, seems autodesk fix one thing and break another each release. I recently changed from 2016 which I found incredibly glitchy to 2019 and it has been a lot more stable and haven’t experienced any massive problems. Link to comment Share on other sites More sharing options...
Jesper Pedersen Posted November 24, 2018 Share Posted November 24, 2018 Hi Tom, That seems to be what I'm hearing generally. Yes looking forward to getting set up with 2019 soon (but form past experience we don't dare to switch in the middle of projects/upcoming deadlines) .. in a few weeks time (January) we'll go for it. Thanks for the advice. Regards Jesper Pedersen http://www.pedersenfocus.ie Link to comment Share on other sites More sharing options...
Jon Berntsen Posted November 24, 2018 Share Posted November 24, 2018 They also changed the good old boolean from 16 to 18 (probably in 17, but we skip odds). Luckily they kept the old one accessible in maxscript, because the new one didn't work for our operations at all. It started giving results back like proboolean, which returns missing or buggy polys, if anything at all. We have an important intern tool written in maxscript which relies on boolean, because of that proboolean bug. There's a trick, however, that you could try. There seem to be something going on in the object type translation which sometimes makes it work by clicking proboolean, boolean, shapemerge, boolean, proboolean, before trying an operation again. Not sure why, but that sometimes makes the probool work. Same with boolean. Such a shame they changed boolean into the same shit as proboolean is. Anyway too unstable. It should be able to cut any simple geometry. Link to comment Share on other sites More sharing options...
Jose Negrete Posted November 28, 2018 Share Posted November 28, 2018 Jesper, I haven't had much to complain about with 2019 - We did skip 2017 and 2018 though and I'm curious if we'll be allowed continued access to 2016 next year. What I can think of at the moment is the same issue with the booleans that Tom brought up. Additionally, I seem to have a glitch where the spinner jumps if I click and drag it down or up beyond the edge of the screen. I forget if this happened a lot in 2016 or not... Another thing I ran into was black tiles from imported Infraworks .fbx files. Autodesk provided a script to fix these tiles and if I recall correctly, the bitmaps came in fine but their tiling was jumbled on import for some reason. Link to comment Share on other sites More sharing options...
tomlowe Posted November 28, 2018 Author Share Posted November 28, 2018 I have the same issue with the spinner jumping when dragged beyond the edge of the screen. I read somewhere that it could be an issue caused by a Windows 10 update that happened a while ago. Link to comment Share on other sites More sharing options...
Jason L Posted December 3, 2018 Share Posted December 3, 2018 They also changed the good old boolean from 16 to 18 (probably in 17, but we skip odds). Luckily they kept the old one accessible in maxscript, because the new one didn't work for our operations at all. It started giving results back like proboolean, which returns missing or buggy polys, if anything at all. We have an important intern tool written in maxscript which relies on boolean, because of that proboolean bug. There's a trick, however, that you could try. There seem to be something going on in the object type translation which sometimes makes it work by clicking proboolean, boolean, shapemerge, boolean, proboolean, before trying an operation again. Not sure why, but that sometimes makes the probool work. Same with boolean. Such a shame they changed boolean into the same shit as proboolean is. Anyway too unstable. It should be able to cut any simple geometry. I was just going to come in and post a similar topic and saw this thread. I just did the "upgrade" to Max 2019, and I find the boolean operations absolutely horrible. My workflow is completely disrupted as I have to export my scene to Max 2016 to do any sort of boolean operations. I am finding that more often than not, using Max 2019 my objects just disappear when performing a boolean operation using the default boolean tool, and when using the Pro Boolean tool my Max simply crashes or creates a corrupted object. Using Max 2016, I am able to perform these same operations using the default boolean's without a hitch. Is your script that your firm developed something you would be willing to share or sell? I am relieved to hear that the old code is still hidden in there. There is much I like about Max 2019, but the broken booleans is ruining the experience for me. Link to comment Share on other sites More sharing options...
Jose Negrete Posted January 28, 2019 Share Posted January 28, 2019 Jon, I want to ask about your script as well. Is it something you're willing to share or sell? JLVisuals, For what it's worth, I use Chris Grant's copy/paste script and am able get a post-boolean object back to 2019 a bit faster. http://www.scriptspot.com/3ds-max/scripts/copy-and-paste-objects Link to comment Share on other sites More sharing options...
Jon Berntsen Posted June 1 Share Posted June 1 Sorry to be such a slow responder, like five years later. I totally forgot about it. This boolean case is still being an issue for 3ds max. For this mentioned script in particular, it's a cladding script which makes you able to put different types of cladding on polygons with a one click solution. So say you have a wall, you just detach the faces where you want the cladding, and then it applies it. It also hides the base geometry, and it also works on multiple selected walls. In theory you could select 100 different polygons and have a cladding applied to all of them while you go fetch a coffee. You could tailor it to have other geometries than cladding as well. I can rewrite the script and maybe make a plugin out of it, but I'm not sure if the effort is worth it or if it's a market for it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now