Sef Pinney Design

@Pauls Thanks Paul. Here is the .afpub from my other thread. You can see the aliasing resolution is at least half that of the Interface (191ppi) while the document resolution intent is set to 300ppi, even in the attached screenshot. Casegood .AFPUB

@Jon P Will do. Thank you!

@Jon PAlright, I will look into that. It would be best if Resource Manager read Pixel dims from Explorer meta-data, then don't you think? Also, it REALLY needs to compare File Modified tags, b/c I think it's getting lots of false positive "file changes." So, I think Resource Manager has two issues that may be compounding this. It's wrong about File changes, AND it freaks out when an Image has been resized externally, AND possibly crashing when it's also a missing link. Please see my other thread: resource manager spamming me... Please let me know. I will fix all the broken links and see what happens.

@Jon P Alright, I will look into that. It would be best if Resource Manager read Pixel dims from Explorer meta-data, then don't you think? Also, it REALLY needs to compare File Modified tags, b/c I think it's getting lots of false positive "file changes." So, I think Resource Manager has two issues that may be compounding this. It's wrong about File changes, AND it freaks out when an Image has been resized externally, AND possibly crashing when it's also a missing link. Please see my other thread: resource manager spamming me... Please let me know. I will fix all the broken links and see what happens.

I don't have Designer, but I know how my monitor (and windows, and my Quadro) anti-alias by default without any up or down-scaling. That's all I want. To fake some lower resolution with a 72ppi pixel view is lying to the user about monitor settings, and the documents underlying resolution (with raster images.) Document Setup has a DPI setting, and it's set to 300ppi in this case. So, Pixel view should take One pixel of Document and translate it to One pixel of Display. AND it should take Vectors with no inherent pixels and Rasterize them at 300ppi, obviously. If I wanted to work at 72ppi as the document standard, I would set that, and would expect to see pixels all day long. If I wanted 2x Magnification or 3x (for 300ppi) to make the pixel edges visible, I would zoom (B/c 4k). There's a reason why Photoshop's pixel grid overlay only appears at 2x actual pixel res. Am I missing some "Gotcha" in the User interface design logic of the devs?

Also crashing at random. But this morning it crashes on File Open. Every time. Please HELP ! I'm in the middle of a critical quality control document for our company. Pretty worried, I may need to try and recover from a (hopeful) incremental backup.... ugh. The uploader failed twice with the attached 18Mb .zip, worked the 3rd time, FYI. Casegood Quality Guide.zip reports.zip UPDATE: -------------------- I was able to open the .afpub on my Mac, fix a few broken links, and re-save as a new version. I hope it's not crashing exclusively for missing resources... that seems Brittle. Please let me know. However, Publisher Windows STILL crashes attempting to open either file.

Are you using the latest release version? yes. 1.7.1.404 (here's how to check) Can you reproduce it?. Change any Image in my folder of Linked images, Does it happen for a new document? Don't know. No time to check. Windows 10. What happened for you . Resource Manager notifies that ALL files change, when only ONE has been updated. Provide a recipe for creating the problem. Change a File in Affinity Photo, for example. Save. Then publisher RM goes crazy. Screenshots (very handy) or a screen capture/video. Attached. Any unusual hardware. Not really, regular workstation.

I second that. It's not slight. It appears like 72ppi. On a 23in Dell 4k monitor with 191 pixel pitch, dropping down to 72ppi is like losing your pants in public. Awful. Looks great in Pub. persona! Photo Persona has a lower res anti-aliasing being applied to Text and Curves at normal zoom levels. I can't find any Preferences relevant.