|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 18-1-2016 8:08, Ger wrote:
> Btw, Pietje Puk is my alter ego :)
>
LOL (strictly for Dutch)
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ger <No.### [at] ThankYou> wrote:
> clipka wrote:
>
> > Am 17.01.2016 um 23:43 schrieb Ger:
> >
> >> Persistence of Vision(tm) Ray Tracer Version
> >> 3.7.1-alpha.7695039.unofficial
> >
> > Uh... that's 17 months old. Ever thought of trying a newer version?
>
> I have thought of it, but somehow never got around to it.
>
> Okay, got the latest? stable version
> built it, and guess what. It doesn't accept the -CC option
....
> It's the first version with the -CC option (no povstatefile) that I
> requested.
Dang, I was just about to ask what the "-CC" option is... do remember now.
Send a few round tuits my way and I'll have a look at both issues.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ger <No.### [at] ThankYou> wrote:
> Ger wrote:
>
> Forgot the version info
>
> Persistence of Vision(tm) Ray Tracer Version 3.7.0.unofficial (g++ 4.8 @
Ah, okay... THAT is NOT the lastest version, so no surprise about the "-CC"
option.
You want the "master" branch, not anything else. Looks like you downloaded the
"stable" branch, or the only official release. Which boils down to the same.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> There is no line 169
I guessed it doesn't means line 169 on data.inc, but on test.pov...
that is, on the ParseCenterOfMass macro.
After some tests making changes to that macro, the errors seemed to
suggest that sometimes data.inc was not fully written when it was
included in that macro.
So I tried moving the call to include data.inc outside the macro, and
worked just fine. BTW, judging by the line 162 seems you already tried that?
--
jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> So I tried moving the call to include data.inc outside the macro, and
> worked just fine. BTW, judging by the line 162 seems you already tried
> that?
Sorry, I see now that indeed you tried, and that was the original
question: why it works outside the macro but not inside.
Anyhow, I did a test putting the macro in a separate include file,
and now at least the error message isn't random anymore: it's always
"Attempt to access uninitialized array element" on this line:
#declare CFS[Count] = CFS[Count-1];
But as data.inc is included and has valid #declares, that cannot be
the real reason...
????
--
jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jaime Vives Piqueres wrote:
> Sorry, I see now that indeed you tried, and that was the original
> question: why it works outside the macro but not inside.
Correct.
>
> Anyhow, I did a test putting the macro in a separate include file,
> and now at least the error message isn't random anymore: it's always
> "Attempt to access uninitialized array element" on this line:
That's the error I started out with.
>
> #declare CFS[Count] = CFS[Count-1];
>
> But as data.inc is included and has valid #declares, that cannot be
> the real reason...
>
That's how I started out. I like certain things kept together in separate
include files, and since I don't always use the CenterOfMass calculations
it's a perfect candidate for the #if(CenterOfMass) clause.
>
> --
> jaime
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka wrote:
>> It's the first version with the -CC option (no povstatefile) that I
>> requested.
>
> Dang, I was just about to ask what the "-CC" option is... do remember now.
> Send a few round tuits my way and I'll have a look at both issues.
A whole bag of tuits is on the way, but you don't need them for the -CC
option thingy. Only for the #include thingy. So you may have some spare left
over that you can use for other stuff.
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot wrote:
> On 18-1-2016 8:08, Ger wrote:
>
>> Btw, Pietje Puk is my alter ego :)
>>
>
> LOL (strictly for Dutch)
>
What can I say? :)
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well... I'm puzzled. After some more tests, my only conclusion is that
the #include inside the macro sometimes fails to load correctly the
included file contents, leaving there "unparseable" code.
--
jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jaime Vives Piqueres wrote:
> Well... I'm puzzled. After some more tests, my only conclusion is that
> the #include inside the macro sometimes fails to load correctly the
> included file contents, leaving there "unparseable" code.
>
> --
> jaime
I have tried it in every possible way I can come up with and what I have
found is that povray sometimes chokes on reading data while inside a #macro.
Which indicates to me that povray does not handle #macros correctly. Another
indicator to that is that shortly before it crashes the memory usage goes up
strongly.
--
Ger
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |