Welcome to Fractal Forums

Fractal Software => Bug Reporting => Topic started by: taurus on September 20, 2013, 01:53:41 PM




Title: incomplete imagery in 1.17
Post by: taurus on September 20, 2013, 01:53:41 PM
I encountered a problem, when animating in opencl mode. the saved images are incomplete. I tried with all three opencl modes and in png16 and jpeg - all the same. The screenshot below shows what is saved.


Title: Re: incomplete imagery in 1.17
Post by: Nahee_Enterprises on September 20, 2013, 02:21:26 PM
    I encountered a problem, when animating in opencl mode.   the saved images are incomplete.  I tried with all
    three opencl modes and in png16 and jpeg - all the same.   The screenshot below shows what is saved.

Difficult to see, but are you referring to the black strip at the top of each image??  Because the height of that "strip" changes between the images, which leads me to think that it may be what should have been rendered.  But like I said, it is too small to tell from those tiny thumbnails.

Besides, if the JPEG file was incomplete, it probably would not even be displayable without getting an error.
 


Title: Re: incomplete imagery in 1.17
Post by: taurus on September 20, 2013, 04:16:44 PM
But like I said, it is too small to tell from those tiny thumbnails.
click on the screenshot to enlarge

Besides, if the JPEG file was incomplete, it probably would not even be displayable without getting an error.
Only if the file was incomplete. Here the content of the image seems to be incomplete...
the missing part already misses in render window


Title: Re: incomplete imagery in 1.17
Post by: Buddhi on September 20, 2013, 09:30:02 PM
It looks like I have next problem to solve. I observed sometimes the same problem on my computer, but it was once per hundreds of images. I will look deeply in the code.


Title: Re: incomplete imagery in 1.17
Post by: Buddhi on September 22, 2013, 11:48:05 AM
Taurus, I'm working on this problem, but it is quite hard to reproduce it. I have one project where it occurs about once per 50 frames and what is surprising it is repeatable. On some animations it doesn't happen at all. I see that on your animation this is visible on every frame. Will be very helpful for me if you send me your project file (main settings file and keyframes) via email or priv message and then I will try to work on it. Do you observe it on some other animation too?


Title: Re: incomplete imagery in 1.17
Post by: Buddhi on September 22, 2013, 03:55:57 PM
I FOUND IT! When I used in debugger many conditional breakpoints and watch expression, I found some very old thing in the program which shouldn't be now at all. This caused too early image refresh which erased some part of the image. In few day I will release updated packages with all new bug fixes.
Thanks for bug reporting.


Title: Re: incomplete imagery in 1.17
Post by: taurus on September 22, 2013, 04:25:10 PM
Oops, just finished my response. It's obsolete now, but I leave it in a quote. Thanks for your efforts!

Quote
Ok, before I prepare the files, I need to explain some things, because my workflow might be pretty different, than expected.
Usually I work with at least four animations at the same time. One regular animation project, with keyframes in default directory and three search animations, with keyframe files in subfolders (search01, 02, 03) of the keyframe folder. In order not to loose track of what is what, I do not have a main settings file, I store all the settings - incl. paths - within keyframe00000.fract and/or 00001 (the second one sometimes with reduced resolution, effects and subframe number).
So when you want to load the settings, just open keyframe00000.fract via "load settings", I will remove all asolute windows paths, so it should open with your default path settings.

So far I tried with two of my branches. one search and the project branch. I'll send you both. both should be rendered in full shader mode, as the detail level parameter is elementary part of my fractals. (Just go ahead and try with normal or fast - the results are not even close)
When my observation is right, the black stripe is bigger with frames, that render in shorter time, which lead to the assumption that there is a timing problem. But it's now up to you to interpret the results. Just to mention, that it doesn't happen to all frames but I never had 10 frames in a row, without something missing. Good luck and happy hunting - and feel free to ask, if you need additional information.