 | | Re: Rendering implementation details
|
|
(...) I'm not 100% sure, but I believe most (if not all) of these outlining algorithms expect you to know the difference between the front faces and the back faces. It could be that they could be adopted for use when you don't have this information, (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) I'm not sure it's possible to implement for real without serious slowdowns. It might be possible to implement in a vertex program, but I haven't studied vertex programs, so I really don't know. (I'm pretty sure you can't throw out a vertex (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Cross platform GUI
|
|
(...) The look and feel is one of the reasons why I rejected GTK (...) To me, compile times are a non issue. However the non-free nature of Qt leaves a bad taste in my mouth (and I not even a Open Source zealot). I can however develop a Qt based (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat
|
|
(...) It would be nice if there were also a part used to store points. It would then be declared at the end of the .pov file as a uniquely named vector. (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | 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)
|
