| |
John VanZwieten wrote...
> Maybe you could test to see which studs are completely contained within the
> bounding box of a list of standard parts (regular bricks and plates, etc.)
> then replace a part with a simplified version if all its studs are so
> contained. I'm not sure how to phrase a similar test for the underside faces
> and studs. Maybe if a 2x4 brick contains 8 studs (not including it's own)
> inside its bounding box, then you can leave out the underside.
>
> I could see at least two different implementations of this idea: First would
> be an "optimization" option in L3P, which would direct L3P to run the
> optimization tests, and make any substitutions in the resulting .pov file.
> The original .dat file would remain untouched.
>
> The second implementation would create an optimized .dat file which could be
> viewed in any rendering engine, with the understanding that if you later edit
> the file, you may get ugly results. For Datsville, when someone submits a
> house, I would run the optimization routine, then include the optimized file
> in the town scene.
A general analyzer may be a good idea. As you say, the optimized .dat file
can be viewed in any rendering engine, and also, you can run L3P on it.
Of course, the analyzer could be compiled into L3P, L3Lab, LDLite etc.
/Lars
|
|
Message is in Reply To:
 | | Re: L3PLiTE?
|
| Tore Eriksson <tore.eriksson@mbox3...wipnet.se> wrote in message news:38DE84F4.380C9D...pnet.se... (...) only those standard bricks, plates, and tiles (...) could be a way to free up some resources for (...) somehow, and I don't know exactly how (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
|
19 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
