 | | Re: Need volunteer to test LdGLite on accelerated hardware.
|
|
(...) Oops, Sorry, I just needed to save target as. -Chuck (25 years ago, 16-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: Need volunteer to test LdGLite on accelerated hardware.
|
|
(...) I tried this link, and it said the page was unavailable. -Chuck (25 years ago, 16-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: Need volunteer to test LdGLite on accelerated hardware.
|
|
(...) Yeah, I know all about that. A few experimental releases back I was printing NULL strings instead of actual version info (Which made it crash on linux). The current experimental code grabs the version after opening the window. So have you (...) (25 years ago, 16-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: Need volunteer to test LdGLite on accelerated hardware.
|
|
[...SNIP...] (...) Some (almost all) implementations of OpenGL Drivers only after creating a window do: - reset the GL_ERROR state variable - supply correct state strings which obviously include the GL_VERSION (and all other) string(s). Make sure (...) (25 years ago, 16-Mar-00, to lugnet.cad.dev)
|
| |
| | Need volunteer to test LdGLite on accelerated hardware.
|
|
Would anyone with a 3D accelerated video board running windows like to run a test on LdGLite? The current windows executable in the experimental ldglite source zip file prints out the opengl version used. When it uses the unaccelerated software (...) (25 years ago, 16-Mar-00, to lugnet.cad.dev)
|
