Hi, thanks for the feedback. Does this issue occur only when creating PNG files, or does it also happen while using the software?
And this all started with the most recent version? In the latest update, I switched from fragment to compute shaders for rendering. I’m currently on vacation, but I’ll try to reproduce the issue once I’m back. I might need your help to test some possible solutions. I’ve also been thinking about opening a Discord server for easier communication.
Regarding your suggestion for better stroke/layer management, I plan to rework the internals to handle things like subgroups and combine the UI into a single tree view. I also want to add several quality-of-life features, so you might want to wait for what I have planned—though it will take some time. :)
46 days ago(+1)
Hi, I tried to reproduce the issue on all my available GPUs, including two different AMD ones, but I wasn’t able to. This one will be tough to track down, so I’ll need more detailed information about when it happens and when it doesn’t. We should probably move communication to Discord or Twitter for easier troubleshooting. Also, you might want to check if your graphics drivers are up to date, just in case. Best regards
45 days ago(+1)
Okay, great to hear. The issue with the snapshot function seems like a GPU resource synchronization problem to me. It would probably be a good idea to have a channel where I can send you test builds, so you can let me know if the issue persists.
45 days ago(+1)
Alright, I’ll set something up and let you know once it’s ready. By the way, kudos for making the most of your available display resolution! :D
I'm absolutely clueless when it comes to stuff like this, so you'll have to let me know if this works or not.
Here's the link -> https://discord.com/invite/42wGegU2