Dan C

No problem at all, I'm very glad to hear this As Walt mentions above, we've release 2.2.1 today and you can find the list of bug fixes in this version here: We're working to release a 2.3 beta as soon as possible for users signed up to our beta program but I'm unable to guarantee any specific bug fixes until the beta is released - or until the 'Serif Info Bot' posts in any thread to confirm a fix. At this time, the issue reported here is still logged with our developers (this is logged as a 'regression' as it is a new bug introduced in 2.2 with the update of 'PDFLib', the Library Affinity uses to export to PDF) and therefore should hopefully be addressed as soon as possible. I hope this clears things up!

Welcome to the Affinity Forums @FranciscoRiojas As Garry has mentioned above, please try opening your SVG in a separate application, as the viewer you are using may be applying this white matte to your file. If the issue continues, can you please provide a copy of your .afdesign file here for me, so that I can investigate further? I'm a little confused by the above statement also, I suspect that you mean a different format that you have had no problem with previously? Many thanks in advance!

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

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.

Many thanks for trying all of these steps for me and I'm very sorry to hear this behaviour has continued. I've escalated this issue internally with our team as I'm unsure of why the apps are acting in this way for you, so I'll be sure to respond here ASAP with any further suggestions we have. In the meantime, I appreciate new crash reports are not being generated by the app, therefore would you be able to produce a new Event Viewer log, following the same steps as before, to see if there is any further indication of a cause to the right-click context menu crash you can replicate across multiple users? Again this is not something being reported by other users or replicable directly by our team at this time, indicating a potential local issue to your machine but hopefully the Event log will be clearer in this regard

Hi @Kamui, Welcome to the Affinity Forums & thanks for your report! I'm getting this logged with our development team as the behaviour doesn't seem quite correct to me - and doesn't match the behaviour on the Desktop. However in the meantime, you should be able to achieve this by creating your selection of the table cells, Copying, then creating a selection of table cells where you want to paste the content to and then use Paste - you should now find this pastes the data between multiple cells as required: RPReplay_Final1697645532.MP4 I hope this helps

Thanks for your report @Darner! I believe you're referring to the 'Rights' section in the Metadata Studio within Affinity Photo, though unfortunately I don't understand the issue you're reporting based on the above. Can you please expand on your exact workflow for me? If possible, a screen recording would also be helpful

My apologies - I will DM you a direct link to download the file on Dropbox now through the Forums, as I'm unsure why this isn't being correctly received externally currently!

'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.

Please find attached a 'fixed' version of your file, which no longer uses any FX and can be exported to PDF with vector layers, which can then be imported into Illustrator. There were a few oddities with your file, such as the document using a 32bit HDR colour space (which is unusual for a label) as well as a few issues with the text objects, so I have recreated these. Please carefully double check this file to ensure you are happy with my changes before sending to print etc. Metalic Base_F.afdesign I hope this helps

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

Hi @accesstime, Thanks for your report! Unfortunately I've been unable to replicate this behaviour here currently - though this may be occurring due to your Layers hierarchy in your specific file. I appreciate you mention this is an intermittent issue, but if you are able to provide a screen recording showing this happening, we should be able to investigate further. If you're unsure how to take a screen recording, please check out our FAQ linked below - Does this occur with seemingly any asset, or only specific ones? Are your Icon Assets purely vector, or a mixture of pixel and vector content? When this next occurs, I'd recommend checking the layers Opacity in the Layers Studio, to ensure this has not accidentally been reduced - equally you can use the Transform Studio to see the current X,Y,H&W values for the selected object, which also may provide some insight as to the objects location in your document. Many thanks in advance

Thanks for reporting this issue and letting us know the solution you used to resolve this. This isn't an issue I've seen reported previously and thus far I have been unable to replicate this behaviour here. If you find a consistent way to 'trigger' this issue occurring on your mac, please do let us know and I will be happy to report this to our developers! This likely depends on the specific 'preferences' you deleted, as the app stores settings in multiple locations on your Mac and I don't believe any of the 'CTRL' run up reset options would directly affect this setting.

Your post in 'Bugs' was a duplicate of your 'Questions' thread, which was posted first and updated as [SOLVED] with your findings shortly after. Please do not create duplicate threads across multiple sections of the Forums - this can cause delays in our support team replying and is not required. I'll be locking this thread from further replies, and we'll continue to support/discuss this issue within the original Questions thread below. Any further duplicate posts may be removed without warning, and this applies to all Forum members.

