MEB

This workaround solved the problem for me, too. Great to know about this! 😀

Hi folks - I got a comment posted by Moderator MEB (which I now don't see) which included a link to an FAQ article - my issue was just resolved using the second item listed in that article:

"...If you do not have a Font Manager installed or do not have an excessive amount of fonts installed within macOS, please try going to the Apple menu 🍏  > System Preferences > General > Recent Items to None and try our app again..."
This solved the issue completely and I'm able to save and save as entirely normally now.

Here's the FAQs link MEB provided:
This DOES point out that somewhere in the core Affinity code there's a non-fault-tolerant system which is looking for or at data provided by or to the OS on recent saves, and cannot handle either lag or lack of data. It's clear this is not true of other apps - I use a wide range of 3D generalist tools, CADD tools and other graphics tools, and sadly only Affinity showed this issue.

I AM glad it has a simple workaround.
Thanks to all the mods involved in this one!

Hi PrimozRome,
Welcome to Affinity Forums :)
Select the black and white image/layer and go to menu Layer ▸ Rasterise To Mask. You can then attach/nest it to the image/render by dragging it over the image/render's thumbnail until a blue vertical marker appear (in the Layers panel).

Hi @mann, @Dan C
This issue is not related with the distance from the text but with a bug that generates a rectangular wrap outline around the rounded text frame in certain circumstances (which I'm logging now). The clip shown above doesn't not fix the issue, just disguises it. If you delete the red rounded rectangle after the steps shown in the video you will see that the text still doesn't wrap around the rounded corners of the grey rounded picture frame. This is because it has a rectangular wrap outline applied to it preventing the rounded parts from being filled with text. You can check this if you select the grey rectangle and click the Edit Wrap Outline button - the wrap outline shows a rectangle. To fix the issue you must press the Reset Outline Button to force the wrap outline to take the form of the rounded picture frame (again you can check this pressing the Edit Wrap Outline button again - it is now a rounded rectangle) and thus the text can now fill the rounded areas of the grey picture frame.

So to truly fix the issue you only have to select the rounded grey picture frame and click the Reset Outline Button in the main toolbar. Delete the rounded red rectangle and red rounded paths since they are not required.

To correct my previous posting: the information that I had read on line yesterday is clearly wrong: On1 RAW does not support tethered streaming for Fuji cameras.  I wrote to On1 RAW to ask, and received the following reply:

Hello, 
Thank you for contacting ON1 Support.

We do not have support for tethered shooting with Fuji cameras.

Currently only Canon and Nikon cameras.

We appreciate your interest in ON1 PHOTO RAW and are always looking for valuable user feedback and suggestions.

I have forwarded on your comments to our product team for further review and consideration.

For future reference, please visit our ON1 Photo RAW page for feedback and feature requests where you can submit ideas that are then voted on by the community for possible inclusion in a future release.

https://www.on1.com/products/photo-raw/ideas/

We appreciate you taking the time to contact us.

Let us know if we can be of further assistance.

 
Stevie | Tech Support & QA Engineer

Hi @SylwesterD,
Thanks for the screenshot. You have the Blend Mode in the context toolbar set to Darken. Please set it to Normal.
You may also want to turn the Wet Edges option off as it affects the opacity and edges of the painted strokes.

Hi @SylwesterD,
Thanks for the screenshot. You have the Blend Mode in the context toolbar set to Darken. Please set it to Normal.
You may also want to turn the Wet Edges option off as it affects the opacity and edges of the painted strokes.

Hi @thegary,
This is a known issue that's already logged to be looked at. Thanks for raising it up though.

Hi @Bikr,
Welcome to Affinity Forums
Thanks for your feedback. We are investigating these issues. Meanwhile, duplicate the Affinity Photo.app file, delete or the original app file to something else, then rename the duplicated app file (remove "copy" from its name) and launch the app. This seems to fix the slow start/bouncing until we find out what's causing the issue.

Hi @Jen1234,
Welcome to Affinity Forums
Thank you for your feedback. I've updated/bumped the report to bring it up to management/development attention. It's up to them to decide what issues and when should be fixed first. Thanks for understanding.

Hi @Josan,
Welcome to Affinity Forums
The file without the resources seems to load correctly. Maybe the issue is with one of the images/resources in the document? Try renaming the folder where you have the assets for this document then load the file you attached in your post above. Reply "No" when asked about locating the missing resources. Does it load the document or still crashes for you?

Today’s update did the trick, thanks. 👍🏼

My apologies @ashf. You did mention placed images in your report (just checked). Not sure what's going on then. Better wait for Mark Ingram's comments. In any case the bug related to placing images do remain open.

Hi @awakenedbyowls,
Because you have applied a linear gradient transparency to the group that contains the planet and the rings (thus affecting all contained within the group). Select the saturn group then switch to the Transparency Tool as you should see the transparency handle on canvas and how it affects the planet.

Hi @ashf
I believe @Mark Ingram was referring to loading in the other thread, not placing. As you noticed there's a bug report for this thread which deal with placed images specifically and that still remains open in our logs.

It may be that you think the export quality of PNG is perfect. That is not yet a reason to portray other opinions as ridiculous.

It seems someone is obsessed with non-existing issues of export quality. Started with font rendering, now switched to circles. What will be next? Issues with raster export of heart symbol?

I'm aware of what shared memory is/how it works/what benefits it has performance wise. I still think that buying a system with 16 Gb of shared memory (non-upgradeable) which is supposed to last a few good years for someone creating large artwork is not a great investment for future.

I'm aware of what shared memory is/how it works/what benefits it has performance wise. I still think that buying a system with 16 Gb of shared memory (non-upgradeable) which is supposed to last a few good years for someone creating large artwork is not a great investment for future.

Hi @furyeffect,
Welcome to affinity Forums
This is working correctly (with a mouse at least, i still have to check with the Wacom) but there's some key modifiers conflicts going on in certain circumstances.

Please try this with the mouse first (Magic Mouse): press both ctrl and command simultaneously then click on the object to display the menu you are looking for. Make sure that no other object/layer is selected when you try it and ideally click on a group that contains some objects inside as in the video below. Can you see the menu? If not let me know.
menu.mp4

Hi @Baan,
Welcome to Affinity Forums
Thanks for your report. This is an issue we are already aware of. I've updated/bumped our log to bring it up to developers attention again.

Hi macalienx,
Go to Affinity Designer ▸ Preferences..., Tools section and uncheck Enable Canvas Rotation with Trackpad.

Hi @chris.da.rule,
Welcome to Affinity Forums
Affinity doesn't perform any optical character recognition when loading PDF's. It's simply loads what's contained in the PDF (text if any and embedded fonts/font information plus images etc). The files you provided above are just scanned images - they do not contain any editable/selectable text. To make the text editable you must run the PDF through an OCR app first. Not sure yet why the second document is giving a parsing error.

Thank you @walt.farrell I am following the news in Apple land and waiting for more info. They are going launch what seems like the have the name "Mac Studio", what will be there line-up for content creators. Will see about that. M1 or M2, it is very different than x86. Specially the shared memory is so different. 

Thats why i am very courious how people using these machines experience these the speed when they work in huge heavy (vector) files.

Hi @mimi123,
Welcome to Affinity Forums
Affinity apps do not support gradient meshes. I'm afraid there's no way to work around this, sorry.