thomaso

If there is 100 K only, no other colour in the document, a possible way is to export as Grayscale with Black&White as profile:

In addition to Brian's note that another nearby object may be snapping: In this screenshot the currently selected object seems to be snapping at the page edge: Or does the pink object have a black border assigned?

So your first 'culprit' (7A13) was not involved at all but just seemed to be for 1 hour? Good luck with the new suspect! – Can you upload this if it continues to be the culprit for quite a few hours of successful work in the affected .afpub? Just curious: why did you choose GIF as the replacing file type? (not PNG or JPG or even PDF for instance)

Was the AP document linked or embedded? Are there more instances of that Affinity document placed within the affected APub document … or any other Affinity document? Can you open their originals (not their instances in APub layout)? Do the placed documents use font files that aren't identical on the two computers? Can you exclude a font issue / corrupted font file?

Hi @wtbusiness, Welcome to the Affinity Forums! None of the 3 Affinity apps offers the creation of HTML & CSS for web sites which appears to be required for a flexible layout, displayed with variable font size and column width for instance. Web sites use "responsive design" to take into account the user's device + screen size + screen orientation when displaying content. If you want to publish the newsletter as PDF or PNG for instance AND get the layout & font size auto-adjusted on the various devices you might use/need a workaround by creating several layout versions, e.g. one for mobile (portrait format, larger fonts), one for desktop (landscape, smaller fonts) and ideally even a third version for tablets, each layout with suitable font sizes … and make the web site code decide to deliver the appropriate version to a specific device and user. Although you may create several versions of a basic layout with the support of APub's "Constraints" panel for multiple sizes and page orientation you would still need to export each version individually with its fixed size, aspect ratio and orientation. If you only create + publish one layout version, you will have to choose a compromise with a layout + sizes somewhere between the possible screen resolutions / sizes that either results in an optimal display for one device but is less useful for other devices, or in a layout and font size that may appear too large/too small on any device.

There might be a workaround for AD. (in APub it would be easy with Data Merge). 1. I'm using a vertically long document that can hold multiple vertical copies of the image. 2. Then I create one long text frame which contains the various text paragraphs with the leading set to the image height. (If each text has more than 1 line you need to use "Space after" additionally with reduced leading to achieve the image height as sum.) 3. The text frame gets nested inside the image layer. With "Lock Children" activated a duplicate of the image+text gets moved by the image height. Then with "Power Duplicate" the multiple copies should be easy. 4. In the Export Persona all copied image layers get selected + turned into slices with 1 click for export of all image copies with 1 click. Unfortunately I run into an issue: it seems with Power Duplicate (cmd-J) the active layer attribute "Lock Children" gets ignored. This feels like a bug to me – but possibly it got fixed in V2? (this not locking children also occurs when using multiple power-duplicated copies of Artboards, one for each image+text). duplicate & lock children.m4v

As usual "beauty" is a matter of taste. For text justification it concerns the balance of black & white (text, ink <-> blank, paper, gaps, spaces). Concerning "justification" it refers to the look of line end/start in left/right aligned text and to gaps in justified text. For justified text and apart from hyphenation it mainly focuses on "rivers" that may prevent a balanced gray (black vs. white). To detect those areas it helps to zoom out or look at the layout from a larger distance. It gets influenced by hyphenation settings + word / character space settings. The latter gets mainly set as Paragraph Style attribute (but may also get set as Character Style attribute, in particular for more individual adjustments, especially in short text or line length/column width). Affinity starts with a useful default spacing: Characters: 0% | Words: 80% / 100% / 133%. There are many web articles about these aspects, for instance:

… whereas the issue appears more problematic than usual issues because this doesn't get obvious neither in .afpub nor in an exported PDF. (… unless the user checks the TAC as you did in your video, which should not be necessary after assigning a profile to the document or for PDF export, especially for PDF/X). Do you know if this was ever (bug-)reported for V2 ? (… I never have noticed an according bug report for V1 and I have V1 only).

What a nasty issue. It also occurs to me in APub V1. After assigning the other document profile then switching the colour model in the Colours Panel does not refresh the image and TAC values (but applies a fill colour, even if the wells are set to none before). Instead I can either replace the image (which is not useful) or save + close + reopen the document to get the profile with correct colour values / TAC displayed. Without this additional workaround also an export shows the values of the former document profile (when placing the image) though PDF/X-1 is using the correct intent for export.

The current workflow for such issues asks users to change their current hardware acceleration setting to see if an issue they are experiencing still occurs. If this helps prevent the problem, the situation is considered resolved – regardless of a possible alternative culprit or solution. The mentioned self-test routine might work similarly with the corresponding conclusions. As Walt says, it doesn't seem useful or necessary to discuss any further details in the forum – nor is there any need to convince you.

If you have APhoto you could try the "Benchmark" feature to get an impression for your specific hard-/software configuration. Run it twice, 1x with Metal, 1x with OpenGL activated. https://affinity.help/photo2/English.lproj/index.html?page=pages/Extras/benchmark.html&title=Benchmark

I don't think that's quite right, at least for Windows. I can't follow your conclusion. The fact that faulty GPU driver software causes issues does not affect the question whether Affinity is fully compatible with Hardware Acceleration in general. If Affinity would be fully compatible then all these issues were caused by faulty OS or drivers but not by Affinity – which appears odd if you consider that apps and documents are coded for specifications given by the OS, not vice versa. For Windows it appears additionally confusing that Hardware Acceleration is an Affinity System Requirements although + while this feature in particular may need to get disabled by users in case of lacking compatibility. True, a feedback of screen rendering versus display might be required to control the reliability of both input + output. I assume such an interface exists already in particular for GPU or monitor development. But hardware acceleration not only causes rendering/display issues, but can also cause Affinity to freeze or crash, according to related posts. Could Serif use their existing "Benchmark" test code, perhaps augmented with display feedback, to provide a reliable recommendation for an "optimal" performance setting for any specific, individual hardware/software configuration?

The V1 preference files might still exist in your system folder. (The location depends on your operating system + its version + the used Affinity store for app purchase/installation). If you did not delete the related V1 folder then this two posts might help to get wanted V1 content transferred to V2:

… for what in particular?

Instead of searching for an Affinity(?) user or photographer or designer I used a search in the Affinity help, maybe that is what you are asking for? If not you might show, describe or link the wanted workflow or feature for more efficient forum response? https://affinity.help/photo2/English.lproj/index.html?page=pages/LiveMasks/mask_liveLuminosityRange.html&title=Live Luminosity Range Mask