Question concerning the internal buffer size for Booleans on OS-X

[Eugeny]

If u get this massage on Mac u will get the same on PC - just try it !
There is no way to adjust internal buffers - try to move the Boolean operands, triple polygons or eliminate 2 point poly if u have ...
... and stop blame Macs , i know u hate macs as i hate PC - but i not screaming on all corner that damn PC LW not working or crashing or not working for me (believe me i have lot of problems with PC) ...
P.S. (hope the new war will be started :) ... just a joke. )

[lightwolf]

Originally posted by red_oddity

Now the problem comes, the Mac LW version (7.5) starts whining about the 'internal buffers being too small for the requested operation' and aborts the Boolean operation (i tried doing this section by section already and poly by poly for the intersecting polygons, to no avail).


Hi,

LW doesn't have a 'internal buffers being too small for the requested operation' error message, only if you use a cracked version.
So, maybe you should buy a legit license, and the problem will go away.

Cheers,

Mike

[wgreenlee1]

I dont know where everyone keeps coming up with this LW crashing stuff?
LW ,for me at least,was always the most stable of any application Ive had.
Ive had it for 7months and it crashed maybe twice and was usually the fault of XP,it never crashed on 98se.

[Eugeny]

Originally posted by lightwolf
Hi,

LW doesn't have a 'internal buffers being too small for the requested operation' error message, only if you use a cracked version.
So, maybe you should buy a legit license, and the problem will go away.

Cheers,

Mike

For this massage there is nothing to do with crack - i get the same massage with licensed version... It's just about right modeling, that's all.

[red_oddity]

Originally posted by lightwolf
Hi,

LW doesn't have a 'internal buffers being too small for the requested operation' error message, only if you use a cracked version.
So, maybe you should buy a legit license, and the problem will go away.

Cheers,

Mike

Actually, i have a legit version, buddy, so stop throwing mud... You want a scan of my CD covers, or should i just type my serial and dongle serial here? Or will my word do and you gonna give me a decent answer when you have one, or are you gonna tread me like some newbie hacker kiddo again?

And Eugeny, as i said, i wanted a simple answer, not annother G**damn flame war. And i told you, the PC doesn't do the internal buffer error (i use the exact same objects, they are even opened over the network from a Mac), so that was my only question, not to blame the Mac for anything, i just wanted to know where i could adjust my internal buffer.

I did notice though that the problem goes away when using tripled polygons rather than quads, but then other problems arise (mostly calculation problems)

So, does someone have a decent answer? or should i just delete this entire post?

[Eugeny]

Originally posted by wgreenlee1
I dont know where everyone keeps coming up with this LW crashing stuff?
LW ,for me at least,was always the most stable of any application Ive had.
Ive had it for 7months and it crashed maybe twice and was usually the fault of XP,it never crashed on 98se.

Modeler is really stable but Layout ...
Try to work with rigged character with morphs and sound loaded to time line - then i close scene or exit the program i get crash :annoyed:
May be it's depend on my card or any other PC stuff i don't know. I can say only one thing LW Modeler is rock solid but Layout is far from this ...

[ThE_JacO]

Originally posted by red_oddity

Now the problem comes, the Mac LW version (7.5) starts whining about the 'internal buffers being too small for the requested operation' and aborts the Boolean operation (i tried doing this section by section already and poly by poly for the intersecting polygons, to no avail).


I can only roughly guess (hell i'm not even a LW user anymore) but you could want to try scaling up all the objects.

if it has to do with math precision issues (and it very much sounds like that) scaling up usually reduces the amount of decimals and makes math easier to crunch for the CPU.
I never coded anything for Macs, but i heard about this issue (in other situations) a good deal of time, so i'd blame it on that.

[Eugeny]

Originally posted by red_oddity

And Eugeny, as i said, i wanted a simple answer, not annother G**damn flame war. And i told you, the PC doesn't do the internal buffer error (i use the exact same objects, they are even opened over the network from a Mac), so that was my only question, not to blame the Mac for anything, i just wanted to know where i could adjust my internal buffer.

I did notice though that the problem goes away when using tripled polygons rather than quads, but then other problems arise (mostly calculation problems)

So, does someone have a decent answer? or should i just delete this entire post?

Well, sorry for that :)
As i say try to move the operands, even cut / paste the part that mast be booleaned to another layer and triple only these polygons ...
Some times if u have big poly (i mean more then 4 points) the boolean is not working ...
Hope this will help.

[red_oddity]

Ah, that's okay, i just had to go and figure out a workaround really quick ( the time limits on these previz jobs are insane...), i came up with a solution that didn't involve booleans whatsoever (even though it leaves a incredible mess (i'm not scoring any points here on clean meshes...but what the heck))

Thanx anyway, but that still leaves the question (i will try that upscale though (and might try that with some quantisation on my point coordinates))

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.