 | | Re: About datsville —Tore Eriksson
|
| | | I think it's all. Isn't it enough? ;o) One thing I must say: L3P is really impressive. It takes 34-41 seconds to render the whole town.mpd on my very burdened P2-450/128. Next step is to find that mpd splitter utility... /Tore (...) (23 years ago, 11-Aug-01, to lugnet.cad)
|
| | | |
| | | | | Re: About datsville —Fredrik Glöckner
|
| | | | (...) Wow! That's quick! Does the 34-41 seconds include the time needed for parsing in POV-Ray? (I assume you are talking about L3P/POV-Ray usage?) When rendering images using L3P/POV-Ray, I commonly find that the parsing of the scene takes a minute (...) (23 years ago, 15-Aug-01, to lugnet.cad)
|
| | | | |
| | | | | | Re: About datsville —Tore Eriksson
|
| | | | (...) I'm very sorry for the typo. I meant L3Lab... I haven't even bothered to try rendering all Datsville using POVray. /Tore (23 years ago, 15-Aug-01, to lugnet.cad)
|
| | | | |
| | | | | | Re: About datsville —Fredrik Glöckner
|
| | | | (...) Oh, but it's still very interesting to hear that rendering Datsville is that quick in L3Lab! It sounds to me like future renderings of Datsville will probably be done in L3Lab rather than POV-Ray. By the way, do anybody know if rendering (...) (23 years ago, 15-Aug-01, to lugnet.cad)
|
| | | | |
