Lee D

@Starbuck265Which workflow are you using to open your images? If you use Apple Photos consider the following workflows for opening your images. 1, Tap hold and drag the RAW file from Photos to our apps icon to then release. 2, Move you RAW files to cloud storage and import directly from that storage instead, this is the most common import method used.

Have you tried creating a new pixel layer above your source and setting it's mode to Darken. Then select the Healing tool is Affinity Photo, setting the dropdown to Current Layer and Below on the Context Toolbar. Like PS you then hold option and click to define a source area.

Hi @Jouvon Welcome to the forums. Have you found this also happens on a new document or only with a particular one? If only one could you possibly provide a download link to your .afdesign file and your workflow for me to test with.

A little confusion there on my part 😉

Hi @Simon Thorpe, welcome to the forums. You can hold the Shift key when using the Pen Tool, this will create straight lines, you get a yellow line indicate showing where the line will be, horizontal, vertical etc.

A blurry preview can occur if the source file isn't available. Have you double checked the source location to make sure that the source files are still available/in place?

This is already logged with our developers.

Not something I can replicate on one of our M1 iPad Air updated to iPadOS15.5, can you reproduce it on a new blank document as well?

This will be due to our importer not reading the included style sheet with the SVG file, this is logged with our developers to investigate.

Hi @Tim123 Welcome to the forum. What's your workflow that requires you to save to .Tiff with Affinity layers as these files can only be reopened using Affinity due to how the layer information is stored. If you've intention is to open and edit again you'd be better saving in our native file format (.afphoto). If you are sending to someone, that doesn't have Affinity Photo, exporting to PSD may be the better option.

Please try resetting the app back to defaults, hold down CTRL and open. A window should appear, release the key and click Clear. The error logs point to Kernelbase.dll which doesn't really narrow down the cause. Have you checked for a crash report, this may provide a little more information.

For opening/importing and saving our app uses the Files app built into iPadOS, so your SAN drive software would need to interface with this. However we don't control how the Files app displays the other locations directories/file structure.

Thanks for your report, I've passed this over to the developers to investigate further.

HI @Affinity_Pro Welcome to the forums. If you open the apps Preferences > Performance if you have the option to turn off Hardware Acceleration/Metal please do and then restart the app. If this fails open that section up again and make sure the Display is set to OpenGL.

Thanks for your report, I've logged this with our developers to investigate further.

@kamelus This isn't necessarily a bug but a workflow issue unique to your system. Can you expand on your workflow, is it a case of just having open multiple .afphoto files that this occurs or are you doing more with each of the files? Does the app itself crash? if so can you follow the steps in this FAQ article to retrieve a crash report from one of the those to upload here for checking. Can you also confirm your system spec including the version of Windows running.

@AnnMDo you have a previous save of the file that you can revert to? Also was you doing anything particular within the app that caused the issue, using a certain tool or feature? Can you reproduce the issue on a new document? You can try checking the following location to see if there is an autosave file available. Press the Windows Key + R to launch the Run dialog and enter the relevant app path: %AppData%\Affinity\Photo\1.0\autosave (For Designer, same as above just change Photo for Designer) Can you please confirm your system specs, including the version of Windows.

Our apps use DWM as it's always active in Windows, Disabling G-Sync should result in a smoother presentation. For your other queries they shouldn't have an impact on our apps. Is this something you've customized for any other apps similar to ours and what processes/methods did you use?

Hi @Susan shooltz Welcome to the forums. Are you printing direct from within Affinity or exporting to a file and importing this into an app that came with the printer? If direct from Affinity it should be a case of selecting the installed printer and the preset/settings required for the particular item as outlined by the printer maker (Epson). Are you using macOS or Windows?

The workflow I've used so far is: 1, Open your 000.afpub file in Affinity Publisher 2, Use File > Export > PSD 3, Open new 000.PSD in PS and edit, then use File > Save 4, Open 000.PSD back in Affinity, edits from PS shown, file has no other issues. Is this different to your and which apps are being used to edit our again or another?

If that's the case what workflow are you using that requires you to open the 1st exported PSD in Affinity again to then export out to PSD again? If you need to edit it why not open the original .afpub file?

I've tested exporting your file to PSD and reopening in our apps as well as PS and everything appears the ok on macOS and Windows. When exporting with preset are you selecting and are you changing any other options? How are you then previewing the exported .PSD file? 000.psd

This new version is working for me, can you test it yourself to make sure. I had to use Publisher to open the file and then use File > Edit in Photo and once in Photo resave to a new file. The file size is different so please check it over. 910219507_NewVer.afphoto

Hi @Walter B Welcome to the forums. We do have some reports logged that relate to IDML files, DPI and fonts, these are with the developers to investigate further. Apart from the workaround you've already used there isn't much that can be done as the importing of the file is done automatically. If it's possible to provide an example .IDML file that this occurs with I can test to confirm the issues and add it to the existing reports.

This is indented and isn't a bug. If you're currently viewing a master page and go to export you do have the option of changing the Area to the current page and exporting.