 | | 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)
|
| |
| | 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)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
Rui Martins wrote in message ... (...) I concur that WINDING is strictly local. It may be a struggle of words, but I wouldn't call INVERT *local* as it affects the behaviour all tris/quads in *subfiles* And I don't see why clipping should be local. (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING
|
|
Rui Martins wrote in message ... (...) Part authors should define the tris/quad the way he finds best, easy and logical - maybe sometimes CW and sometimes CCW. Also when fixing old parts, just insert a lot of WINDING keywords in stead of editing the (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Object Orientation & DAT files & CLIPPING/WINDING [DAT]
|
|
Steve Bliss wrote in message <380b3366.9260126@lu...et.com>... (...) No, you don't need to bother with the matrix. Use the 0 INVERT to tell the renderer: "Hey, please turn the following subfiles inside-out". Remember the example from stud2.dat: 1 16 (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
| |
| | Re: Several replies to CLIPPING / WINDING
|
|
(...) We both want the same thing, now we need to make everybody agree with us :) (...) I sort first by color and then by line type. I have everything pre-processed and I don't use glBegin()/glEnd() to render. (...) From my personal experience, (...) (25 years ago, 19-Oct-99, to lugnet.cad.dev)
|
