Subject:
|
Re: Datsville Overview Map (Was: Boundary Box Utility)
|
Newsgroups:
|
lugnet.cad, lugnet.cad.dev
|
Date:
|
Thu, 16 Aug 2001 16:23:52 GMT
|
Viewed:
|
79 times
|
| |
|
|
Here is another idea for optimizing dat models. It isn't a very good one, but,
it just seems more realistic than what I said earlier (writing a utility smart
enough to optimize an entire model).
One could write a utility that presents each polygon to the user and asks to
keep it or get rid of it. Then it writes a flat file of polygons (rather than
file references) that represents the model.
The optimized model would not be very editable. And it would take a long time
to optimize a big model. But if one plans on making alot of renderings with the
one model, then it might be worth it.
The boundary box utility could also make obvious choices (like, if it is visible
from outside of the boundary box, it wont even ask.
Just an idea.
--
Thanks:
James Reynolds
http://www.cc.utah.edu/~jer29950
james.e.reynolds@m.cc.utah.edu
james@mail.mlmc.utah.edu
|
|
Message has 1 Reply:
Message is in Reply To:
 | | Re: Datsville Overview Map (Was: Boundary Box Utility)
|
| This is great! An idea: if bitmaps were created of the model from 6 directions (left, right, bottom, top, front, back), you could texture map those to the boundary box (inside, to make sort of a 6 point, 3 plane cross intersecting in the center) and (...) (23 years ago, 16-Aug-01, to lugnet.cad, lugnet.cad.dev)
|
12 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
