| | Re: Suggestion for MLCad Plug-Ins
|
|
(...) I like that idea. (...) Yep. The idea is for LDAO to be both a source and sink for dragged parts. (...) Two approaches: 1. Allow multiple formats for the string being passed in the WM_COPYDATA message. One format is the one you're already (...) (25 years ago, 2-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
|
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) How long does it take with LdGLite on your P400? Try it at a similar resolution with the -V6 or -V5 command line switches to make it fair. Go ahead, I won't be embarrased if the numbers are really poor since I've spent absolutely no time (...) (25 years ago, 2-Feb-00, to lugnet.cad.dev)
|
|
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) Well I haven't read the section of the book on vertex arrays yet. From a quick glimpse I suspect they won't help me much since I'm using the LDRAW files rather than a converted database of parts. I'm surprised you don't use display lists at a (...) (25 years ago, 2-Feb-00, to lugnet.cad.dev)
|
|
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) Bummer. (...) STB Velocity 400. I should know the chipset, but I don't. Steve (25 years ago, 2-Feb-00, to lugnet.cad.dev)
|
|
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) Whoa. That's the same WTOWER.DAT distributed with ldglite. The one that LDLite, on my Pentium 400 with Win98, renders in 5.8 seconds? Amazing. Steve (25 years ago, 2-Feb-00, to lugnet.cad.dev)
|