well, i've worked on the gear code of mine much more... i've added a
bunch of features, and made it much quicker... i've also made it so you
can either use metric or imperial(or both for that matter), though this
doesn't do anything to the gears themselves.

It now uses meshes, which has sped up the process amazingly, but i've
noticed a little bit of dark spot problems... not sure why...

It does have one problem... i think it triggers a problem in povray
every now and then... in one function it doesn't except a period
operator (.u) on one thing, asking instead for a '(' for some reason...
it doesn't come up all the time, and only does when making gears with
fewer than 100 teeth... very strange... the smalltest.pov triggers it
alot of the time as it's set in the package.

Sorry 'bout the size... it seems to have grown quite a bit with all the
added things.

There's a full help part at the begining that should explain things, and
the updated version of the geartest.pov file, as well a small test pov
file.

Have fun with it, eh,
     the Loial Raven

Post a reply to this message

Attachments:
Download 'gears.zip' (10 KB)

Eeek, my mistake... there is an error in the code in the
gear_tooth_base_style = 1, or the bezier tooth base part...

um, i'll have it working problerly in a little bit hopefully...

sorry for blamming others, at first it was intermittent, i'll track it down.

Post a reply to this message

Loial Raven wrote:

> Eeek, my mistake... there is an error in the code in the
> gear_tooth_base_style = 1, or the bezier tooth base part...
>
> um, i'll have it working problerly in a little bit hopefully...
>
> sorry for blamming others, at first it was intermittent, i'll track it down.

ok... fixed... i think it is accually a problem with povray after all... the
fix was very strange...
pretty much all i did was instead of handing a macro a 2d vector straight from
the output of another macro, i handed it a 2d vector of the .u and .v portions
of the other macro's output.
    make_3d_point(bezier_value(_bezier_points, i*step))
     became:

make_3d_point(<bezier_value(_bezier_points,i*step).u,bezier_value(_bezier_points,i*step).v>)

which is extreamly strange since the make_3d_point uses the .u and .v parts
just as the above line does...
why does this make a difference?

well, hope it works now compleatly...
     the Loial Raven

Post a reply to this message

Attachments:
Download 'us-ascii' (26 KB)