I'm very sorry to hear this Dave! Out of interest, do you have a clipboard manager or similar app that may be interfering with the paste/context menu within Affinity? I'd also like to suggest a few more options, to see if we can specifically pinpoint the cause here. 'Roll back' to version 2.1.1 - now you have the 2.2 EXE version installed, we can technically install 2.1.1 MSIX at the same time, provided the apps aren't open simultaneously. We don't recommend this long term, but can be useful for testing purposes. Of course any of your saved 2.2 documents won't be compatible within this version, but I'm interested to know if 2.1.1 is legitimately more stable for you and the crashing you're experiencing is directly related to the 2.2 update - or if this is simply coincidental timing with the latest release. Create a new user account - if you are willing, I'd be interested to know how the apps behave on your PC within a new user account on Windows. Once you've created the account you can install the version 2.2 Affinity apps and use your Affinity ID to license the apps (as you would normally) and then using either a new document, or continuing with the files you're using above where you're experiencing issues, test the app to see if they remain as unstable as they are on your regular account./ This could help determine if the cause of the latest instabilities within Affinity on your PC are related to additional third party apps you may have installed, your user profile configuration, Windows OS settings etc. Should the same issues occur in a new user profile, and not within 2.1.1 then this would give much more credit to the possibility of a wider issue within version 2.2 that I could report to our development team for further investigation

Thank you for your continued patience here - I've been doing further testing and investigating with your files and I have found the following: __________ 1. There is an issue with your 'Original MASTER.afpub" files provided in regards to the file size and opening times in the Affinity apps. Opening this file on my mac took a considerable amount of time (over 60 mins), used 33GB+ of RAM (memory) and read over 175GB worth of data from the disk. This is never expected with an Affinity document and indicates a larger issue with this specific file that I can't personally locate - therefore I have logged that specifically as a bug with our developers to be investigated further. I believe this is the same issue underlying issue causing the files inability to be 'reduced' in physical size - as I have deleted all pages & master pages from the document, essentially leaving a file with a singular blank page and the size of the saved .afpub file did not reduce. I have noted this within the development report for your file. __________ 2. Following the below steps with your V1 files (in both V1 & V2) I'm not seeing the additional masters being created - though this may be due to a misunderstanding in your workflow, as I do not mind admitting I've had a little trouble understanding the PDF file provided with these files. The steps I've followed are as such: Open "V1 2024 BUJO Master 0 Pages.afpub" Select "Master BUJO Links.xlsx" in Data Merge manager to relink Set Sheet to "MergeFutureLog" All Records, Merge Enabled, All Pages Generate from Data Merge Save generated document Return to "V1 2024 BUJO Master 0 Pages.afpub" Add pages from file - select recently generated/saved doc Add All Pages, Before Page 1, Discarding unused text styles (❌) No new masters added to file? Delete Page 2 (was Page 1) Add new Page using "00 Year by Months LinP DM" master Data Merge Manager Set Sheet to "Merge Year Calendar", All Records, Merge Enabled, Page Range 2-2 Generate from Data Merge Save generated document Add Pages from file - select recently generated/saved doc Add All Pages, After Page 2, Discarding unused text styles (❌) No new masters added to file? Am I misunderstanding the workflow you've described within the PDF provided for the V1 files? If so, could you point out amendments to the above steps that would replicate this duplicating masters issue? I did not continue past the first two Merge > Save > Add Pages from File attempts, as neither of these created duplicated masters and therefore I determined my workflow must be missing something. __________ 3. As I wasn't yet able to replicate the duplicating of masters, I don't believe I'm seeing the same file size increasing on 'Add Pages' that you've reported also. When adding the merged result document to the 'parent' .afpub file and saving it, the file size does increase slightly - but this is expected as new page(s) have been added to the document, from the merged files. Again I suspect that I'm not seeing the reported issue directly due to misunderstanding the workflow causing your duplicated masters. __________ Hopefully with the correct steps for point 2 above, I'll be able to replicate both issues reported and log these with our developers also. I look forward to hearing from you here

Many thanks for providing these for me - I have logged this as a bug with our development team to be investigated further and they will use the files/information provided to work to resolve these crashes in a future update, as this is unlike anything we've seen previously. In the meantime, as we're unable to replicate this internally - even on an Ultrawide monitor, currently our best suggestions are either to continue to use 150% scaling within Windows, or not to 'full screen' the Affinity apps. My apologies that I don't have any further resolutions at this time, but I will be sure to update this thread with any information or suggestions that our team can provide

