POV-Ray : Newsgroups : povray.programming : Native TAR archive support in POV : Re: Native TAR archive support in POV Server Time
29 Jul 2024 06:19:23 EDT (-0400)
  Re: Native TAR archive support in POV  
From: Nigel Stewart
Date: 28 Mar 1999 00:26:41
Message: <922598605.1987625978@news.povray.org>
There is now a web-page describing "Imp Pov", a povray 3.1
compilation with a few extra features for network rendering.

http://www.imp.org/members/tech/rcast/rcast.html

Binaries for Win32 and Linux are available.

Features:

     * Passive render-farm mode "+N" for rendering farming
       The network rendering mode waits for configuration files in INI
       format to be placed in the incoming directory. Outputs are placed
       in the outgoing directory.
     * TAR file as read-only file-system
       Packing scene files into a TAR archive allows long filenames, and
       case sensitive filenames across every platform. It also simplifies
       scene distribution, and allows modules to be packaged and
       distributed conveniently.
     * Automatic scene dependency reporting
       Pov-ray will report the set of files required to render a scene.
       Ultimately, this feature will be developed to provide render
       farmers with the minimal set of files required for a each frame of
       animation.
    * Command-line interface
       No user interface is included for the sake of portability. It
       should be simple to layer a GUI on top of the network rendering
       mode, by manipulating the file queues and writing some state
       information to a file from povray.
     * Different directory searching policy
       Currently, pov requires every directory to be included in the
       library search path in order to find include files. IMP POV
       implements a 'relative to current file' search, so that files in
       the same directory as the current one are found first. This means
       you can include a module using an absolute path: #include
       "galaxy/galaxy.inc" and files it depends on this will be expected
       in the galaxy directory.
       This reduces the amount of library configuration, and also reduces
       the chances that included filenames will collide. (For example, a
       local "colors.inc" vs the global "colors.inc")
       


-- 
Nigel Stewart (nig### [at] eisanetau)  http://www.eisa.net.au/~nigels/
Postgrad Research Student, RMIT University, Melbourne, Australia
All extremists should be taken out and shot.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.