Jump to content

Recommended Posts

Posted

I've noticed that AP really likes to blur graphic in numerous occasions.
I work on pixel art a lot and it messes up everything. Is there any way to prevent it?
I'm attaching png that was not moved or copied at all, and the one that I adjusted positioning.

Notice the difference between top left sprite and bottom right. Move moving, more blurring (no size changing).
Any ideas or solutions, my friends? 351340511_087-Monster01SHRINK.png.03fe60ef11c98bc8cd4f3f792d9a7f1d.png087-Monster01.png.a9ebf0ea9fe1e8787993fb6358b8d771.png

Posted
13 minutes ago, Ssinssrigg said:

Any ideas or solutions,

Most likely you have not turned on in the snapping section "Force Pixel Alignment".

When doing Pixel Perfect Work you have to have the following on for the snapping. 

797980225_ScreenShot2023-05-07at11_00_38AM.png.dd9f8a0c4091604b055dfa5a128e3d2f.png

If you have a Pixel based grid made you can then turn on Snap to grid as well.

Under no circumstances turn on Move by Whole Pixels.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Posted
1 hour ago, Old Bruce said:

Most likely you have not turned on in the snapping section "Force Pixel Alignment".

When doing Pixel Perfect Work you have to have the following on for the snapping. 

797980225_ScreenShot2023-05-07at11_00_38AM.png.dd9f8a0c4091604b055dfa5a128e3d2f.png

If you have a Pixel based grid made you can then turn on Snap to grid as well.

Under no circumstances turn on Move by Whole Pixels.

I wish that would help but it doesn't :( I noticed that resizing works better under this setup, but it still blurs the image when moving or copying... or merging.

1.png.8b444be78bfb9dd837e7f4e3d5ef4e26.png3.png.3342a218c1b3076b7882e851f14066de.png

Any other ideas? 😅

2.png

Posted
3 hours ago, Red Sands said:

Does it make any difference if you set View Quality to nearest neighbour?

image.png.b031daa57d357ac44a10b51fc78d4abd.png

Sorry, I should mention this straight away. Yes, I have "Nearest Neighbour" view quality...x.png.b14c6113315b2a5ff844e1f397c1dd43.png

Posted
12 hours ago, Ssinssrigg said:

I wish that would help but it doesn't :( I noticed that resizing works better under this setup, but it still blurs the image when moving or copying..

You need to ensure that the original "pixel perfect" images are "pixel perfect" even after moving (Force pixel alignment setting and Move by whole pixels disabling) and after resizing (2x, 3x). Shifting or resizing by a non-integer part will result in blurring because the original pixel has to be split/blurred into multiple pixels.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted

In addition to the advice above about pixel alignment, why is there so much ‘space’ between the sides of the non-transparent pixels and the sides of the selection bounding box? (Red ‘arrows’ in my attached image.)

Could something in this ‘space’ be causing a problem?

Could those graphics be clipped inside a shape which isn’t pixel-aligned?

Note: Full-screen screen shots are often much more useful in problem diagnosis than small cut-down screen-grabs.

image.png.85ee0e6d6db1a81c588d3ba66b69007d.png

Posted

Working with Pixel Art in Photo requires 100% accurate workflows and detailed knowledge about what matters.

