Gigapixel v5.5.2

Update: Exited and restarted program, set to CPU/Low, did a Preview, exported and it did the GPU ~17% thing again and the exported image looked like that blue one above in a slightly longer 2 mins 14 seconds. It doesn’t seem to much like these new drivers.

Update: It did it again.

Update: and again and again.

It seems that the first time after loading the program the CPU/Low export will use ~17% GPU and that will provide a ‘Blue’ image.

If I cancel the export in the middle - as I did after accidentally stopping my stopwatch - then start again it will not use the GPU and the resulting export image will be fine.

But…I then do a Preview and export again and it goes back to using the GPU ~17%, but this time the results were fine. Pixel identical to the previous export. Definitely going back to the previous drivers. :wink:

Definitely going back because now 5.2.0 doesn’t use the GPU at all with the newer drivers. :frowning:

Update: had a little panic attack as even with the older graphics driver reinstalled, 5.2.0 refused to use the GPU and Previews were taking 65 seconds whether I turned GPU on or off. :frowning:

But selecting ‘Use Recommended Settings’ and it did the little ‘Calibrating’ dance and started using the GPU (@100%), so super fast Previews again. Phew!

Nothing exists like that in 5.5.2., so I’m stuck with whatever it thinks is the right (wrong) thing to do with the GPU. Why was this option removed from later versions?

Yes, I too have the jagged preview issue ever since the 5.5 version was introduced (the new 5.6 beta has it too). I think it relates to Win10 display scaling settings, but SharpenAI and VEAI don’t display this problem. The last beta of DenoiseAI also had the aliased preview, but I never upgraded to the release version to check that.

Any info of Gigapixel 5.6? Long time since 5.5.

I see. Thanks.

No upgrade from April ?

Wake up!

Hi all,

A new version has been released. You can view the release thread here.

Thank you!

1 Like