Serious issues with boolean operations?

[savage]

Okay, this is really strange and just started accuring. My Boolean operations are all messed up and switched around. my union is swapped with my difference and my intersect performs the exact opposite as it should and gives me the result of were they don't intersect instead of where they do. What's up with that?

[jesterKing]

Do your objects have negative scaling?

/Nathan

[savage]

Do your objects have negative scaling?

/Nathan

No, just some extrudes and normal scaling but I suppose it is possable I could have not knowingly scaled one of them into the negative but I don't think so. Does this happen when you do scale in the negative? Oh, and one more thing, when will the windows installer be ready for 2.49, any word yet? 2.49 looks awesome, I can't wait to get my hands on it! Blender is the greatest thing since sliced bread if you ask me!

... And the new material nodes... SWEET!

[lawi]

I also made some simple tries with the boolean operation "difference".
I just started up with the initial cube mede it a litte bigger.
I added an UVsphere and Add Multires to it (one time).

The I intersected the sphere with the cube only 20% of the spher is inside the cube.

Now I tried to select both and press W and select Difference.
First what I found that I have to select the cube and sphere in reverse order to get a 'dip' in the cube.
Next is that after the operation started ....
it takes a while and blender 2.49 simply closes the application.

I tried the same with blender 2.45. With this version I get my 'dip'.

Which version is the most stable regarded to the boolean operations?

Thanks.
Lawi

[psullie]

I'm guessing that it's a 'too many polys' issue. Blender wigged out because it was asked to cut two-three dozen polys out of one (the cube face)

To get this to work, subdivide the Cube 5 or 6 times, then Boolean your sphere. It's far easiest when doing booleans to do like with like as far as poly count is concerned.

[elicia]

Okay, this is really strange and just started accuring. My Boolean operations are all messed up and switched around. my union is swapped with my difference and my intersect performs the exact opposite as it should and gives me the result of were they don't intersect instead of where they do. What's up with that?

Hi,

I had exactly the same problem than Savage : when I WKEY->union, I got intersection. Restarting blender corrected the problem. I did not manage to trigger this behavior again.

Config : Blender 2.49a on ubuntu intrepid with EEEPC 1000H.

Best,
Elicia