topic Re: [MaxScript] Test if ProBoolean.CreateBooleanObject() fails in 3ds Max Programming Forum

[MaxScript] Test if ProBoolean.CreateBooleanObject() fails

JasonCampbell — Thu, 12 May 2016 05:30:51 GMT

Hi Guys,

Is there a way to test if a ProBoolean.CreateBooleanObject() call fails?

If I try something like this;

[code]

result = result=ProBoolean.CreateBooleanObject source target 3 0 0;

[/code]

It always returns 'OK' even if the merge fails.

Thanks in advance.

Re: [MaxScript] Test if ProBoolean.CreateBooleanObject() fails

attilaszabo — Wed, 18 May 2016 15:49:55 GMT

Jason, the CreateBooleanObject() function returns void hence you always get OK as a result.

I agree that it would be much more helpful if it returned the new object it created if successful, and undefined it it werent.

Re: [MaxScript] Test if ProBoolean.CreateBooleanObject() fails

larryminton — Wed, 18 May 2016 16:13:42 GMT

Bit of a hack, but you can check the objects.count value before and after the call. If successful, the target node is deleted, so the count will go down by one.

Re: [MaxScript] Test if ProBoolean.CreateBooleanObject() fails

JasonCampbell — Wed, 18 May 2016 21:18:48 GMT

The problem with counting the objects is that when the boolean fails the target object is being deleted anyway, resulting in dissapearing meshes. So the object count is going down either way.

Re: [MaxScript] Test if ProBoolean.CreateBooleanObject() fails

larryminton — Wed, 18 May 2016 21:31:57 GMT

I don't know what your definition of failure is here.

Is the operation succeeded in terms of creating the boolean object? That is, what class is the source node after you make the call and it 'fails'?

If you select the source object and go to Operands SO mode, are the 2 original objects shown in the Parameters rollout?

Re: [MaxScript] Test if ProBoolean.CreateBooleanObject() fails

JasonCampbell — Wed, 18 May 2016 22:02:37 GMT

My definintion of failure is

The objects don't have any self intersecting geometry (unless ProBoolean is creating it after multiple merges).

In the occurance of the above error the 'source' geometry is deleted and the 'target' geometry becomes the result of the operation. So, you end up with one less item of geometry, breaking the 'count' workaround.