Laura ... can you try with newest verison of MLAB and let me know what happens ? I just did it and it worked find. If you check the LOG window ... the comands need to do the work are echo-ed into that window. The parts are staged in the temp directory for the operations.
02-29-2016, 03:21 PM (This post was last modified: 02-29-2016, 03:23 PM by ggaliens.)
Laura ... I have also seen this happen if the program "INTERSECT" somehow get's hung during a fail.
Start TASKMGR (task manager) and look to see if intersect.exe is still running. There could be 1 or two hung copies. This is for sure a mode of failure that happens.
You can also link me to your model ... but I think it is just a cube inside a cude, right ? I tried that with latest MLAB and all was well.
What operating system are you running ?
The program seems to behave as it only one instance can run at a time. So if there is a failed on sitting there blocking. That's a problem. That would not normally happen with just cube subtract cube test.
If you have SKYPE ... I'm willing to walk you through the problem with screen-sharing.
OK ... I think I broke the program "intersect.exe"
a month or two ago. I re-built it ... without even having a great reason. And I think I did not properly compile it as MONOLITHIC which would me without any DLLS ... with all included for compatibility reasons.
Sorry about that. It is something that would be easy to fix or do properly. I just have to find the time.
Sorry. Works on my machine because I have all the DLLS laying around. But didn't work on the nearby family windows 10 machine.
If you have any older manifoldlabs (2015 or older) around ... you could install it. Grab the intersect.exe file ... and drop replace it into the newe manifoldlab in the same spot. If you were desperate.