On Wed, 8 Jul 1998 21:46:05 -0400, "Justin Rogers" <dig### [at] 3nnet>
wrote:

>I don't want a UNIX binary..  I want something to run Winsock TCP/IP
>distributed rendering...  Maybe I didn't clarify myself enough.  And at
>current the POV Team has no thoughts of implementing an InetPOV...  So you
>are incorrect in assuming I would be wasting my time.

Did I say Unix binary?  Nope, guess not.  The Unix source just
compiles better for a Win32 console-mode executable, is all, but if
you want to spend time hacking out the display support from the DOS
version, I won't stop you.  Never let the advice of someone who's been
there discourage you from reinventing the square wheel, I always say.

And the POV-Team has stated on this very server that they plan to
implement internet distributed rendering in POV 4.0.  They've had a
well-known port registered with IANA since the days of POV 2.0.

>There is
>always someone with a workable idea.  Try to support such people instead of
>discouraging creativity.  You'll find it is much more beneficial.

I do.  But I haven't seen any such people lately.  Have it your way,
though.  I certainly can't stop you.

>Quit talking about crappy OSes...  Windows NT has no problem thread
>switching.  And the only reason 3DSMax and Bryce3D are so quick is because
>they are multithreaded...  Single-Threaded versions are clearly and
>decisively slower in the rendering process.  Also check Ray Dream Studio...

Sorry, NT _is_ my primary OS and I'm still telling you that
multithreading rendering on a single processor is a waste of time, and
that thread switching is inefficient.  Those other raytracers might be
multithreaded, but it's a matter of the UI being in one thread and the
renderer in another, just like in POV.  Again, if you choose to
believe your own fantasy version of what the world is like, I can't
stop you.

>Again your being narrow minded...  Why does POV need to know when a file has
>been changed...  As long as some means is enabled to save a file.  

Duh... so it can ask you if you want to save before it exits?

>Not to mention an entirely new editor can
>be written and put in place of the EditDll.dll.  This is the method I plan
>on implementing...  This way you can swap out editors just like a
>GUI-Extension.  All you have to do is rename the EditDll.dll file, place the
>new one in place and continue on.  Not to mention a rewrite of this dll to
>support ActiveX and OLE would be a definite enhancement.

This method has been proposed before in this group. In fact, it was I
who proposed it.  But if you read the new POVLEGAL you'll see that
ActiveX and OLE interfaces are out of the question, as is extending
the POV<->EditDLL interface.  In any case, the POV team is completely
revamping the editor for 3.1, so let's see what's in the final version
before we continue complaining about it.

>    It sure can... I have added support for all of the command line options
>and all of the command line options can be contained in an ini file.  When
>you create a new POV project it automatically creates a .pov file and a .ini
>file for you.  Then all you have to do is edit the .ini file and hit the
>compile button.  Next thing you know your left with an onscreen POV image or
>it has been shelled to disk and POV will auto-exit.  Not to mention it has
>support for opening multiple versions of POV to do multithreaded frames.

Could you post it somewhere?  If you lack for FTP space, Twyst might
be able to help you out.

Post a reply to this message