Please find below direct links to the Hunspell dictionaries. To download a file, right click the link and select Save Link As... (In Safari, select Download Linked File As... but do not select Download Linked File or .txt will be appended to the filename.) af_ZA af_ZA.aff af_ZA.dic hyph_af_ZA.dic an_ES an_ES.aff an_ES.dic ar ar.aff ar.dic be_BY be-official.aff be-official.dic hyph_be_BY.dic bg_BG bg_BG.aff bg_BG.dic hyph_bg_BG.dic bn_BD bn_BD.aff bn_BD.dic bo bo.aff bo.dic br_FR br_FR.aff br_FR.dic bs_BA bs_BA.aff bs_BA.dic ca ca-valencia.aff ca-valencia.dic ca.aff ca.dic hyph_ca.dic cs_CZ cs_CZ.aff cs_CZ.dic hyph_cs_CZ.dic da_DK da_DK.aff da_DK.dic hyph_da_DK.dic de de_AT_frami.aff de_AT_frami.dic hyph_de_AT.dic de_CH_frami.aff de_CH_frami.dic hyph_de_CH.dic de_DE_frami.aff de_DE_frami.dic hyph_de_DE.dic el_GR el_GR.aff el_GR.dic hyph_el_GR.dic en en_AU.aff en_AU.dic en_CA.aff en_CA.dic en_GB.aff en_GB.dic hyph_en_GB.dic en_US.aff en_US.dic hyph_en_US.dic en_ZA.aff en_ZA.dic eo eo.aff eo.dic hyph_eo.dic es es_AR.aff es_AR.dic es_BO.aff es_BO.dic es_CL.aff es_CL.dic es_CO.aff es_CO.dic es_CR.aff es_CR.dic es_CU.aff es_CU.dic es_DO.aff es_DO.dic es_EC.aff es_EC.dic es_ES.aff es_ES.dic hyph_es.dic es_GQ.aff es_GQ.dic es_GT.aff es_GT.dic es_HN.aff es_HN.dic es_MX.aff es_MX.dic es_NI.aff es_NI.dic es_PA.aff es_PA.dic es_PE.aff es_PE.dic es_PH.aff es_PH.dic es_PR.aff es_PR.dic es_PY.aff es_PY.dic es_SV.aff es_SV.dic es_US.aff es_US.dic es_UY.aff es_UY.dic es_VE.aff es_VE.dic et_EE et_EE.aff et_EE.dic hyph_et_EE.dic fr_FR fr.aff fr.dic hyph_fr.dic gd_GB gd_GB.aff gd_GB.dic gl gl_ES.aff gl_ES.dic hyph_gl.dic gu_IN gu_IN.aff gu_IN.dic gug gug.aff gug.dic he_IL he_IL.aff he_IL.dic hi_IN hi_IN.aff hi_IN.dic hr_HR hr_HR.aff hr_HR.dic hyph_hr_HR.dic hu_HU hu_HU.aff hu_HU.dic hyph_hu_HU.dic id id_ID.aff id_ID.dic hyph_id_ID.dic is is.aff is.dic hyph_is.dic it_IT it_IT.aff it_IT.dic hyph_it_IT.dic kmr_Latn kmr_Latn.aff kmr_Latn.dic ko_KR ko_KR.aff ko_KR.dic lo_LA lo_LA.aff lo_LA.dic lt_LT lt.aff lt.dic hyph_lt.dic lv_LV lv_LV.aff lv_LV.dic hyph_lv_LV.dic mn_MN mn_MN.aff mn_MN.dic hyph_mn_MN.dic ne_NP ne_NP.aff ne_NP.dic nl_NL nl_NL.aff nl_NL.dic hyph_nl_NL.dic no nn_NO.aff nn_NO.dic hyph_nn_NO.dic nb_NO.aff nb_NO.dic hyph_nb_NO.dic oc_FR oc_FR.aff oc_FR.dic pl_PL pl_PL.aff pl_PL.dic hyph_pl_PL.dic pt_BR pt_BR.aff pt_BR.dic hyph_pt_BR.dic pt_PT pt_PT.aff pt_PT.dic hyph_pt_PT.dic ro ro_RO.aff ro_RO.dic hyph_ro_RO.dic ru_RU ru_RU.aff ru_RU.dic hyph_ru_RU.dic si_LK si_LK.aff si_LK.dic sk_SK sk_SK.aff sk_SK.dic hyph_sk_SK.dic sl_SL sl_SI.aff sl_SI.dic hyph_sl_SI.dic sq_AL sq_AL.aff sq_AL.dic hyph_sq_AL.dic sr sr-Latn.aff sr-Latn.dic hyph_sr-Latn.dic sr.aff sr.dic hyph_sr.dic sv_FI sv_FI.aff sv_FI.dic hyph_sv.dic sv_SE sv_SE.aff sv_SE.dic hyph_sv.dic sw_TZ sw_TZ.aff sw_TZ.dic te_IN te_IN.aff te_IN.dic hyph_te_IN.dic th_TH th_TH.aff th_TH.dic tr_TR tr_TR.aff tr_TR.dic uk_UA uk_UA.aff uk_UA.dic hyph_uk_UA.dic zu_ZA hyph_zu_ZA.dic

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.

