Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'force pixel alignment'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.3 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 7 results

  1. Could someone please explain something to me, before I punch my monitor? I turn Force Pixel Alignment and Move By Whole Pixels on (pic 1). I use Rectangular Marquee, I move the selected area ONE pixel to the right and everything looks fine (pic 2) until I unclick the tool (pic 3) when Affinity Photo does... something weird with the selection. How the hell do I force Rectangular Marquee to full pixels?
  2. When 'Force pixel alignment' is turned on all drawing from that moment is snapping to whole pixels. But when you start moving those just drawn curves (all created on whole pixels) around you see they are still resulting in half pixels some times. So I did some switching in snapping options and found out that Force Pixel Alignment isn't on top of it all (highest priority). There are certain other snapping options that still cause Designer to chose off pixels. Like 'include margin midpoints', but also other important snapping options, like 'snap to grid'. Look at this: (for the record: ''Move by whole pixels' is turned off) double-snapping.mp4 In my opinion this is confusing, misleading and error prone and the unexpected endresult remains hidden to designers while designing, because we (well at least I do) assume all graphics will be snapped to pixels when 'Force pixel alignment' is set to true. I place this under bugs, because I really believe designers should be able to trust that 'Force pixel alignment' will indeed force pixel alignment, and right now it's not and most of the time we don't even know it until problems occur (like blurry images as an end result we see when we finished the design and 'render' to png for example). In the video you can see clearly the node is bing placed on a half pixel because it's prefering the margin snapping over pixel forcing. But you can only see that now while looking very closely on a zoomed-in grid of 100x100 and even a visible pixel-grid turned on. Normaly we don't work like that and need to trust Designer to always pick/snap to whole pixels if we set 'Force pixel alignment' to true. Why else would we turn that setting on and the setting is a prominent button on the UI that's different to other snapping options. So it seems like this is causing the half-pixel issues I was having for drawing graphics. I found out that Designer has a 'pixel work' preset in snapping options that turns off all other snapping options making sure forcing to pixels works. So yes, that preset (all other snapping turned off) will probably always work with pixel work and always chose whole pixels. But if we need to turn off all snapping options just to work on whole pixels that seems a little too black and white / one or the other to me. I want to use both and consider that to be a very standard expected workflow more designers like to use; I use snapping options a lot, but I only want to enable force pixel alignment next to that as a top priority(-correction) at the end. In my opinion force pixel alignment should always be priority over all other snapping options, so in practise I would expect Designer to fire it's snapping algorithms first and then correct the end position of those snappings to the nearest pixel when Force pixel alignment is turned on.
  3. Force Pixel Alignment does not work when using the modifier key(Option/Alt) to ignore snapping. (such as with Move/Node tool) I want Force Pixel Alignment to work like when the Snapping(U magnet icon) is disabled.
  4. I know this has been reported in the past but we still seem to have this issue and that is that PDF page sizes do not export to the correct size. They are off by up to 5/1000th of an inch. Here is an example: So in this example you have a ready to print PDF but on the left the page size is 5.503x2.130 while it's supposed to be what affinity shows and that is 5.5x2.125. This may not seem like a big problem but it really delays our Quite Imposing automation for printing. The file then has to be manually cropped in Acrobat. This happens with almost all files with multiple artboards. I have been told that I need to use for pixel alignment and that should correct it - I keep it on and I still get these results. Is there a way to resolve it on my end or is something that Serif must do? thanks!
  5. Could we perhaps get a customizable keybind for this feature? Would be lovely as I think it may be used more than the snapping bind, for me at least. Thank you!
  6. Hey Affinity. I'll try and make this brief: 1.) I've bought into your Windows Program as soon as it was available because I loved the betas I participated in. 2.) I'm using the program to attempt production quality work and I'm running into issues that are common but they never have a direct answer. Setup: -Assets are created in 200x200 pixel RGB documents (300 D.P.I.) -Object Creation is created with "Force Pixel Alignment" and "Snap to Margins" set (as well as many other snapping settings that aren't displayed by guides or rules when manipulation occurs) -All issues occur on Paid version: Windows 10 x64 Issues: -Objects snapped to Artboard boundaries are rendered with Aliasing Artifacts. -Objects "snapped" to margins aren't truly aligned with margins, scroll in far enough and the placement is off, likely resulting in the artifcats -Artboard/Canvas doesn't draw accurately when zooming Concerns: -I'm needing to create a tilemap, a series of objects sized the same way that can be aligned flawlessly without export/rendering artifacts. -I've created a full tilemap out of objects that have supposedly "snapped" to the margins and it's full of rendering artifacts (aliasing, object out of place, etc) -I've attempted to recreate a single tile in a 200x200 shape that results in the same artifacts, blending pixels around margins when I expect a solid color Finally I ask this: -All this considered, is there a way to create a 200x200 and eventually a 100x100 object that forces FULL pixel alignment, exports to PNG with Transparency and avoids using Aliasing- or should I find another solution? I've enjoyed your product for an extensive amount of time, that being said, I've read enough on these forums to see that Pixel-Snapping considers "1/2" steps, results in floats, and exports include the artifacts included. If I had one request; I'd ask you to create a "pixel-perfect" mode that forces objects to fill full pixels, consider the dimensions of the canvas only (no float values) and renders based on the working image (Retina/Pixel view, no aliasing). If I'm setting up documents to fail, PLEASE educate me- I'd happily admit I'm wrong if you point me in the right direction, as of now, the work I've spent an excess amount of time is going to require just as long to clean up in other programs to create the desired result. Good luck, thank you for reading my book.
  7. Please can someone explain the reason behind the 2 buttons in the top toolbar for Move by whole pixels" and "Force Pixel Alignment"? If you could give an example of when you would use one option over the other that would be helpful for me to understand. Thanks, Rob
  • 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.