 | | | Boolean action problems ? - Whys and resolves (maybe) to | Boolean action problems ? - Whys and resolves (maybe) to 2005-07-06 - By David
Back
Hello list.
No, - No to what ?
Can the effects of a boolean subtraction operation on a high polygon count
object be reduced
given the possible workflow or workpace considerations noted in the initial
question.
No, I have tested this to an extent and still.
So what to do ?
Scope your projects requirements and do your booleans early in the project. ?
Will this create other problems and can point edit tools assist to reduce the
problem while creating ? Don't know to this and think it is possible and will
keep on checking.
David
David <hawksridge@(protected)> wrote:
Hello list,
Boolean problems may be eliminated or reduced with the following questions and
answers. For your consideration and response.
Questions which required answers:
1): What doe the boolean action do and what happens to an object in the process?
2): Does the pace of workflow have anything to do with the problem?:
3): How to resolve this with answers to the above two questions ?
First, What booleans do:
1): Booleans act on an and change an objects face. 2): An objects meshes must
reform to get the face to conform to new angles and an exact (not) similar
mesh as its existing body.
3): The process of boolean action involves a lengthy calculation process to
exact just how the meshes will attach.
Proposed Resolve: A,B,C
A): One resolve is to eliminate item #3. as the problem. Why ? If a calculation
is still in process when exacting the boolean operation then the objects
future state reference (from calculations) may not be resolved. This defeats
the objects reform noted in #2. To check this : read the performance meter
found in the task manager (XP) and if the cpu is still occupied then something
is still going on in the calculation process. Wait a bit to clear the cpu
processing activity before doing the boolean operation .
B): The other is that other workspace actions may occur too soon after the
boolean action has been performed which may interfere with some value required
to resolve the mesh due to processing and referencing errors. This may be a
motherboard or video card processing limitation. Again wait for the computer
to cool down.
C): Think about your meshes before doing them. Just what this means may or may
not have any value.
I like A and B and (eliminate C for the most part) to resolve or at least
minimize the problem.
These are my thoughts which may or may not be correct but I hope shed some
light on the subject towards complete resolve. Other suggestions towards this
resolve either way will be helpful.
Thanks
David
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ______
****************************************************************************
********
This message has been checked for all known viruses by the Cable & Wireless
E-mail Virus Protection service, powered by MessageLabs.
To purchase this service, please contact your Cable & Wireless Account
Manager.
****************************************************************************
********
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ______
****************************************************************************
********
This message has been checked for all known viruses by the Cable & Wireless
E-mail Virus Protection service, powered by MessageLabs.
To purchase this service, please contact your Cable & Wireless Account
Manager.
****************************************************************************
********
<DIV>Hello list.</DIV>
<DIV> </DIV>
<DIV>No, - No to what ?</DIV>
<DIV> </DIV>
<DIV>Can the effects of a boolean subtraction operation on a high polygon count
object be reduced</DIV>
<DIV>given the possible workflow or workpace considerations noted in the
initial question.</DIV>
<DIV> </DIV>
<DIV>No, I have tested this to an extent and still. </DIV>
<DIV> </DIV>
<DIV>So what to do ? </DIV>
<DIV> </DIV>
<DIV>Scope your projects requirements and do your booleans early in the project
. ?</DIV>
<DIV> </DIV>
<DIV>Will this create other problems and can point edit tools assist to reduce
the problem while creating ? Don't know to this and think it is possible
and will keep on checking.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR>David<BR><BR><BR><B><I>David <hawksridge@(protected)></I></B>
wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER
-LEFT: #1010ff 2px solid">
<DIV>Hello list,</DIV>
<DIV> </DIV>
<DIV>Boolean problems may be eliminated or reduced with the following questions
and answers. For your consideration and response. </DIV>
<DIV> </DIV>
<DIV>Questions which required answers:<BR>1): What doe the boolean action do
and what happens to an object in the process?</DIV>
<DIV>2): Does the pace of workflow have anything to do with the problem?:</DIV>
<DIV>3): How to resolve this with answers to the above two questions ?</DIV>
<DIV> </DIV>
<DIV>First, What booleans do:</DIV>
<DIV>1): Booleans act on an and change an objects face. 2): An objects
meshes must reform to get the face to conform to new
angles and an exact (not) similar mesh as its existing body. <BR>3): The
process of boolean action involves a lengthy calculation process to exact
just how the meshes will attach.</DIV>
<DIV> </DIV>
<DIV>Proposed Resolve: A,B,C<BR>A): One resolve is to eliminate item #3. as the
problem. Why ? If a calculation is still in process when exacting the
boolean operation then the objects future state reference (from calculations)
may not be resolved. This defeats the objects reform noted in #2. To
check this : read the performance meter found in the task manager (XP) and if
the cpu is still occupied then something is still going on in the calculation
process. Wait a bit to clear the cpu processing activity before doing the
boolean operation .</DIV>
<DIV> </DIV>
<DIV>B): The other is that other workspace actions may occur too soon after the
boolean action has been performed which may interfere with some value
required to resolve the mesh due to processing and referencing errors.
This may be a motherboard or video card processing limitation. Again wait
for the computer to cool down.</DIV>
<DIV> </DIV>
<DIV>C): Think about your meshes before doing them. Just what this means may or
may not have any value. </DIV>
<DIV> </DIV>
<DIV>I like A and B and (eliminate C for the most part) to resolve or at least
minimize the problem.</DIV>
<DIV> </DIV>
<DIV>These are my thoughts which may or may not be correct but I hope shed some
light on the subject towards complete resolve. Other suggestions towards this
resolve either way will be helpful.</DIV>
<DIV> </DIV>
<DIV>Thanks </DIV>
<DIV><BR>David</DIV>
<DIV> </DIV>
<DIV> </DIV><BR>__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ _____
__ ____ ___<BR>*****************************************************************
***********<BR>********<BR>This message has been checked for all known viruses
by the Cable & Wireless<BR>E-mail Virus Protection service, powered by
MessageLabs.<BR><BR>To purchase this service, please contact your Cable &
Wireless Account<BR>Manager.<BR>***********************************************
*****************************<BR>********<BR></BLOCKQUOTE>
<BR>
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ______<BR>
****************************************************************************<BR>
********<BR>
This message has been checked for all known viruses by the Cable & Wireless<BR>
E-mail Virus Protection service, powered by MessageLabs.<BR>
<BR>
To purchase this service, please contact your Cable & Wireless Account<BR>
Manager.<BR>
****************************************************************************<BR>
********<BR>
|
|
|