clipka <ano### [at] anonymousorg> wrote:
> Am 05.06.2017 um 13:19 schrieb omniverse:
>
> > Tried that now using HxD (https://mh-nexus.de/en/), and that does work okay if
> > deleting back from end of file to the prior ViIdINT4.
> > Or more precisely, as seen in the Hex editor:
> >
> > 56 69 49 64 49 4E 54 34 00 00 00 04 00 00 00 03
> >
> >  or
> >
> > ViIdINT4........
>
> Yes, those "00", "04" and "03" are characters you're typically losing if
> you use any odd text editor.
>
> >> I've had a look at the relevant source code by now, and judging from it
> >> there should be no problem reading a truncated file: The code is
> >> designed to just read the state file up to the first location that
> >> doesn't seem to make sense.
> >
> > No luck here when I deleted back to a midway point between the ViIdINT4's.
> > POV-Ray just acts like the render was done without opening a render window and
> > doesn't show any errors in the message pane.
>
> Does that hold true even if you do the truncation in a hex editor?
>
> Because the file is full of "00" and other non-printable characters, and
> text editors tend to not treat them nicely.
>
> Also, the file is likely to include some "0D" here and there, which a
> Windows-based text editor might interpret as a Unix-style line ending
> and replace it with the Windows-style "0D 0A" line ending when saving;
> while a Unix-based text editor might do just the opposite, replacing any
> occurrence of "0D 0A" with "0D". Either modification will invariably
> break the file from that point onward.

No changes like that showing up in hex editor.

Could be my mistake about the messages POV-Ray shows, I guess. I might have
overlooked a regular kind of message because I had been thinking it would be
highlighted or look more obvious.

I was trying the same thing as before by removing the last good block of code
back to ViIdINT4 (plus extraneous code afterward as I already told of). Got the
same no render window again.
However this time I noticed the message pane tells me it was "skipped" because
it already existed (shows message near end of all other info). Sure enough, the
completed render was there so I deleted it.

Next I removed code back to a midway point of end to ViIdINT4.....

Successful with continue trace (without existing image), it draws up the
partially done render window and goes on to finish it.

Only difference this time is the 03's are now 02's, which I couldn't explain.
Maybe relates to different day?? Only conjecture I'm sure.

Bob

Post a reply to this message