Hajo,
I have large *.inc file with definition of my objects.
Almost 90% time of rendering in every frame takes parsing of data.
However data does not change during rendering.
Is it possible to read data only once ?

thanks in advance

--
Gawel
-------------------------------
Pierwszy ³yk z pucharu nauk przyrodniczych czyni ateist±, ale na dnie
pucharu czeka Bóg.
Werner Heisenberg

Post a reply to this message

> Hajo,
> I have large *.inc file with definition of my objects.
> Almost 90% time of rendering in every frame takes parsing of data.
> However data does not change during rendering.
> Is it possible to read data only once ?
>
> thanks in advance

Depends. If your include-file actually generates the objects via some SDL,
there might be possibilities to write the finished objects to a file and
load that, instead of parsing the objects for every frame. If the parsing is
needed to simply load large meshes or CSG objects, and the include doesn't
generate the objects via Macros or such, well, then there's not much you can
do about it. POV-Ray, though with animation support, wasn't programmed to be
an animation tool. It was programmed to render a single frame, via "clock"
it just automates rendering one frame after another.

Regards,
Tim

-- 
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>

Post a reply to this message

Wasn't it Gawel who wrote:
>Hajo,
>I have large *.inc file with definition of my objects.
>Almost 90% time of rendering in every frame takes parsing of data.
>However data does not change during rendering.
>Is it possible to read data only once ?

No, but in many cases it's possible to speed things up by saving the
results of any complicated calculations that you are performing during
the parsing. The parser tends to be pretty quick at processing raw
objects, and the things that tend to take up the parsing time are often
the complicated calculations that determine the positioning of those
objects. So save the calculated data from the first frame by #write-ing
it to a file and then just #read it back for the other frames.

The other thing that's likely to take huge amounts of parsing time is
the loading of tens of megabytes of mesh data, and there's no way to
avoid the parsing time for that.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

> The other thing that's likely to take huge amounts of parsing time is
> the loading of tens of megabytes of mesh data, and there's no way to
> avoid the parsing time for that.

