Xakiru Posted January 26, 2023 Posted January 26, 2023 This image was supposed to be 128x128, but it got exported to 130x130 Quote
GarryP Posted January 26, 2023 Posted January 26, 2023 Are the pixel values in the Transform Panel actually integers, or do they just look like integers because of rounding? Try changing the Decimal Places settings to three (or more) via Preferences / User Interface and check again. Are there any Quick Effects applied to the parent layer(s) of that layer? When you export that layer, how do you export it? File → Export, or the Export Persona? Note: Full-screen screenshots are often more useful than small screen-grabs as we get more information at the same time. Quote
Xakiru Posted January 26, 2023 Author Posted January 26, 2023 Side note: This happens in both V1 and V2. Here I started a new document of 256x256px I added a black square of 124x124px + outline of 2px (which becomes 4px since it's from both sides), I export to PNG (Ctrl+Alt+Shift) and here is the result. Just to make sure, I've just set everything in decimal places to 0 (I have no idea what these do). The result png file (opened in affinity): I attached the file, just in case. padding.afdesign Quote
NotMyFault Posted January 26, 2023 Posted January 26, 2023 Outline leads to partially transparent pixels. The export includes them, even if they are barely visible. better use stroke to outside. Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
GarryP Posted January 26, 2023 Posted January 26, 2023 1 hour ago, Xakiru said: I export to PNG (Ctrl+Alt+Shift) I think you meant “Ctrl+Alt+Shift+S” to get to the export dialog. Have you tried using the Export Persona instead? 1 hour ago, Xakiru said: Just to make sure, I've just set everything in decimal places to 0 Setting the Decimal Places settings to zero will not show any decimal places. If you do as I said earlier, “Try changing the Decimal Places settings to three (or more)” then you should be able to see the decimal places, if there are any. As NotMyFault said above, in this sort of case you probably should be using a Stroke on the Outside rather than the Outline Quick Effect. Quote
Xakiru Posted January 26, 2023 Author Posted January 26, 2023 7 hours ago, NotMyFault said: Outline leads to partially transparent pixels. The export includes them, even if they are barely visible. better use stroke to outside. Same result with stroke my friend 6 hours ago, GarryP said: I think you meant “Ctrl+Alt+Shift+S” to get to the export dialog. Have you tried using the Export Persona instead? Setting the Decimal Places settings to zero will not show any decimal places. If you do as I said earlier, “Try changing the Decimal Places settings to three (or more)” then you should be able to see the decimal places, if there are any. As NotMyFault said above, in this sort of case you probably should be using a Stroke on the Outside rather than the Outline Quick Effect. Yea I meant clrl+alt+shift+S I didn't try to use persona export cuz I'm not planning to cut out every single item I'm exporting while they are already in separate layers. I didn't read well about the "three or more", I changed it to 3, and it somehow worked, what does the decimal places for unit mean ? Quote
NotMyFault Posted January 26, 2023 Posted January 26, 2023 This is a old bug unearthed again. Probably a rounding issue. Clip canvas shows the extra pixel, too. If you rasterize and trim, no extra pixel. If you add strokes or outlines, this will add the stroke width to the canvas. Minor deviations will lead to 1 extra pixel outside, as exported files by Affinity will always have „rounded up“ number of pixels. If you set a stroke of 1.9px, no extra pixels will be added. Visual result is almost what you want loukash 1 Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
R C-R Posted January 26, 2023 Posted January 26, 2023 55 minutes ago, Xakiru said: ... what does the decimal places for unit mean ? It means how many decimal places will be displayed in the UI, but that has no effect on the actual values used, which is to about 8 decimal places of precision. Quote All 3 1.10.8, & all 3 V2.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7
loukash Posted January 27, 2023 Posted January 27, 2023 6 hours ago, NotMyFault said: This is a old bug unearthed again. It's in 1.10.6 as well. 6 hours ago, NotMyFault said: If you rasterize and trim, no extra pixel. There are a few other workarounds without rasterizing: use Align Stroke Inside only Expand Stroke 6 hours ago, NotMyFault said: If you set a stroke of 1.9px, no extra pixels will be added. In case of the Outline Effect, even 1.999999 px width will fix it. NotMyFault 1 Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
Xakiru Posted January 27, 2023 Author Posted January 27, 2023 Alright, Thank you guys, I learned many ways of working around this, but I hope they will fix this issue and make it work properly as it should someday, and that I wouldn't have to pay for V3 to get that V1 feature bug fixed. loukash 1 Quote
Dan C Posted February 24, 2023 Posted February 24, 2023 Hi @Xakiru, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm I am able to replicate this issue here and therefore I have logged this with our development team to be resolved in a future update. I hope this helps Xakiru 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.