LDraw.org Discussion Forums

Full Version: some train images rendered with the recent parts update 2012-01
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Maybe you'd like to look at some images
which I had used during the 12V train parts creation for parts update 2012-01.
I finally also got myself a brickshelf folder...

[Image: 4.5v_tapered.jpg]

[Image: 4.5v_slotted.jpg]

[Image: 12v_tapered.jpg]

[Image: 12v_slotted.jpg]

[Image: 7866.jpg]

[Image: image01.jpg]

[Image: image02.jpg]

[Image: image03.jpg]

[Image: image04.jpg]

[Image: image05.jpg]

play well
Nice work. Out of interest how long did they take to parse?
not long.
the file structure efficiency of our ldraw files directly translates
into the same efficiency of the resulting .pov file.
for example, because the riffled top of the train rail track makes efficient use of a subfile,
the resulting .pov data is comparibly small.
previously, the rail had modeled all its riffles by individual quads, without subfile usage.
this resulted in a much bigger and inefficient .pov file (and .ldr file).
(in fact, that was the reason why I had refactured that rail part:
both the ldraw and pov representation had a benefit from that.)
the same goes for the other parts. for example, the 12v train point also makes
efficient usage of subfiles. parsing its .pov representation goes comparably fast.
to name some numbers, if I remember correctly, parsing even the big scenes files with povray only took 2-5 seconds.
(however, I'm running on a quite fast machine with ssd and plenty of ram etc.pp.)
Cool. That's surprisingly quick. And yes proper subfiling makes a huge difference to POVray which is why I was curious Smile

have just re-rendered e.g. 12V Slotted.jpg: parsing time: 7 seconds