some does and donts:

  1. Pixel aligned positions
  2. Exact sizes (never resize objects unless you know how to, e.g. using Pixel Art resize)
  3. in Designer: pixel aligned artboards
  4. use px as units for documents and lines and font size
  5. use snapping options
  6.  Use transform panel, set 6 decimal digits
  7. Don‘t use nearest neighbor for view mode. It can hide issues until it’s to late. Use bilinear to allow spotting issues immediately. Use NN only at export.
  8. Vector objects with px strokes (or uneven numbers in general: don’t use stroke centered, or position to 1/2 px positions 
  9. Use anti-aliasing (on vs. off) and profiles in Blend ranges (except iPad)
  10. Avoid partial transparence
  11. use pixel brush (instead regular brush)
  12. Correct usage of merge / rasterize, avoid merge down
  13. use of grid / helper objects
  14. in Designer: use of constraints

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.

 

Posted
15 hours ago, Pšenda said:

You need to ensure that the original "pixel perfect" images are "pixel perfect" even after moving (Force pixel alignment setting and Move by whole pixels disabling) and after resizing (2x, 3x). Shifting or resizing by a non-integer part will result in blurring because the original pixel has to be split/blurred into multiple pixels.

I'm sure it was "pixel perfect" before (I think it can be ensured with maximizing and merging alpha curve... at least that is how I sometimes do that)

15 hours ago, GarryP said:

In addition to the advice above about pixel alignment, why is there so much ‘space’ between the sides of the non-transparent pixels and the sides of the selection bounding box? (Red ‘arrows’ in my attached image.)

Could something in this ‘space’ be causing a problem?

Could those graphics be clipped inside a shape which isn’t pixel-aligned?

Note: Full-screen screen shots are often much more useful in problem diagnosis than small cut-down screen-grabs.

image.png.85ee0e6d6db1a81c588d3ba66b69007d.png

Nothing was clipped. There is so much space just because I selected it like that, just to make sure I tried to move it when selecting more carefully. Same effect. BTW its not a problem with this one specific graphic, its with all images I work on.
About the "full screen thing". Thank you, I didn't know it matters, I will post full screen shots in the future.

13 hours ago, NotMyFault said:

Working with Pixel Art in Photo requires 100% accurate workflows and detailed knowledge about what matters.

some does and donts:

  1. Pixel aligned positions
  2. Exact sizes (never resize objects unless you know how to, e.g. using Pixel Art resize)
  3. in Designer: pixel aligned artboards
  4. use px as units for documents and lines and font size
  5. use snapping options
  6.  Use transform panel, set 6 decimal digits
  7. Don‘t use nearest neighbor for view mode. It can hide issues until it’s to late. Use bilinear to allow spotting issues immediately. Use NN only at export.
  8. Vector objects with px strokes (or uneven numbers in general: don’t use stroke centered, or position to 1/2 px positions 
  9. Use anti-aliasing (on vs. off) and profiles in Blend ranges (except iPad)
  10. Avoid partial transparence
  11. use pixel brush (instead regular brush)
  12. Correct usage of merge / rasterize, avoid merge down
  13. use of grid / helper objects
  14. in Designer: use of constraints

Wow, that looks good. But, I'm not a professional, honestly, I don't even fully understand some of that. Is there some guide or video that will explain how to do all of that?
- What do you mean by pixel aligned positions?
- I try to use exact sizes and I modify that only if necessary,
- I always use px as units,
- I use snapping options (as it was discussed earlier),
- I rarely use transform panel,
- I changed view mode as you advised,
- I don't think I use vector objects at all,
- how to use anti-aliasing and profiles in Blend ranges?
- I'm avoiding partial transparence like a fire (if possible)
- Pixel brush is main tool I use
- I think I'm using merge / rasterize correctly, but I'm not a professional, so cannot be sure here, I'm avoiding merge down (usually go with merge visible)
- I'm using grid / helper objects
I was kinda hoping that there is some one-click option or a profile or something like that to prevent Affinity from all that blurring. I mean... how difficult can it be?
Microsoft Paint resize, copy, move etc. without blurring by default...

Thank you guys for all your help and advice! I really appreciate your time 😁

Posted
On 5/7/2023 at 12:45 PM, Ssinssrigg said:

I've noticed that AP really likes to blur graphic in numerous occasions.

@Ssinssrigg You may want to skim/peak at this thread aka "a rabbit hole" for future reference:

You are expected to learn: "Pixel" layers are not actually pixel layers. So it is important to Rasterize everything BEFORE merging layers to connect them to document DPI (your document's actual resolution)...

See in particular: @fde101's post:

Maybe give my whingepost a thumbs up in Feedback area if your head has not completely melted and what I requested makes more sense to you:

Posted
14 hours ago, NotMyFault said:

some does and donts:

15. Watch out for object rotation! At least in V1 it did mischief when converting to pixels.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted
6 hours ago, Ssinssrigg said:

I was kinda hoping that there is some one-click option or a profile or something like that to prevent Affinity from all that blurring. I mean... how difficult can it be?
Microsoft Paint resize, copy, move etc. without blurring by default...

Unfortunately, such an imagined one-click option is not available. Affinity apps are so much powerful, at the cost of being far more complex to handle.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.

 

  • 2 weeks later...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.