|
 |
I can appreciate that, but I haven't learned that much of the SDL yet, and I
have scant programming experience, anyway.
I can appreciate conceptually that a #while loop would automate the
construction and the coding quite a bit, but my 'style' of workflow on my
POV scene is that I tend to go ahead and write *some* code according to the
first 'version' of a scene element that occurs to me, with the intention of
eventually substituting more efficient 'versions' of the elements as I learn
more SDL.
I just haven't gotten to these macros and loops yet. In time.... ;-) I
also spend/waste a fair bit of time downloading trial modelling apps,
usually ending up puzzling over the docs and the interface before I
determime that I don't know how to make it do what I have in my
cobweb-filled head!
--Mark
Ib Rasmussen wrote:
> Mike Williams wrote:
>
> > 4. for real speed (and coding simplicity) use a #while loop to place
> > each individual brick,
>
> I'll second that! The stuff you are doing is much much easier to do with
> loops. Trust me, I have done a lot of individual-brick-placing myself.
> My latest church has over 100000 objects. I couldn't have done that
> without loops.
>
> /Ib
Post a reply to this message
|
|
|
|
Thanks for your link to the tutorial. Having applied its principles (as
particularly spelled out in your most recent posting on this thread) I
have been going through my scene files with a fine-tooth comb, and have
found a couple of elements/objects which benefitted greatly -- and
others for which my initial versions were slightly superior. ;-)
Going "back to the drawing board" is sometimes a bit of a bother, but
always a learning experience.
Many thanks again!
--Mark
Mike Williams wrote:
>
> Wasn't it LibraryMan who wrote:
> >As I replied to Bob Hughes, the stats in both the unioned version and
> >the diff'd version indicated that the scene contained 2 objects, which
> >mystified me, until I realized it was probably referring to the one
> >declared object, which I placed *2* instances of side-by-side in the
> >scene, like so:
> >
> >[ #declare inter_arc = union { etc. ... } ]
> >
> >object { inter_arc } //which is 1.6 units wide
> >object { inter_arc translate x*1.6 }
> >
> >I discovered that my default bounding threshold was 3, so I lowered it
> >to 2 for the sake of the experiment, and this DID improve the rendering
> >time of both versions SLIGHTLY, but the diff'd version still rendered a
> >little faster than the unioned version, which as stated in my original
> >posting, I thought was counter-intuitive.
> >
> >I suppose I may not be the first ever person who ends up completely
> >re-writing his scene, once he learns more SDL...
> >
> >Should I end up posting the code I'm talking about? Maybe someone else's
> >mileage will vary. Yeah, what the hey!
>
> Right, I've now looked at your code, and the significant factor is that
> BOTH your inter_arc objects contain a difference operation that clobbers
> the bounding. I suggest that you go back to my hole tutorial page and
> read it more carefully this time. Then try the following:-
>
> 1. Make sure that automatic bounding is happening, and then render both
> versions with the bounding slabs displayed ( use the +UD switch).
> Observe that there's a single slab for the whole of the object.
>
> 2. From the first inter_arc, comment out the "difference {" and the
> lines
> }
> cylinder { <-0.4, 0, -0.0101>, <-0.4, 0, 0.301> 1
> texture {T_Grnt19b }}
> cylinder { <-0.4, 0, -0.0101>, <-0.4, 0, 0.301> 1
> texture {T_Grnt19b } translate x*2.4 }
> leaving just the brick wall without the arch cur outs, and render this
> with +UD. Observe that each brick now has its own little bounding box,
> that the number of box tests logged in the stats has reduced by a factor
> of about 200, and that the thing renders very much faster.
>
> 3. Try cutting out the arch cylinders from each row of bricks. You
> should be able to gain much of the bounding improvement. My code for
> doing this looks like this:
>
> #declare arch = union {
> cylinder { <-0.4, 0, -0.0101>, <-0.4, 0, 0.301> 1}
> cylinder { <-0.4, 0, -0.0101>, <-0.4, 0, 0.301> 1 translate x*2.4 }
> }
>
> #declare inter_arc = union {
> difference {object { Row_Odd } object {arch}}
> difference {object { Row_Even } object {arch}}
> difference {object { Row_Odd translate y*0.16 } object {arch}}
> difference {object { Row_Even translate y*0.16 } object {arch}}
> difference {object { Row_Odd translate y*0.24 } object {arch}}
> difference {object { Row_Even translate y*0.24 } object {arch}}
> difference {object { Row_Odd translate y*0.32 } object {arch}}
> difference {object { Row_Even translate y*0.32 } object {arch}}
> difference {object { Row_Odd translate y*0.40 } object {arch}}
> difference {object { Row_Even translate y*0.40 } object {arch}}
> difference {object { Row_Odd translate y*0.48 } object {arch}}
> difference {object { Row_Even translate y*0.48 } object {arch}}
> difference {object { Row_Odd translate y*0.56 } object {arch}}
> difference {object { Row_Even translate y*0.56 } object {arch}}
> difference {object { Row_Odd translate y*0.64 } object {arch}}
> difference {object { Row_Even translate y*0.64 } object {arch}}
> difference {object { Row_Odd translate y*0.72 } object {arch}}
> difference {object { Row_Even translate y*0.72 } object {arch}}
> difference {object { Row_Odd translate y*0.8 } object {arch}}
> difference {object { Row_Even translate y*0.8 } object {arch}}
> difference {object { Row_Odd translate y*0.96 } object {arch}}
> difference {object { Row_Even translate y*0.96 } object {arch}}
> difference {object { Row_Odd translate y*1.04 } object {arch}}
> difference {object { Row_Odd translate y*1.04 } object {arch}}
> texture {T_Grnt19b}
> }
>
> Which only gives a 20 fold decrease in the number of box tests (because
> there's only one bounding slab per row, instead of one per brick) and
> results in a 5 fold speed increase.
>
> 4. for real speed (and coding simplicity) use a #while loop to place
> each individual brick, and difference the arch cutouts from each brick.
> That way you get a bounding slab for each brick.
> You might think that there would be an overhead from performing lots of
> unnecessary differences, but you're actually already telling POV to do
> all those difference operations anyway, they're just buried inside the
> unions.
>
> --
> Mike Williams
> Gentleman of Leisure
Post a reply to this message
|
|
net>