Dan C

Oh wow, i should have come to the forums from the get go...i didnt know these videos existed...thanks!

There is more to the above issue than simple wording - as I understand it the reason an Artboard is described as a Rectangle is due to the way Artboards are programmatically used in Affinity.
Essentially when exporting Artboard documents, all containing layers are exported nested within a vector 'Rectangle' in order to be compatible with vector formats that don't understand the concept of an 'Artboard' outside of Affinity.
I am not claiming this issue cannot be fixed, but it is important to know this is more than a simple UI error and is actually displayed as such due to how Artboards are created in the backend code of the Affinity apps.

Thanks for letting us know @凌剑君 & I'm sorry to see this issue is yet to be resolved by our translation team. I have 'bumped' this issue with the team to bring it to their attention once again so it can be resolved as soon as possible.
I've replied in the linked thread regarding this separate issue - as it's not as 'clear cut' as you might expect.

There is more to the above issue than simple wording - as I understand it the reason an Artboard is described as a Rectangle is due to the way Artboards are programmatically used in Affinity.
Essentially when exporting Artboard documents, all containing layers are exported nested within a vector 'Rectangle' in order to be compatible with vector formats that don't understand the concept of an 'Artboard' outside of Affinity.
I am not claiming this issue cannot be fixed, but it is important to know this is more than a simple UI error and is actually displayed as such due to how Artboards are created in the backend code of the Affinity apps.

Dual Lighting is a cool effect that can add some extra punch to your images. Today we’ll look at how to create such images in Affinity Photo (and Designer), and also check out how to create good base images in MidJourney. 
 
 

Absolutely, please see the latest update to this issue here:
We hope to release 2.3 as a customer beta as soon as possible

I updated the suite right now to version 2.2.1. 
App wide color settings are stable now and changing document profiles works as it should.
Thanks.
I now will enjoy the new features of 2.2 😊

If you look at the post just above yours, from the Serif Info Bot, the issue is fixed in 2.3.0.2083. The update you just installed is for 2.2.1.2075, which would not have the fix. When 2.3.0 is available for beta testing, you could try it there, or wait for the 2.3.0 official release.

Disregard I was able to get it working. It was an iCloud Drive sync setting that I needed to turn on. Thanks for your help!

Looks like removing the FX was the trick! The printer says he can make it work now.
 
Thanks for the help fellas

I can confirm our team have replicated this issue here and it stems from the same failure of reading these installed ICC profiles correctly.
I've covered this further in the below FAQ - 
Both issues are logged with our team and we're working to resolve these ASAP

Hi @GoVicinity & @FotobobJP,
Thanks for your reports and my apologies for the delayed response here!
 
Just to confirm, I have logged these issues with our developers - firstly the error message shown is incorrect and should reference the inability to write a ~lock~ file in this location. Secondly, the apps should open these documents in a 'Read-Only' state, and when attempting to Save any changes should provide the 'Save-As' dialog and prompt the user to save to a new location.
However thus far I've been unable to replicate this behaviour using Read Only folders within Finder - though I must admit I am not using Virtual pCloud folders in my testing. Can you provide any more information regarding the exact steps you're taking and they folder structure you have when these links are 'lost'? 
Many thanks in advance 

Unfortunately this issue remains open with our developers at this time - I can confirm that the reason this dropdown is not working currently is due to a bug that Apple have introduced in macOS Sonoma, as it affects both V1 & V2 of the Affinity apps.
Our team are aware of the importance of this issue and we're working to resolve this as soon as possible. Our apologies for any inconveniences caused due to this in the meantime.

For the record, the flickering of my TIFF Epson scans hasn't been fixed in 2.2.1 yet.

Thank you trying these steps for me - it's certainly interesting to hear that the same occurred with v2.1.1, indicating the crashes are not a programmatical error in v2.2 specifically.
 
Our team currently believe that the fact DDU is unable to run and you've been unable to login to this newly created user indicates a wider issue on your machine that isn't directly related to Affinity.
Unfortunately at this time we can only suggest generic Windows 11 repair options, such as those in the link below, in the hopes this resolves the multiple issues occurring with your machine -
https://www.thewindowsclub.com/how-to-repair-windows-11
My apologies that I do not have any further specific advice for you at this time. 

