 | | Re: Rendering implementation details
|
|
(...) You're right about the performance hit. We've discussed this issue previously on lugnet, because quite a few of the renderers out there use opengl (ldview, leocad, ldglite, Mac Brick Cad...) Source code is available for all of these if you (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) Someone once suggested to me (Dan from Microsoft maybe?) that given today graphics libraries, one could probably get away with ignoring op-lines altogether and use edge detection. This would present a potential problem since edge color is (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Rendering implementation details
|
|
I was envisioning how an LDraw renderer would be implemented if it were done with OpenGL, and I've arrived at some questions that I can't answer for myself. I'm particularly wondering about line type #5, the optional line. According to the LDraw (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat [DAT]
|
|
(...) I updated the camera.dat and look_at.dat so they don't need to be REMmed out: 0 ~Camera Position 0 Name: Camera.dat 0 Author: Tore Eriksson 0 Un-official part 2 24 -4 0 0 4 0 0 2 24 0 -4 0 0 4 0 2 24 0 0 -4 0 0 4 0 L3P IFNOTPOV 1 0 0 25 37 1 0 (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat
|
|
(...) Yes,I am very well aware of the multitude of camera settings POV offers, and I haven't yet decided which way to go. The fastest way may be to run my own race using my own META statements: 0 LDA CAMERA.POSITION x y z 0 LDA CAMERA.LOOKAT x y z 0 (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev, lugnet.cad.ray)
|
