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.)
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.)