cgartists Posted April 18, 2023 Posted April 18, 2023 When eporting artboards via esport persona all sizes of jpgs are +1 px on height and when exporting individual artboard one-by-one it is correct. In past it happened when artboards had x or y coordinates not as full pixels but as 0,5px value for example even for individual but in this case now I checked all of them are full pixes. ads.afdesign Quote www.cgartists.eu
walt.farrell Posted April 18, 2023 Posted April 18, 2023 All 3 artboards named Artboard1 are have non-integer sizes: The others look OK to me. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
cgartists Posted April 18, 2023 Author Posted April 18, 2023 You are right - I have them there but never select them in export panel - do you think it may be affecting the correctly located/sized ones? Quote www.cgartists.eu
walt.farrell Posted April 18, 2023 Posted April 18, 2023 13 minutes ago, cgartists said: do you think it may be affecting the correctly located/sized ones? Possibly, but I'm not sure. I have a vague memory that there was one problem possibly related to this that was fixed for File > Export but not fixed in the Export Persona. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Staff MEB Posted April 19, 2023 Staff Posted April 19, 2023 Hi @cgartists, If you are using the Export Persona make sure both the X,Y coordinates and width and height of each artbord have integer pixel values, otherwise the export sizes will be incorrect. If you are exporting the artboards individually via menu Fie > Export (so one at a time) you only have to worry about the width and height of each artboard being pixel integer values (x,y coordinates are irrelevant here). Regarding the file you attached specifically (and considering you are using the Export Persona to export them all at once), besides the three "Artboard1" artboards not having pixel integer values for their width and height, there's also other artboards which have their X,Y coordinates on non-integer pixel values - those must be also corrected to integer values to ensure all slices will have the correct dimensions on export. walt.farrell 1 Quote A Guide to Learning Affinity Software
cgartists Posted April 19, 2023 Author Posted April 19, 2023 Thanks all - I do see now that it was caused by first artboard in top left corner of all artboards (in relation to 1px added width then left and in relation to 1px height it is first artboard from top). @MEB - your analysis and workaround is correct but it is a workaround... the fact that one artboard can make all others export wrong is a bug. I don't think artboard defined as 100x100px should ever export as 100x101px. Also when moving artboards around default should be snapping to full pixels as most design files (or all?) don't support anything other than full pixels anyways. Quote www.cgartists.eu
Staff MEB Posted April 19, 2023 Staff Posted April 19, 2023 Hi @cgartists, You are correct. I'm seeing the weird behaviour you're describing which may be related to the origin point (seems you have changed it or started creating new artboards to the top left of the original origin point). I don't have much time now to check this out now but will take a deeper look tomorrow. Seems there's a bug somewhere yes. My apologies. Regarding you last paragraph, the artboards may be intended for print and use physical dimensions which do not translate to full pixels most of the time. The main toolbar has a button to Force Pixel Alignment (in the Snapping group) to ensure artboards that use pixels as dimensions are pixel aligned. Note this only applies to objects created after you enable it (it does not "fixes" objects previously created). Also in the same group make sure Move By Whole Pixels is disabled, otherwise artboards that are already located in non-integer pixels positions will keep them part since that button only allows full pixel translations/movements. cgartists 1 Quote A Guide to Learning Affinity Software
LEB Posted March 3, 2024 Posted March 3, 2024 For your information, the problem of individual artboards not being rendered at the correct size when located at a non-integer position has not been resolved in version 2.4.0. Quote
GarryP Posted March 3, 2024 Posted March 3, 2024 The discussion here between users and staff might give some useful information about, and some of the reasoning behind, this long-running issue. LEB 1 Quote
LEB Posted March 22, 2024 Posted March 22, 2024 Thank you, I could solve my issue by using origin point with no decimals. Not trivial to understand for a vectorial app where it could not matter when you are exporting an individual art board. Quote
GarryP Posted March 22, 2024 Posted March 22, 2024 If you read the discussion I linked to in the post before your last one you will see that there seems to be an agreement between some users and some staff members that Artboards should (by default) be pixel-aligned upon creation and that a 'ticket' (AF-2093) has been logged for development to have a look at to see if this could be implemented. However, some posts in that discussion also give information about some problems that could occur by making this change, so it’s probably not a trivial change with no possible negative repercussions. In other words, it's something that needs to be properly investigated before any possible change is implemented, to be sure that any knock-on effects don't make things worse. LEB 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.