Unfortunately there's no option for this in Affinity currently, you would need to open each 'tab' and use Export individually - our apologies!

Update from OP
one of my games failed to work and I discovered there’s a bug with GeForce Experience where it installed a developer build driver. Rolled back to the current stable driver and it fixed Affinity for me.
Thank you everyone for your time and I’m glad this thread could help others!

Thanks Mate! ill try sending this as a pdf to my printer and see what he thinks *fingers crossed*

Hi @mpstaton,
Thanks for your post!
If I've correctly understood your requirements, you can achieve this by simply Grouping your multiple vector objects, then applying a Gradient using the Gradient Tool to the Group layer, which will reflect the gradient through all objects within, without the use of Mask layers -
2023-10-16 11-12-53.mp4  
Does this achieve the results you're looking for please?

Thanks for your report @Affinity-Inspiration!
As mentioned in your thread here, this is expected behaviour in the Affinity apps, as we don't currently recognise the 'long press' action when using the Apple Pencil -
There are a few things happening here -
Firstly the 'Quick Actions' menu will only appear with a long-press on screen, and therefore will only work with your finger to open this menu, as above.
Secondly, the 'Delete' option here acts the same as the Delete icon on the left hand toolbar and will not delete rows/columns, it should simply delete any text contents of the cell(s) you have selected.
The pop-up menu with these options can be triggered by tapping once on the right hand side of any Row / Column label - which is the same behaviour as on desktop. Due to this being a singular 'tap' to open the menu, it can be achieved using either a finger or the Apple Pencil.
I can see the cause of the crash in your recording, after deleting the first column, the app does not correct select the next column in the table, instead only selecting the first cell. When then selecting delete column with only the first cell selected, the app crashes. I'll be logging this as a bug with our development team now.
I hope this helps

'Fenster' is the Window menu, not View menu - so I'm not sure why OP mentioned the View menu in their post.
From what I understand, the 'Fenster frei Vercheibbar' menu item referenced above is actually 'Ansicht als frei verschiebbares Fenster' within the 'Fenster' menu, which is the German Translation for the Float View to Window option in the Window menu.

Hi and welcome to the forums. Unfortunately, this is a known issue with Affinity.
As a workaround, you can use the History panel to undo the extra step.
 

Affinity V2 uses the Hunspell Engine for spell checking and it also allows for additional Hunspell dictionaries to be added. You can download additional dictionaries from LibreOffice's GitHub page here but you can find direct links in the last post here. 

