If anyone is interested, I have fixed the wireframe cone object so that
it now does truncated cones, and have added a +q1 spitch to views.inc to
make for faster rendering of the wireframe views.Please keep in mind
that it uses the MegaPOV ini_option keyword, which may go bye bye soon.
I have not had time for a total rewrite, which is about due, but these
imporvements are better than nothing.

Post a reply to this message

Attachments:
Download 'wire cone.zip' (2 KB)

"Dave Dunn" <poi### [at] aolcom> wrote in message
news:3B748900.BC783503@aol.com...
> If anyone is interested, I have fixed the wireframe cone object so that
> it now does truncated cones, and have added a +q1 spitch to views.inc to
> make for faster rendering of the wireframe views.Please keep in mind
> that it uses the MegaPOV ini_option keyword, which may go bye bye soon.
> I have not had time for a total rewrite, which is about due, but these
> imporvements are better than nothing.
>
Thanks,

Maybe you could take a look at what ABX has done as well at
http://news.povray.org/povray.binaries.utilities/15804/?tsor=3
and get the best of both worlds =)

- Nekar

Post a reply to this message

> Maybe you could take a look at what ABX has done as well at
> http://news.povray.org/povray.binaries.utilities/15804/?tsor=3
> and get the best of both worlds =)

Funny you should mention it. The modeling.inc file was what sparked the
discussion on AOL that led to the creation of POVGUI. The approach, as you can
see, is a bit different, in that the modeling.inc file seems to try and
capture all views at once in a very small file, and our idea was to
concentrate on one view at a time, and pack it with features (wireframes,
proxies, etc.). One of the great things about POV-Ray, as this illustrates, is
that there is always more than one way to do the same thing. (Note to ABX:
maybe a hybrid is possible?). BTW, I have rewritten the objects and lights as
macros, and they are much easier to handle. Look for an update soon.

Post a reply to this message