That's the case. I have large meshes :(.
I found that MegaPov in version 0.7 have
persitent variables and that's what I need but
I can't find this version (0.7).
Below links seems not to work :(
http://www.nathan.kopp.com/download.htm

Do you know where I can find  MegaPov version 0.7?

thanks in advance

Gawel

Post a reply to this message

In article <40bb62fa$1@news.povray.org> , "Gawel" <gaw### [at] SPAMIKgazetapl>
wrote:

> Where can I find this soft ?
> Below links seems not to work :(
> http://www.nathan.kopp.com/download.htm

The link works just fine.  This is not surprising either because it points
to the same server as you are posting to, and as you can post here,
povray.org obviously is not down :-)  You may want to check your web browser
configuration...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Well, MegaPov 0.7 is not enough becasue it needs PovRay 3.1 and
this version does not support mesh2 :(. Any other idea ?

Gawel

Post a reply to this message

In article <40bb7f44@news.povray.org> , "Gawel" <gaw### [at] SPAMIKgazetapl> 
wrote:

> Well, MegaPov 0.7 is not enough becasue it needs PovRay 3.1 and
> this version does not support mesh2 :(. Any other idea ?

Argh!  It of course needs the rest of the files that come with POV-Ray!  It
is a POV-Ray patch collection, and as such it obviously provides you with a
new POV-Ray executable which you find in the archive you are supposed to
download and which then tells you how to replace the POV-Ray executable from
the official version...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

"Gawel" <gaw### [at] SPAMIKgazetapl> a écrit dans le message de
news:40bb7f44@news.povray.org...
> Well, MegaPov 0.7 is not enough becasue it needs PovRay 3.1 and
> this version does not support mesh2 :(. Any other idea ?

Actually mesh2 was introduced in the Megapov line of patches, so it's
supported. However, you will have to add "#version unofficial Megapov 0.7"
on the top of each mesh file (not just once in the scene file), otherwise it
won't work.

G.


-- 

**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message

> > Well, MegaPov 0.7 is not enough becasue it needs PovRay 3.1 and
> > this version does not support mesh2 :(. Any other idea ?
>
> Argh!  It of course needs the rest of the files that come with POV-Ray!
It
> is a POV-Ray patch collection, and as such it obviously provides you with
a
> new POV-Ray executable which you find in the archive you are supposed to
> download and which then tells you how to replace the POV-Ray executable
from
> the official version...

I do not understand you post. Especially your annoyance...

I wrote that I have MegaPov 0.7 and Povray 3.1.
What's more I thought that combintion of those both application does NOT
support mesh2 object.
I also was not able to run MegaPov 0.7 with Povray 3.5. Therefore I did not
see any possibility to solve
my problem. Fortunately Gilles Tran gave my an advice and now I know how to
render mesh2 with MegaPov 0.7
and PovRay 3.1. That's all.


Gawel

Post a reply to this message

> Actually mesh2 was introduced in the Megapov line of patches, so it's
> supported. However, you will have to add "#version unofficial Megapov 0.7"
> on the top of each mesh file (not just once in the scene file), otherwise
it
> won't work.

Thanks very much. It solves my problem, although is pity that is does not
take advanatege of
newest version of PovRay.

--
Gawel
-------------------------------
Pierwszy ³yk z pucharu nauk przyrodniczych czyni ateist±, ale na dnie
pucharu czeka Bóg.
Werner Heisenberg

Post a reply to this message

On Tue, 1 Jun 2004 21:24:24 +0200, "Gawel" <gaw### [at] SPAMIKgazetapl> wrote:
> I do not understand you post. Especially your annoyance...

This is a hard time for all POV-Team members. Please be forgiving for any side
effect of completing 3.6. Note, it is reasonably to expect that somebody who
downloaded some application has readed homepage of this application, in
particular key features where extended mesh syntax is listed.

Pozdrawiam, ABX

Post a reply to this message

In article <40bcd7f2$1@news.povray.org> , "Gawel" <gaw### [at] SPAMIKgazetapl>
wrote:

> I also was not able to run MegaPov 0.7 with Povray 3.5. Therefore I did not
> see any possibility to solve
> my problem. Fortunately Gilles Tran gave my an advice and now I know how to
> render mesh2 with MegaPov 0.7
> and PovRay 3.1. That's all.

You still have not understood at all: MegaPOV just needs the support files
from POV-Ray 3.1.  It does in no way run together with POV-Ray 3.1, it is a
full replacement!  As such, it is completely irrelevant what POV-Ray 3.1 can
and cannot do as MegaPOV replaces it.  You don't run MegaPOV 0.7 together
with POV-Ray 3.1!

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <hlmpb058jfet4l9l0t6hpbrpus0fdp3asj@4ax.com> , ABX 
<abx### [at] abxartpl>  wrote:

> On Tue, 1 Jun 2004 21:24:24 +0200, "Gawel" <gaw### [at] SPAMIKgazetapl> wrote:
>> I do not understand you post. Especially your annoyance...
>
> This is a hard time for all POV-Team members. Please be forgiving for any side
> effect of completing 3.6. Note, it is reasonably to expect that somebody who
> downloaded some application has readed homepage of this application, in
> particular key features where extended mesh syntax is listed.

No, that is not the reason at all.  It is the fundamental misunderstanding
that MegaPOV somehow runs ontop of POV-Ray 3.1 as seen in the latest post
with the statement "although is pity that is does not take advantage of
newest version of POV-Ray" and "now I know how to render mesh2 with MegaPov
0.7 and POV-Ray 3.1."  Apparently this person has not understood what
MegaPOV is at all (and what an executable is for that matter, as I explained
it using that term), and this will sooner or later result in more serious
misconceptions and problems.  Maybe communication in English is insufficient
to help this person understand the misconception...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

> You still have not understood at all: MegaPOV just needs the support files
> from POV-Ray 3.1.  It does in no way run together with POV-Ray 3.1, it is
a
> full replacement!  As such, it is completely irrelevant what POV-Ray 3.1
can
> and cannot do as MegaPOV replaces it.  You don't run MegaPOV 0.7 together
> with POV-Ray 3.1!

Ok, I found the place of misunderstanding. There is in documentaton that
during
installation MegaPov 0.7 must be copied to folder where Povray 3.1 exists.
It is not written that ONLY dlls are requaired. Now all is clear.
And sorry for my thoughtlessness.  Nowodays I sleep not to much...

thanks again

--
Gawel
-------------------------------
Pierwszy lyk z pucharu nauk przyrodniczych czyni ateista, ale na dnie
pucharu czeka Bóg.
Werner Heisenberg

Post a reply to this message

> This is a hard time for all POV-Team members. Please be forgiving for any
side
> effect of completing 3.6. Note, it is reasonably to expect that somebody
who
> downloaded some application has readed homepage of this application, in
> particular key features where extended mesh syntax is listed.
>

All those bad things occured because I did not understand idea of MegaPov.
Now all should be easier and not so annoying for others ;)

Gawel

Post a reply to this message

"Gawel" <gaw### [at] SPAMIKgazetapl> wrote:
> Hajo,
> I have large *.inc file with definition of my objects.
> Almost 90% time of rendering in every frame takes parsing of data.
> However data does not change during rendering.
> Is it possible to read data only once ?
>
> thanks in advance
>
> --
> Gawel
> -------------------------------
> Pierwszy ³yk z pucharu nauk przyrodniczych czyni ateist±, ale na dnie
> pucharu czeka Bóg.
> Werner Heisenberg

Hi,

I would like to know how you managed to Parse only once when rendering an
animation.

Thanks in advance,

Ikatchu

Post a reply to this message

In article <web.40d83e39cb1a83faa14d5b880@news.povray.org>, nomail@nomail 
says...
> "Gawel" <gaw### [at] SPAMIKgazetapl> wrote:
> > Hajo,
> > I have large *.inc file with definition of my objects.
> > Almost 90% time of rendering in every frame takes parsing of data.
> > However data does not change during rendering.
> > Is it possible to read data only once ?
> >
> > thanks in advance
> >
> > --
> > Gawel
> > -------------------------------
> > Pierwszy ³yk z pucharu nauk przyrodniczych czyni ateist±, ale na dnie
> > pucharu czeka Bóg.
> > Werner Heisenberg
> 
> Hi,
> 
> I would like to know how you managed to Parse only once when rendering an
> animation.
> 
> Thanks in advance,
> 

Rewrite a version that is smart enough to do so? Though how practical it 
would be.. Seriously though, there is no way to do this in the current 
version. It needs to rebuild the location of every object in every frame, 
including all the depth based trees and other things it needs to render 
correctly. I suspect, though have no real clue, that redesigning it to 
render once and run may be non-trivial.

-- 
void main () {
  If Schrödingers_cat is alive  
    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message