gzah Posted December 26, 2019 Posted December 26, 2019 I have similar problems. All images in the attached files are the same size, but when I export them with the export persona, some images are suddenly higher and/or wider. If I export them individually, the automatically adjusted distortion is already displayed during export. Only if I close and open again the lock I can enter the exact dimensions and then it still works. The problem occurs in designer and photo. I have not tested publisher. This is a very annoying major bug. Please fix it soon. Lüfter_v2.afdesign Lüfter_v3.afdesign Quote
pruus Posted December 29, 2019 Posted December 29, 2019 Could this be a problem because the image has been cropped? Than things go wrong. Try this one: After Restorize and Trim. Then export. I did get rid of this problem. Quote
gzah Posted December 31, 2019 Author Posted December 31, 2019 thanks for the hint. if i rasterize and trim it it works. but i don't want that. if the transform panel says it is 32x32px then it should be exported exactly in size. Quote
gzah Posted December 31, 2019 Author Posted December 31, 2019 (edited) another bug I noticed: if the image has a decimal point in the x position, it will be one pixel wider!!! even if it is rasterized and trimmed! With the y position it is the same. As soon as a number with decimal places is entered => height = height + 1 Edited December 31, 2019 by gzah Quote
walt.farrell Posted December 31, 2019 Posted December 31, 2019 2 hours ago, gzah said: another bug I noticed: if the image has a decimal point in the x position, it will be one pixel wider!!! even if it is rasterized and trimmed! With the y position it is the same. As soon as a number with decimal places is entered => height = height + 1 That's the way it works. You need to ensure that your image has an integer pixel size and is positioned properly aligned (snapped) to the pixel grid. 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.2.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
gzah Posted January 3, 2020 Author Posted January 3, 2020 if that is the intention, I acknowledge it. But I still don't understand what the point is. Is there a setting where you can specify that the x and y position can only be changed as integers? I just tested with my two files (Lüfter_v2 / Lüfter_v3) what happens if I align all artboards with integer numbers. I have intentionally avoided raster and trimming. I do not want to do that. It worked with Lüfter_v2. All artboards are now exported with 32x32px! With fan_v3 it also worked except for two artboards (-90°,-110°). Why didn't it work for both of them? Then i moved the two artboards a few integer pixels back and forth. suddenly it worked. it's just acting really weird. if you like you can test this yourself. here attached you will find the original files and the modified files in which all artboards are aligned integer. if you move the two artboards -90° and -110° back and forth in fan_v3_integer aligned, they will suddenly be exported correctly with 48x48px. if you move those artboards it is also possible that suddenly other artboards are no longer exported with 48x48px. just strange and time-consuming. Lüfter_v2.afdesign Lüfter_v2_integer aligned.afdesign Lüfter_v3.afdesign Lüfter_v3_integer aligned.afdesign Quote
walt.farrell Posted January 3, 2020 Posted January 3, 2020 26 minutes ago, gzah said: Is there a setting where you can specify that the x and y position can only be changed as integers? You may want to have Snapping enabled, and make sure that Snap to Pixel Grid is enabled, and Move by Whole Pixels is disabled (off). Then, any object you create should be properly positioned and sized, as long as you don't hold the Alt key while copying an object. 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.2.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Staff MEB Posted February 6, 2020 Staff Posted February 6, 2020 Hi @gzah, Welcome to Affinity Forums:) Sorry for the delay getting back to you. These posts were originally on this thread which i have split since they are not directly related. Regarding you questions/issues: the reason for the wrong export sizes was the non-integer values of the X,Y coordinates on most of them as walt pointed out. The problem with the two artboards in particular (-90°,-110°) in the Lüfter_v3_integer aligned.afdesign file is the same. Some of the artboards remain misaligned on the Y coordinate (so on non-integer values) with those two in particular enough misaligned to add an additional pixel to the height of the exported files. To check this go to Affinity Preferences, User Interface tab, Decimal Places for Unit Types section and change the Pixels value to 4 or more pixels so you can see more decimal places in the Transform panel (and elsewhere). Check the artboard's Y coordinate again and you will see that some of them remain misaligned vertically - although by a very small margin. Align them all vertically to their tops and they should then export correctly. As you also discovered, if you move those two artboards slightly with Force Pixel Alignment enabled (and Move By Whole Pixels disabled) they should also snap to integer values and export correctly. So ideally you shouldn't have any decimal values on the X,Y coordinates or on the objects dimensions (with/height) that define/set the slice dimensions - in this case the artboards - to ensure a correct export/output. You can ensure this by having Force Pixel Alignment enabled and Move By Whole Pixels disabled from the beginning and making sure you duplicate the artboards when necessary using the cmd key rather than the alt key as this last one duplicates them but also overrides the snapping options (Force Pixel Alignment etc) leaving room for incorrect placement on non-integer values. Quote A Guide to Learning Affinity Software
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.