Seems quite a ridiculous claim, yet . . .

As I was trying to work out a few isosurfaces last night, I repeatedly noticed a
curious, and troubling phenomenon:

Sometimes when I made changes to my code and re-rendered, POV-Ray did not take
the changes into account, and just re-rendered the scene that I had before I
made the changes.

If I rendered another scene or (intentionally) triggered an error, it seems that
something got reset, and POV-Ray actually noticed (parsed) the new code and
rendered the expected changes.

Has anyone run into anything like this?

I will have to post the (short) scene later and see if I can figure out a
reliable, repeatable way to get it to happen.

I'm running 3.8, and am probably using a S***-Ton of memory

My brain is like an internet browser. I have 17 tabs open, 3 of them are frozen
"and I have no idea where the music is coming from. . ."

Except that I'm sure I have 5 browser windows with more than 17 tabs....

- BW

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> Seems quite a ridiculous claim, yet . . .
>
> As I was trying to work out a few isosurfaces last night, I repeatedly noticed a
> curious, and troubling phenomenon:
>
> Sometimes when I made changes to my code and re-rendered, POV-Ray did not take
> the changes into account, and just re-rendered the scene that I had before I
> made the changes.
>
> If I rendered another scene or (intentionally) triggered an error, it seems that
> something got reset, and POV-Ray actually noticed (parsed) the new code and
> rendered the expected changes.
>
> Has anyone run into anything like this?
>
> I will have to post the (short) scene later and see if I can figure out a
> reliable, repeatable way to get it to happen.
>
> I'm running 3.8, and am probably using a S***-Ton of memory
>
> My brain is like an internet browser. I have 17 tabs open, 3 of them are frozen
> "and I have no idea where the music is coming from. . ."
>
> Except that I'm sure I have 5 browser windows with more than 17 tabs....
>
> - BW

I have! Using 3.7 64 bit for windows. I always set the auto save on  and some
times POV just doesn't save anything but the save icon gets turned off. After I
render a few times and nothing changes I manually save and then things start to
work normally. It doesn't happen often, But it can be annoying.

Have Fun!

Post a reply to this message

"Leroy" <whe### [at] gmailcom> wrote:

> I have! Using 3.7 64 bit for windows. I always set the auto save on  and some
> times POV just doesn't save anything but the save icon gets turned off. After I
> render a few times and nothing changes I manually save and then things start to
> work normally. It doesn't happen often, But it can be annoying.

Excellent (or not).
I thought maybe it was me since no one else has ever mentioned it.

Might just be a 3.8 or a Winblo$ thing.

Probably going to be a slippery bug to track down.

- BW

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> Seems quite a ridiculous claim, yet . . .
>
> Sometimes when I made changes to my code and re-rendered, POV-Ray did not take
> the changes into account, and just re-rendered the scene that I had before I
> made the changes.
>

Yep, the same thing happens to me every now and then, running Windows 10 and
v3.8 beta 1. (I sometimes switch to official 3.7.0, but I haven't really taken
notice as to the quirk occuring in both versions.)  I don't have auto-save on,
I just use the GUI's RUN button after I've made a code change. As usual, most
times a little window comes up asking me if I really want to save the change
before rendering-- but sometimes that window doesn't appear, and the render
proceeds anyway...without the saved change.

I finally realized that I needed to hit the SAVE button at the top of the GUI
when this happens, to 'force' a save.

BTW, I always seem to have the maximum number of tabs open in POV-ray; I wonder
if that has anything to do with it.

Another thought is that modern machines are SO fast, with multi-cores/threads,
and with hundreds (thousands??) of processes going on all the time in a
time-shared manner... along with POV-ray being capable of symmetric
multi-processing.  Maybe the 'run' or 'save' activation just happens to 'fall
through the (timing) cracks' occasionally?

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> Excellent (or not).
> I thought maybe it was me since no one else has ever mentioned it.
>
> Might just be a 3.8 or a Winblo$ thing.
>

> Probably going to be a slippery bug to track down.
>
That was my thought also. I should have spoken out when it first happened. I
think it even happen on my win XP. But it ain't some thing that is repeatable.
Kenneth May be right about having a lot of tabs open. I usually do.

Have Fun!

Post a reply to this message