Hi!
I was trying to use persistent variables in an animation sequence using
MegaPov 1.0. I was using the same syntax as in MegaPov 0.7. i.e. use
Persistent_Animation=yes in the INI file and then using label and modify
inside the script. This is producing all kinds of errors. I was wondering
if there is a change of syntax in MegaPov 1.0 or persistent variables
supported at all. Can anybody throw light on this please. It will be of a
great help to me.

Sup

ps: Initially I posted it in the animation forum, but since this is more
related to megapov than animation, I thought 'would be appropriate to post
it here.

Post a reply to this message

On Wed,  8 Oct 2003 03:07:01 EDT, "sups" <sbh### [at] lycoscom> wrote:
> ps: Initially I posted it in the animation forum, but since this is more
> related to megapov than animation, I thought 'would be appropriate to post
> it here.

Thanks, Sup, for using this group now, but... is there anything wrong with the
answer you already received in povray.animation group? I quoted there sentence
we wrote at begining of http://megapov.inetart.net/manual/news.html where you
can find all features already reimplemented. The only other help I can give
you at this moment is workaround this feature with importing/exporting
variables through external file. Is this sufficient?

ABX

Post a reply to this message

Hi ABX!

Thank you for both your replies. From your previous reply it was clear that
persistent variables may not have made it to MP1.0. But in the manuals of
MP1.0, nowhere it has been explicitly mentioned. Therefore I had the
slightest hope that this feature may be accesible in some other way. It
would be really nice to get this feature back since my code is not
compatible with MP0.7. I have tried the file I/O feature. Due to the very
large size of the file (476 Kb), reading seems extremely slow, almost same
time as generating the data. e.g. My parsing time is 5 min, rendering time
30 sec. I guess I have to wait till this feature gets implemented.

thanks again
Sup

ABX wrote:
>On Wed,  8 Oct 2003 03:07:01 EDT, "sups" <sbh### [at] lycoscom> wrote:
>> ps: Initially I posted it in the animation forum, but since this is more
>> related to megapov than animation, I thought 'would be appropriate to post
>> it here.
>
>Thanks, Sup, for using this group now, but... is there anything wrong with the
>answer you already received in povray.animation group? I quoted there sentence
>we wrote at begining of http://megapov.inetart.net/manual/news.html where you
>can find all features already reimplemented. The only other help I can give
>you at this moment is workaround this feature with importing/exporting
>variables through external file. Is this sufficient?
>
>ABX
>

Post a reply to this message

On Wed,  8 Oct 2003 13:27:52 EDT, "sups" <sbh### [at] lycoscom> wrote:
> I have tried the file I/O feature. Due to the very
> large size of the file (476 Kb), reading seems extremely slow, almost same
> time as generating the data. e.g.

What method do you use to perform writing/reading ?

Do you use #write #read ? Perhaps reading through #include would be faster ?
Perhaps writing it into array would offer later fastest #include? Perhaps
other trick could be possible as well - for example you could write data into
ascii image and then read it through evaluation of colors on pigment. I
suggest to seeking for workarounds temporary as long as persistent variables
are not available.

ABX

Post a reply to this message

sups wrote:
> Hi ABX!
> 
> Thank you for both your replies. From your previous reply it was clear that
> persistent variables may not have made it to MP1.0. But in the manuals of
> MP1.0, nowhere it has been explicitly mentioned. Therefore I had the
> slightest hope that this feature may be accesible in some other way. It
> would be really nice to get this feature back since my code is not
> compatible with MP0.7.

It is not very likely that this will happen any time soon.  The 
persistence of variables patch was somewhat ugly and Nathan was probably 
the only one who really understood it.

I would also prefer a different syntax for such a patch.  Like for 
example a new #persistent directive which works like #declare and #local 
but stores the data differently so it is not cleared after each frame.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 2 Sep. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message

Right now, I have used the #read and it seems too slow. I will try #include
and let you know what happens. I also agree with Chris on the syntax of
persistent variables.

thank you
Sup

ABX wrote:
>On Wed,  8 Oct 2003 13:27:52 EDT, "sups" <sbh### [at] lycoscom> wrote:
>> I have tried the file I/O feature. Due to the very
>> large size of the file (476 Kb), reading seems extremely slow, almost same
>> time as generating the data. e.g.
>
>What method do you use to perform writing/reading ?
>
>Do you use #write #read ? Perhaps reading through #include would be faster ?
>Perhaps writing it into array would offer later fastest #include? Perhaps
>other trick could be possible as well - for example you could write data into
>ascii image and then read it through evaluation of colors on pigment. I
>suggest to seeking for workarounds temporary as long as persistent variables
>are not available.
>
>ABX
>

Post a reply to this message

in news:jtv### [at] tritonschunteretctu-bsde Christoph Hormann 
wrote:

> I would also prefer a different syntax for such a patch

Just an idea, how about something inspired by Pythons pickle and shelve:
http://www.python.org/doc/current/lib/module-pickle.html
http://www.python.org/doc/current/lib/module-shelve.html

You could make not just variables persistent but whole objects or scene 
sections.

Ingo

Post a reply to this message

#declare_persistant = XXXX;

This seems like the best way. This would work for objects as well I would
assume. Just my thoughts.

"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:jtv### [at] tritonschunteretctu-bsde...
> sups wrote:
> > Hi ABX!
> >
> > Thank you for both your replies. From your previous reply it was clear
that
> > persistent variables may not have made it to MP1.0. But in the manuals
of
> > MP1.0, nowhere it has been explicitly mentioned. Therefore I had the
> > slightest hope that this feature may be accesible in some other way. It
> > would be really nice to get this feature back since my code is not
> > compatible with MP0.7.
>
> It is not very likely that this will happen any time soon.  The
> persistence of variables patch was somewhat ugly and Nathan was probably
> the only one who really understood it.
>
> I would also prefer a different syntax for such a patch.  Like for
> example a new #persistent directive which works like #declare and #local
> but stores the data differently so it is not cleared after each frame.
>
> Christoph
>
> --
> POV-Ray tutorials, include files, Sim-POV,
> HCR-Edit and more: http://www.tu-bs.de/~y0013390/
> Last updated 2 Sep. 2003 _____./\/^>_*_<^\/\.______
>

Post a reply to this message

In article <3f855704$1@news.povray.org>,
 "Micheal \(Mike\) Williams" <mic### [at] quixnetnet> wrote:

> #declare_persistant = XXXX;
> 
> This seems like the best way. This would work for objects as well I would
> assume. Just my thoughts.

Simply #persistant should be enough, and consistent with the existing 
#declare, #local keywords. And it should be possible without too much 
work for anything that can be declared...but I haven't really looked at 
the changes that would need to be made.

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/

Post a reply to this message

On Thu, 09 Oct 2003 13:07:08 -0400, Christopher James Huff
<cja### [at] earthlinknet> wrote:
> Simply #persistant should be enough, and consistent with the existing 
> #declare, #local keywords. And it should be possible without too much 
> work for anything that can be declared...but I haven't really looked at 
> the changes that would need to be made.

I suppose it will be more difficult at least because of functions existence.

#declare C=function{pigment{object{sphere{0,1}rgb 0 rgb 1}}}
#persistent D=function{C(x,y,z)+1}

BTW I would prefer #persist more than #persistent

ABX

Post a reply to this message