I worked on a large image of 49XXx70XX in pixatool. It looked right before export, but when I looked after export, there were lines in the image that did not contain dither. Hope this will be fixed in the new version.
I just tried the fullscreen function by pressing the F key. I have tested both 4K monitors and 1K monitors. On both screens, the export button disappeared off the screen, so I couldn't press export. I'm using windows 10, is that the cause? Anyway, I'll keep you informed to improve your program.
I just downloaded v155. I will test this.
I will give you more information for your exact test.
In v155, pressing F works the fullscreen normally I wasn't thinking of trying to test it because the fullscreen mode was not available on the v157 by pressing F. Sorry.
When I pressed F, the strange stripes disappeared as well. But it still seems that the problem occurs.
I will Attach a screenshot. This is an image that worked on fullscreen in v155.
My resolution is 1920x1080. I'm sorry I can't provide you a preset file.
I have no way to upload files here.
I will also take a screenshot of the preset information.
%%NOTE: I also edited Dither Amount to 14
I just discovered that I can open the preset file with Notepad. In the image I uploaded earlier, I adjusted the area inside the red box.
Also uploads the preset information.
{"c2array":true,"size":[200,1,1],"data":[[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[256]],[[0]],[[1]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[100]],[[100]],[[0]],[[2]],[[2]],[[2]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[100]],[[0]],[[0]],[[0]],[[0]],[[100]],[[100]],[[2]],[[2]],[[1]],[[1]],[[0]],[[100]],[[100]],[[100]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[14]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[231]],[[75]],[[154]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[10]],[[0.1]],[[0.5]],[[1.5]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]],[[0]]]}
Can you test with the "batch procesing" ? just select that image instead of multiple.
If not well, i recommend contact on support@itchio.com and request a refund. Sorry, all seems fine what you are doing, some it looks some bug in the tool. Btw, i will try to investigate to see if i can fix it, sorry for the incovenience!
Sorry. As a result of testing on v155, the same problem occurs with pixelate W,H=3 and W,H=4. I press F to get fullscreen. The reason seems to be simply a matter of size. I want to give you the information you want, but I think this is the limit I can provide.
%%NOTE:Unfortunately, batch processing also creates the same problem.
I am using Windows 10, and the font size is 100%, which is the default of Windows 10. I'm using a desktop.
But I have also seen this error on other computers with 4K monitors attached. The computer is running Windows 7.
That computer is my personal work computer and is currently not accessible. I am currently home. Sorry.
I live in another non-English speaking country, but I am a programmer. I have witnessed js error on v135 you made. I mainly use c# and c++, but not javascript, so it may not help. Still, I want to help you as much as I can.
In my opinion, in the process of converting an image to a floating point between 0 and 1, I want to check if there is any error in the position of the pixels. Floating point errors sometimes make a roundoff operation. The key to this problem is that the dithering doesn't work in areas where it should be. Somewhere, it seems that the pixel is clearly not recognizing where it should be taken.
Or, it may be that the dithering position is pushed by one and the calculation is not possible.
I love this program so much that I want to help improve it whenever possible.
