Using the Hollow-tool will delete object
by DreamPharaoh · in Constructor · 12/11/2008 (7:15 pm) · 8 replies
I have not used constructer in a while and I wonder if updating the video card driver a month ago is causing this issue.
Anyway when I make a simple box and apply the hollow-brush it will delete the box instead.
Also I was wondering if it may be better to buy Houdini for TGEA and make DTS buildings instead. The current problem I am having with Blender-made dts objects is that the character will get stuck on the polysoup enabled mesh, and so I am wondering if Houdini will cause this same issue making it a dead end solution as well. I may need to get a new computer and start from scratch, any thoughts.
Computer Specs
System Information:
OS: Windows XP second edition
CPU: Ath64 4K 2.4gig
Memory: 1 gig
Video Card: Nvidea Gfor. 7300 GS
Sound Card: Legacy Audio
Hard Disk: 126 gig free
Connection: Broadband
Anyway when I make a simple box and apply the hollow-brush it will delete the box instead.
Also I was wondering if it may be better to buy Houdini for TGEA and make DTS buildings instead. The current problem I am having with Blender-made dts objects is that the character will get stuck on the polysoup enabled mesh, and so I am wondering if Houdini will cause this same issue making it a dead end solution as well. I may need to get a new computer and start from scratch, any thoughts.
Computer Specs
System Information:
OS: Windows XP second edition
CPU: Ath64 4K 2.4gig
Memory: 1 gig
Video Card: Nvidea Gfor. 7300 GS
Sound Card: Legacy Audio
Hard Disk: 126 gig free
Connection: Broadband
About the author
If you want to learn more, please go to my website. GodsandNemesis.com.
#2
That's the only I could duplicate your problem. Think about it: a default 1X1X1 cube, the default Wall-thickness setting is 0.5. Add together all of your wall-thicknesses top-bottom/left-right/front-back subtract them from the cube and you'll be left with nothing. Makes sense to me. Not really an issue since anytime that wall-thickness is equal to half the size of your object I would expect that behavior.
Houdini vs Blender is subjective to the user. I've never used Houdini, but I use Blender and can't say I've experienced your problem. I doubt it would be a hardware or driver problem. Possibly a design flaw or collision error somewhere.
12/11/2008 (8:08 pm)
Did you use the default settings for the cube and the hollow tool? That's the only I could duplicate your problem. Think about it: a default 1X1X1 cube, the default Wall-thickness setting is 0.5. Add together all of your wall-thicknesses top-bottom/left-right/front-back subtract them from the cube and you'll be left with nothing. Makes sense to me. Not really an issue since anytime that wall-thickness is equal to half the size of your object I would expect that behavior.
Houdini vs Blender is subjective to the user. I've never used Houdini, but I use Blender and can't say I've experienced your problem. I doubt it would be a hardware or driver problem. Possibly a design flaw or collision error somewhere.
#3
Small details can confuse opcode, especially if you have something like a chair rail or do baseboards that can catch different parts of the model for apparently no reason at all. I believe the player is still a bounding box, too. I need to get in and play more with this. It has been a while since I've touched polysoup modeling and collision. I've been working on other things, sadly. To bad I'm a crap artist (which could be a ton of my problems!)
12/11/2008 (8:19 pm)
Heh. That makes perfect sense. Strangely, I don't think I've tried to hollow anything to a point smaller than the shape.Small details can confuse opcode, especially if you have something like a chair rail or do baseboards that can catch different parts of the model for apparently no reason at all. I believe the player is still a bounding box, too. I need to get in and play more with this. It has been a while since I've touched polysoup modeling and collision. I've been working on other things, sadly. To bad I'm a crap artist (which could be a ton of my problems!)
#4
12/11/2008 (8:25 pm)
I have the updated Constructer version 1.0.51 and I have used various wall thicknesses. It seems to now allow me to use this option but instead of making the object hollow it will automatically go into face-mode and list 6 faces in the right window after using the hollow-brush even though I an in brush-mode.
#5
Create cube:

Hollow cube and set wall thickness:

Cube hollowed and the geometry broken into six brushes:

Or am I misunderstanding something?
EDIT:
Fixed the images. I had somehow set my FTP session to ASCII instead of Binary...grrr!
12/11/2008 (8:38 pm)
Oh. It is doing what it is supposed to do. It is breaking up the geometry to create a hollow cube. When you hollow a cube, you end up with six brushes, each of the thickness you specify.Create cube:

Hollow cube and set wall thickness:

Cube hollowed and the geometry broken into six brushes:

Or am I misunderstanding something?
EDIT:
Fixed the images. I had somehow set my FTP session to ASCII instead of Binary...grrr!
#6
12/11/2008 (9:15 pm)
Quote:Heh. That makes perfect sense. Strangely, I don't think I've tried to hollow anything to a point smaller than the shape.I just tried. It seems that only a wall thickness of exactly half, equal to, or greater than the shape's size will cause the object to be deleted. Using a wall thickness of more than half created some odd geometry formations in the new walls - but the resulting shape was still hollow.
Quote:it will automatically go into face-mode and list 6 faces in the right window after using the hollow-brush even though I an in brush-modeNow that I've never seen before. I just spent about an hour messing around in Constructor hollowing things - even spheres - and it always remained in Brush-mode for me.
#7
12/11/2008 (11:47 pm)
I'd wipe out constructor completely, then reinstall and patch up.
#8
12/12/2008 (7:33 am)
It seems I copied the update wrong, and by uninstalling Constructor and reloading it and re-applying the upgrade it solved the issue. Thank you for the direction, on this.
Associate David Montgomery-Blake
David MontgomeryBlake