Hi everyone

this is my first contribution here.
I'm running the 64bit beta 29 on Windows Vista x64. Intel quadcore CPU, 4GB RAM.

I'm trying to render a rather long sequence of images with radiosity with the
built-in queue feature. The first scene renders problem-freely, but the
subsequent ones in the queue fail with an "unknown internal error".

Instead of the official queue I also tried to use a batch script to call POV-Ray
and render each image one after the other. Again, the first image is output
correctly, but right after that, an error message pops up saying that an
unhandled exception occurred and prompting me to save a memory dump to disk.
That wouldn't be a problem if the batch loop weren't interrupted by this user
interaction demand, but this obviously prevents an automated rendering.

So I came to the beta page and found that this memory dump feature only exists
since beta 16. Is there a page where I can download previous beta versions? I'd
like to have a shot at beta 15.

I don't observe this problem when radiosity is deactivated.

The reason why I can't use 3.6.1 is that it lacks full parallelism. Rendering
the whole movie would take much too long in serial processing.

Any help ist highly appreciated!

Roman

Post a reply to this message

"Roman" <nomail@nomail> wrote:
Hm... having embarked on the quest of fixing some issues in the 3.7 radiosity, I
must confess I'm less interested in solving your immediate problems, but rather
in learning what's wrong with the .29 radiosity that might cause the crash in
the first place...

So can you narrow down the crash to a particular scene (or maybe even particular
aspects of it), and post that one in one of the binaries newsgroups, so I can
check that?

> Any help ist highly appreciated!

Same goes for me :)

Post a reply to this message

"clipka" <nomail@nomail> wrote:
> "Roman" <nomail@nomail> wrote:
> Hm... having embarked on the quest of fixing some issues in the 3.7 radiosity, I
> must confess I'm less interested in solving your immediate problems, but rather
> in learning what's wrong with the .29 radiosity that might cause the crash in
> the first place...
>
> So can you narrow down the crash to a particular scene (or maybe even particular
> aspects of it), and post that one in one of the binaries newsgroups, so I can
> check that?
>
> > Any help ist highly appreciated!
>
> Same goes for me :)



Assuming there is a 3.7 test pvengine for download, what was used to compile it?

And what was used to compile 3.6?


Because what was used to compile 3.6 went against the laws of my computer,
I now have compiled mingw versions: 3.6, 3.6.1, 3.6.3 stereo/motion, and MegaPOV

were, or actually I don't, hence the questions.

(downloadable megapvengine had none of probs of 3.6, and my pv*.exe's look and
act perfectly like megapv. probably the same compiler was used, makes sense to
me)

Would like to know what to expect before running anything that might help with
your efforts.

Post a reply to this message

"alphaQuad" <alp### [at] earthlinknet> wrote:

>
> And what was used to compile 3.6?


Wait, (the winsrc was 3.6 and) the winexe was 3.6.1, if I remember, humpft its
not even here anymore to check that v#, but it didnt run right. how many people
just give up because of what is MS compiled? Now that I think more of it, you
guys are usin like MS 2007 whatever its called now?

Mingw all the way or we waste our time and everyone else's time!!!!!!!!!!!IMHO

Post a reply to this message

"alphaQuad" <alp### [at] earthlinknet> wrote:
> Assuming there is a 3.7 test pvengine for download,

There *is* in fact - the famous "beta 29" at the moment.

> what was used to compile it?

Depends on what platform you're talking about.

The official Windows 32-bit binary was compiled using MS Visual C++ 8 (i.e. the
C++ compiler in Visual Studio 2005).

The official Linux 64-bit binary was compiled using the Intel C++ compiler,
version 10.1. About the others I don't know.

> And what was used to compile 3.6?

Windows 32-bit: Something abbreviated "icl8" - whatever that means. I think it's
an Intel compiler as well.

Linux 32-bit: g++ 3.4.1.

Others: Dunno.

> Because what was used to compile 3.6 went against the laws of my computer,
> I now have compiled mingw versions: 3.6, 3.6.1, 3.6.3 stereo/motion, and MegaPOV

> were, or actually I don't, hence the questions.
>
> (downloadable megapvengine had none of probs of 3.6, and my pv*.exe's look and
> act perfectly like megapv. probably the same compiler was used, makes sense to
> me)

Nope, MegaPOV was compiled using MS Visual C++ 7 (which, IIRC is the C++
compiler in Visual Studio .NET 2003)

Post a reply to this message

"alphaQuad" <alp### [at] earthlinknet> wrote:
> how many people
> just give up because of what is MS compiled? Now that I think more of it, you
> guys are usin like MS 2007 whatever its called now?
>
> Mingw all the way or we waste our time and everyone else's time!!!!!!!!!!!IMHO

OMG - another religious zealot!

I bet you don't even have an idea of what you're talking about.

Post a reply to this message

"alphaQuad" <alp### [at] earthlinknet> wrote:
how many people
> just give up because of what is MS compiled? Now that I think more of it, you
> guys are usin like MS 2007 whatever its called now?

.... oh, and BTW - according to your report, it's the stuff compiled with Intel
C++ that crapped up, while the MS-compiled stuff runs fine.

See?

Post a reply to this message

"clipka" <nomail@nomail> wrote:
> "alphaQuad" <alp### [at] earthlinknet> wrote:
> > how many people
> > just give up because of what is MS compiled? Now that I think more of it, you
> > guys are usin like MS 2007 whatever its called now?
> >
> > Mingw all the way or we waste our time and everyone else's time!!!!!!!!!!!IMHO
>
> OMG - another religious zealot!
>
> I bet you don't even have an idea of what you're talking about.

yah its called a C++ standard to which MS cant stick. Sun microsystems sued and
won ten million (albeit a drop in the bucket) for niggin on Java contract.
Nothing "religious" about it. Its called reality. Denial changes nothing, get
out of it.

Post a reply to this message

"clipka" <nomail@nomail> wrote:
> "alphaQuad" <alp### [at] earthlinknet> wrote:
> > how many people
> > just give up because of what is MS compiled? Now that I think more of it, you
> > guys are usin like MS 2007 whatever its called now?
> >
> > Mingw all the way or we waste our time and everyone else's time!!!!!!!!!!!IMHO
>
> OMG - another religious zealot!
>
> I bet you don't even have an idea of what you're talking about.

one more thing. burnin bridges - real bright on your part.

Post a reply to this message

On Sat, 27 Dec 2008 16:32:38 EST, "alphaQuad" <alp### [at] earthlinknet>
wrote:

> to which MS cant stick

Do you know that cant and can't mean different things?
-- 

Regards
     Stephen

Post a reply to this message