Jump to content

dPRogerWilco

Members
  • Posts

    7
  • Joined

  • Last visited

  1. Thanks for forwarding it to the developers. Yes, it's also my experience that it happens more often, if click on crop directly after loading. But sometimes it also crashes after I waited a little bit. Crop is the first thing I usually do when working on a photo. And it also happens with the crop tool during raw file developing. But the error is probably in the freehand tool, which does not left everything in a clean state...
  2. Thanks for your help. I tested msi/exe now and it behaves the same. Thanks to this post, I can now finally reproduce the crash: So if I use the freehand selection (which I need a lot), then open another picture and click on crop, then the app is crashing. In the recording: - I open the picture several times first and click on crop -> no crashes - I open the picture, use the freehand selection, close the picture and open another picture, click on crop -> crash I don't need to restart the computer like mentioned in the other post. It's stable again, until I use the freehand selection again. Affinity Photo 2 2024-12-20 13-56-06.mp4
  3. Since I bought Affinity Photo 2 in 2022 I have frequent crashes. App just closes at random action, mostly I believe if I click to fast e.g. on crop after loading a picture. But sometime also in other cases. I read, that crashes could be related to OpenCL, but it also happens for me with disabled OpenCL. With every update I hope it's getting fixed, but since it still happening, I am reporting it here. I attached the latest crash dumps (the "attachment_Log.txt" looks always very similar, so I added only one). I am using Windows 10. It's not a show-stopper for me, but it's annoying. Especially, because most changed tool settings are not saved, when the app crashes. c5144ae4-7a8f-47ac-a488-2c27af3e83d7.dmp 9556c45c-a539-4d51-a29b-33116f62ef1a.dmp 0d2581a8-6a51-4916-9c28-4fc1d265256e.dmp 762044fe-64b5-40f8-8016-d8b6060c66da.dmp 049f0d07-03ea-4dff-bea8-54728d8d7aae.dmp 3015599f-138f-4d57-afdd-15e135dde407.dmp 727c9093-5a61-40b0-bfac-8154b0272d4a.dmp attachment_Log.txt
  4. Thanks a lot for your help, that was the reason it was not working... such a minimal mistake. It probably only sees exact 1.0 as opaque, because it wouldn't know what background color it should use to calculate the RGB result otherwise. But from usability point of view a threshold of 0.5 (or even selectable) would be better.
  5. Thanks both for your help. Interesting, that a picture can have non natural numbers as dimension. Back to my export issue: I use the curve adjustment layer to manual control the "binary" mask, because indexed PNG doesn't have semi transparency and the export dialog does not have a adjustment for this. I tried now your suggestions and merged the layers. I also exported the file as non indexed PNG (see attachment) to be sure that nothing is left of my layers and half pixels. But still, export as indexed PNG with palette does not work for me.
  6. Thanks, didn't noticed it (I assume I tested the different presets). But sadly it's also not working with any of the other pixel formats (including keeping document format). Weird that it works for you, maybe something wrong with my picture? I attached it now to this post in the afphoto format. What I also noticed: picture is 403 pixels high in the main view, but on the export dialog it changes to 404 pixels... example.afphoto
  7. If I want to export a layer with transparency in Photo 2.5.5 as PNG with palette "auto", then the preview (exported file) just shows an empty picture. PNG without palette and not automatic palettes seems to work. I remember that some minor version before had already a similar bug. Was it introduced again?
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.