 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
this might be an unusal question, but is there any possibility to run POVRAY
on the same scene using different parameters (e.g. antialiasing, viewport
extremly big files (>100Mb) which have to be rendered with different
options. It'd be really neat if there were an option that allows POVRAY to
cache the parsed .pov-file so it could be rendered several times using
different options.
kind regards
psy
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
psy_inf <nomail@nomail> wrote:
> this might be an unusal question, but is there any possibility to run POVRAY
> on the same scene using different parameters (e.g. antialiasing, viewport
> si?ze) without actually reparsing the file?
No.
In a future version of POV-Ray probably yes. Not yet.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warp" <war### [at] tag povrayorg> wrote in message
news:452e6a4a@news.povray.org...
> psy_inf <nomail@nomail> wrote:
>> this might be an unusal question, but is there any possibility to run
>> POVRAY
>> on the same scene using different parameters (e.g. antialiasing, viewport
>> si?ze) without actually reparsing the file?
>
> No.
>
> In a future version of POV-Ray probably yes. Not yet.
That's like... 15 years away..?
~Steve~
>
> --
> - Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
St. <dot### [at] dotcom> wrote:
> > In a future version of POV-Ray probably yes. Not yet.
> That's like... 15 years away..?
Not necessarily. The cleanup for SMP brings positive side-effects to the
core code.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warp" <war### [at] tagpovrayorg> wrote in message
news:452ee20f@news.povray.org...
> St. <dot### [at] dotcom> wrote:
> > > In a future version of POV-Ray probably yes. Not yet.
>
> > That's like... 15 years away..?
>
> Not necessarily. The cleanup for SMP brings positive side-effects to
the
> core code.
might not be the ideal place to ask, but
with all this cleaning of the code, is it still the POV-team's intention
to do a complete rewrite for POV-Ray 4 ? Or will it be some kind of
gradual rewrite? :)
cu!
--
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Zeger Knaepen wrote:
> "Warp" <war### [at] tagpovrayorg> wrote in message news:452ee20f@news.povray.org...
>> St. <dot### [at] dotcom> wrote:
>>>> In a future version of POV-Ray probably yes. Not yet.
>>> That's like... 15 years away..?
>> Not necessarily. The cleanup for SMP brings positive side-effects to the
>> core code.
>
> might not be the ideal place to ask, but
> with all this cleaning of the code, is it still the POV-team's intention to do a
complete rewrite for POV-Ray 4 ? Or will it be some kind of gradual rewrite? :)
The answer is another question: Does it matter much? It is in the future, so
nothing is set in stone anyway.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:452ff377$1@news.povray.org...
> The answer is another question: Does it matter much? It is in the
future, so
> nothing is set in stone anyway.
it doesn't really matter to me, no. As long as I can keep on tracing,
I'm happy :)
I was just wondering
cu!
--
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Zeger Knaepen wrote:
>
> might not be the ideal place to ask, but
> with all this cleaning of the code, is it still the POV-team's intention to do a
complete rewrite for POV-Ray 4 ? Or will it be some kind of gradual rewrite? :)
To make sure this does not get misunderstood - nothing has changed about
the intention that the next major revision of POV-Ray ("POV-Ray 4.0") is
planned to be released under a new, OSI-compatible license.
Despite the major changes POV-Ray 3.7 is quite closely based on the 3.6
codebase in a lot of things - which isn't a bad things since this is
mostly well tested and reliable code. This also ensures a high level of
backwards compatibility.
Christoph
--
POV-Ray tutorials, include files, Landscape of the week:
http://www.imagico.de/ (Last updated 20 Aug. 2006)
MegaPOV with mechanics simulation: http://megapov.inetart.net/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
psy_inf wrote:
> this might be an unusal question, but is there any possibility to run POVRAY
> on the same scene using different parameters (e.g. antialiasing, viewport
> extremly big files (>100Mb) which have to be rendered with different
> options. It'd be really neat if there were an option that allows POVRAY to
> cache the parsed .pov-file so it could be rendered several times using
> different options.
This is internally supported in 3.7 but not tested and most likely will not
be implemented in the released version (i.e. the support is there* but we
would not necessarily enable it via the user interface or command-line since
it would require more testing and possibly delay the final release).
Once the source code is released it's possible** someone will add it.
-- Chris
* 3.7 is based on a 'scene/view' model where the act of parsing a scene is
completely separate from rendering it (via a view). the view determines
the camera location and type, output resolution, AA, and so forth.
** possible == 'next to certain' in this case IMO.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