It's possible that this size increase is due to metadata being exported with the JPEG from Affinity, which may not be included with the original image. The same is true for the Colour Profile, which may not be embedded in the imported image. I'd recommend unticking the relevant options for embedding metadata and colour profiles when exporting your images in order to maintain a smaller file size - though do please note that the above information is still correct and image sizes are bound to change based on the composition of the image, the export compression & algorithms used, etc, all of which is expected behaviour and not a bug. I hope this clears things up

Many thanks for providing these for me! Your Event Viewer logs show that Windows Explorer is hanging, and shortly after the Affinity apps crash in System.IO.FileSystemWatcher - essentially meaning Windows is having trouble with your file system and the Affinity apps then try and access this hung process, which in turn causes the Affinity apps to crash. Windows Explorer hangs can happen for many reasons, so I'd recommend the following: Update Windows - it appears as though you are using a Windows version which has since been patched, so I'd recommend installing the latest version through Windows Settings Run Windows SFC tool - Windows covers this process here, as you are running Windows 11 you can skip step 2 (DSIM): https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Update your GPU drivers - this is a recommended step according to a few sites reporting on exporer.exe hangs, and we always recommend running the latest drivers for Affinity. You can find the latest drivers for your Intel i5-10400 here: https://www.intel.com/content/www/us/en/products/sku/199271/intel-core-i510400-processor-12m-cache-up-to-4-30-ghz/downloads.html Finally, I can see you are using the MSIX version of the Affinity apps, which can occasionally have a harder time accessing files/folders on your system due to the Sandboxed nature of MSIX apps. Therefore I'd recommend uninstalling the MSIX versions (this can be done through Windows Settings > Apps & Features) and then installing the EXE versions from the below links, selecting the "Also Available : EXE" download options for each: Photo - https://store.serif.com/update/windows/photo/2/ Designer - https://store.serif.com/update/windows/designer/2/ Publisher - https://store.serif.com/update/windows/publisher/2/ Please do let me know how you get on here

Thanks for letting me know and I'm sorry to hear this! I've resent the document through Dropbox using the email address your Forum account uses - you should hopefully receive this email shortly, which will have a download link to your file

Each update we release will iterate the 'file version' for Affinity documents. This has always been the case, including V1 updates. For example; v1.8 documents cannot be opened in v1.7, v2.1 documents cannot be opened in v2.0, v2.2 documents cannot be opened in v1.10. Therefore there is nothing 'special' in this regard to v2.2 and v2.1 files, simply files opened and saved in any later version of the Affinity apps cannot be opened in a previous version. A warning will only be shown when trying to open a file in a previous version of Affinity, that has since been saved in a later iteration of the apps. This warning appears as follows: I do not expect that any of the issues you've reported above are specifically due to using 'v2.1 template' files within Affinity v2.2.

Hi @ashr, Welcome to the Affinity Forums I can see you have also directly emailed our support team - please refrain from contacting us through multiple channels at once as this can cause delays to you receiving a response. In regards to the issue reported, we've replied via email and we'll continue to support you there. I hope this clears things up.

As you've mentioned, both the tutorial provided and example screen recordings (such as the one from myself) in this thread show this feature is present and works correctly when following the described workflow. Therefore I'm not certain why this would lead you to such a conclusion. This is not true, and again directly contradicts the screen recordings provided in this thread. Your workflow is still not correct, as the Place Studio does not appear in any of your recordings You are not holding down shift when navigating to File > Place. You are instead 'shift-selecting' your Pages in the Pages Studio, before using File > Place. This is not needed, as you do not need any active selection of Pages or Layers, which Walt covered previously - Please make sure you have deselected the Pages in the Pages Studio, and your Layers in the Layers Studio as requested. Now, make sure you are holding down the shift key and continue to keep this pressed. Navigate to File > Place, with the Shift key still held. You'll now see a Windows Explorer dialog open, prompting you to select the file to place. At this point you can let go of the Shift key and select the PDF to be placed. If you follow this workflow correctly, you'll see the PDF appear in the Place Studio. The 'top bar' can then be found in the Place Studio and can be expanded by selecting the triangle icon - This is the workflow shown in my recording, and described in the post from Seneca in this thread previously: Please make sure you are following all steps, as have been reiterated a few times within this thread and the feature will function correctly.