 | | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) Great! (...) It's local when you look at it in the .DAT where it is used. It's effect is NOT local, when you are looking from the renderer program's view, because it has to keep track of the current invert state. The INVERT meta-command only (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) Yes it is. (...) The reference of the current GLOBAL state is passed down the file-reference tree, YES. (...) Correct. (...) NOT the FILE, but the RENDERING PROGRAM ! (...) Agreed. (...) By default would be CCW. (...) YES and NO. The internal (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) If by default you always use the same winding, then you can know the orientation of the polygon on the fly. IF you mix both you will have a hard time, because you are mixing or reference. (...) That I agree! but my NOTE (suggestion) to pair (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Several replies to CLIPPING / WINDING
|
|
(...) Great ! (...) Don't be pessimistic ! As soon as people see that their models render twice as fast, they will start using the new features. And a utility to make the optimization job easier would make a big difference, to all the lazy people ;) (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Several replies to CLIPPING / WINDING
|
|
(...) That can be done, but you will probably suffer a performance hit, because, most hardware, just use a bit, to keep track of the state. Just minimize the use of the 0 CCW and 0 CW meta-commands, to boost performance. When optimizing existent or (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Several replies to CLIPPING / WINDING
|
|
(...) By candidate, I meant, someone could optiomize it, a place a 0 CLIPPING ON meta-command on it, and get some benefit. If you use enable clipping, but you have no graphic primitives in your file (assuming clipping is stryctly local), than you (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Several replies to CLIPPING / WINDING
|
|
(...) NO, I said that, to be used when optimizing the existent files, not when rendering the optimized files. (...) I never said that ! (...) I think that depends on the host processor that you have and your specific graphics board (2D/3D) ;) (...) (...) (25 years ago, 20-Oct-99, to lugnet.cad.dev)
|
| |
| | [ldraw.org] Model of the Month
|
|
I have just added the Model of the Month pages to ldraw.org. We're going to shoot for the first award being given for November. Entries are being accepted until Monday October 25, and voting will take place until Sunday October 31. The winning entry (...) (25 years ago, 20-Oct-99, to lugnet.general, lugnet.announce, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) Yes the coded inversion is needed, for one big reason: The clipping-ready parts library must be compatible with non-clipping rendering programs, such as LDraw. So the inversions need to occur in the real commands, not in the clipping-extension (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
(...) <snipped stuff about INVERT> I think we're disagreeing about the meaning of 'strictly local'. As you describe the operation of INVERT, it is *not* local. The state of inversion is passed down the file-reference tree. This is not a local (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
