"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