Once you've downloaded the correct file(s), you can use them in Affinity V2 by following the below instructions:
Please note: There are some differences between how you install Hunspell dictionaries for macOS/Windows, since we use the default spelling dictionaries available within macOS but it's also possible to add custom Hunspell dictionaries too.
macOS
macOS includes spelling dictionaries for many languages and hyphenation dictionaries for a few languages, which will already be available in Affinity V2.
To view the available spelling dictionaries, open the Character Studio within the Affinity V2 app, then expand the Language section and click the Spelling dropdown menu.
To view the list of hyphenation dictionaries, click the Hyphenation dropdown menu below Spelling in the Character Studio.
If the spelling or hyphenation language you require is not available in macOS and therefore not already listed here, you can install standard Hunspell dictionaries to use within Affinity V2.
To install a spelling dictionary, copy the required xx_XX.dic and xx_XX.aff files within Finder to:~/Library/Spelling/
To install a hyphenation dictionary, create a new subfolder in ~/Library/Spelling/
Name this subfolder using the format of xx_XX (replacing xx_XX with the language's locale id, for example fr_FR for French) and then copy the hyph_xx_XX.dic file into this folder.
If the spelling dictionary for the language you are adding a hyphenation dictionary for is already available in macOS, please do not also manually install the spelling dictionary, you should only need to manually add the hyphenation subfolder and file.
Please note: Any changes to dictionaries require that you restart Affinity V2 for these to be detected/updated.
Windows
Affinity V2 on Windows includes spelling & hyphenation dictionaries for some languages by default, though typically this is less than is available on mac, due to the use of macOS provided dictionaries, which aren't provided by Windows in the same manner.
To view the available spelling dictionaries, open the Character Studio within the Affinity V2 app, then expand the Language section and click the Spelling dropdown menu.
To view the list of hyphenation dictionaries, click the Hyphenation dropdown menu below Spelling in the Character Studio.
If the spelling or hyphenation language you require is not provided with Affinity V2 on Windows and therefore not already listed here, you can install standard Hunspell dictionaries to use within Affinity V2.
You can add additional dictionaries and hyphenation dictionaries by going to Edit > Settings > Tools.
The default Additional dictionary folder used by the app is C:\ProgramData\Affinity\Common\2.0\Dictionaries but you can change this location by clicking Browse...
It is not necessary to change this default folder location within the Affinity V2 app, but if you do, please make sure that you specify a folder here that holds all subfolders for each locale and not one specific locale folder as this will not work!

To copy any downloaded dictionaries and hyphenation dictionaries to the Additional dictionary folder click Open... but before copying your files to this folder you will need to create a subfolder with its name in the format of xx_XX ( substituting xx_XX for the locale id ). Once you’ve done this you can copy your xx_XX.dic, xx_XX.aff and hyph_xx_XX.dic files to the subfolder. Now restart Affinity V2 for the dictionaries to appear within the app.
_______________________________________
For example, with the default folder used under Settings > Tools, you should see this folder path within the Affinity V2 app and not a specific locale folder:
C:\ProgramData\Affinity\Common\2.0\Dictionaries

You should then have created a folder within the 'Dictionaries' folder in File Explorer, using the locale ID - for example with English Canadian:
C:\ProgramData\Affinity\Common\2.0\Dictionaries\en_CA

Within this folder should be the relevant .dic, .aff & hyph.dic files, downloaded from the post below. This should appear as follows 

Please note: Any changes to dictionaries require that you restart AffinityV2 for these to be detected/updated.

Known Issues -
French (Canadian), French (Belgium), French (Luxembourg) & French (Swiss)
When importing text from external apps, such as Word or LibreOffice, that use these languages, Affinity will show a warning for a missing dictionary.
From our research, individual Spelling/Hyphenation dictionaries do not exist online for these languages, so instead it appears as though these third party apps will simply use a French (French) dictionary in order to provide Spelling/Hyphenation support, assumedly through the use of symlinks.
As the Affinity apps don't currently support symlinks for dictionaries, we instead recommend manually installing the French dictionaries from the above provided links, but changing the Language code of the downloaded files and folders as required.
For example, if you see a warning regarding a missing fr_CA (French (Canadian)) dictionary when importing text, please download the above fr.aff, fr.dic & hyph_fr.dic files.
Once downloaded, rename these files to fr_CA.aff, fr_CA.dic & hyph_fr_CA.dic respectively and then add them to the required location/language folder on your OS, using the above instructions.
These steps are also true for the other languages listed above, substituting the language code (fr_CA, fr_BE, fr_LU or fr_CH) as required.
Once you have installed the French dictionary files using these language codes, you should find the relevant Spelling/Hyphenation options can now be selected in Affinity and the missing dictionary warning is no longer shown.
German (Swiss), German (Austrian) & Belorussian
When downloading dictionaries for the above languages, some of these files have filenames which require amending.
For German (Swiss) and German (Austrian), the files are suffixed with '_frami'.
For Belarussian, the files are suffixed with '_official'.
Before installing the dictionaries for these languages, we recommend deleting these suffixes and not including them within the language code for any folders created.
For example:
German Swiss files are named 'de_CH_frami'. After downloading, rename the file(s) to 'de_CH'  and create the folder using this code.
Belarussian files are named 'be_official'. After downloading, rename the file(s) to 'be' and create the folder using this code.

Thank you, Dan, for all the advice. I will begin working my way through it. I like the last best: returning to the EXE versions! I will keep you posted.