 | | Re: Datsville continuation - more ideas
|
| (...) Doesn't POVray do this inately? After all, at some point POVray has to decide which information it will display, and which information it will not display. Wouldn't it speed up the rendering process even more if all LDraw models were turned (...) (23 years ago, 13-Aug-01, to lugnet.cad, lugnet.cad.dev, lugnet.cad.ray)
| | | | | Re: Datsville continuation - more ideas
|
| (...) I don't know. That's why I asked. :o) I will try to render a lot of ttore.dat's in a model and compare the time used to the time used to render the same model with box replacements. (...) Yes, but how do we accomplish that still avoiding bad (...) (23 years ago, 13-Aug-01, to lugnet.cad, lugnet.cad.dev, lugnet.cad.ray)
| | | | | Re: Datsville continuation - more ideas
|
| (...) And the results are: 16 original ttore.dat's @ 800x600: 3 min 56 sec 16 simplifed ldbox.dat's @ 800x600: 1 min 26 sec I think it's worth keep working on! /Tore (23 years ago, 13-Aug-01, to lugnet.cad, lugnet.cad.dev, lugnet.cad.ray)
| | | | | Re: Datsville continuation - more ideas
|
| (...) If I understand the question correctly, and from my understanding of how a ray- tracer works, Pov-ray must keep all polygon data while it renders since it "traces" all the light rays, even those that you can't see (inside of a brick). It (...) (23 years ago, 14-Aug-01, to lugnet.cad, lugnet.cad.dev, lugnet.cad.ray)
| | | | | Re: Datsville continuation - more ideas
|
| Hey, no problem. I just browse Lugnet every once in a while to see if any progress on such a utility exists. I notice there has been little mention of such a thing in the newsgroups in the past. It would be a "cool" toy. Thanks, Mike (...) (23 years ago, 15-Aug-01, to lugnet.cad, lugnet.cad.dev, lugnet.cad.ray)
| |
