Dan C

Hi @Evgenii, Thanks for your report - I can confirm this issue is still logged with our development team at this time. The officially logged bug is due to Affinity not supporting 'morx' tables with fonts, which causes this issue when exporting. Our dev team have confirmed that adding support for these font tables are unfortunately no small task and although this is something we do hope to implement in the future, we don't currently have any timescale for this - as our team are focusing on other features at this time. I have updated the relevant bug report with our dev team for you now. I hope this clears things up!

Thanks for your report @Beck! As Mike has mentioned, it's possible this dialog is opening on another monitor, or in an unexpected location. If you're unable to find this dialog, we can reset it's window location to return it to the centre of your main display. To do this, please navigate to the below location depending on your installation method, through Windows Run (Windows Key + R) : MSIX - %USERPROFILE%\.affinity\Photo\2.0\Settings\ EXE - %AppData%\Affinity\Photo\2.0\Settings Note you will need to change 'Photo' for 'Designer' or 'Publisher' in the above strings, depending on which Affinity app you're using Once opened this folder, please make sure that Affinity is closed, then delete the Window.xml file found in this location. Having deleted this file, relaunch the Affinity app and then open the Colour Chooser dialog once again. This should now hopefully open and show as expected for you. I hope this helps

In addition to the above, can you also please attach a copy of the .PSD files generated from Affinity Designer and Photo V2 so I can investigate this further? Many thanks in advance

Hi @DMK, Welcome to the Affinity Forums Unfortunately this camera model is not currently listed in our V2 RAW list, which you can find below - Support for these cameras is added through LibRAW, as v_kyr mentions above, and therefore we must wait for an update to LibRAW to include this camera, before we can add support in Affinity. Therefore we hope to include support as soon as possible for this camera, though we're unable to provide any estimated timeframe at this time, our apologies. I hope this clears things up!

Welcome to the Affinity Forums @Helga Kaufmann! I can see you have also posted this issue as a bug in the below thread - Please refrain from creating duplicate threads on the Forums, as this can increase our teams response time to your issue. I'd recommend replying in the above bug report thread, providing a screen recording / screenshots showing the issue you're reporting, so that Lee from our team can assist further. Many thanks in advance

Hi @CBNewham, Welcome to the Affinity Forums Thanks for your report & screen recording provided! I can confirm that although this issue does not trigger each time, I am able to repeatedly reproduce this issue here. From my testing, it appears this issue will only occur when using the Flood Select Tool with the Tolerance slider still 'open' on screen. For example, if you select the tool and expand the Tolerance slider, changing the tolerance, then select the small arrow to hide the slider before using the tool on the canvas, this 0% Tolerance issue doesn't seem to occur. If you leave the Tolerance Slider visible when using the tool on the image, this can occasionally cause the Tolerance to jump to 0% and the UI does not correctly update until switching active documents. I'll be logging this with our development team as a bug now. I hope this helps!

A previous response from myself can be found on page 2 of this thread - This is still logged as an improvement request with our developers, as it is not technically a bug with Affinity Photo. I'll be sure to 'bump' this again for you now.

Welcome to the Affinity Forums @Freddie Poser Thanks for providing a copy of your file once the object has been converted to curves - with the above document I'm able to replicate this issue. Interestingly, it appears very similar to a report we've had recently: As shown in the above thread, the users curve object was not exporting/printing until the Node Handle had been moved for the Curve, or the object had been Flip Transformed. I'm seeing the same behaviour in your file, therefore in order to resolve this I'd recommend simply moving the Node Handle for the end node of the object slightly, and it should then export - 2023-10-20 17-39-42.mp4 In the meantime I will be updating the development log I submitted against the above thread to include your file, as this should help our developers identify the cause of this and stop it from happening in the future. I hope this helps

Thanks for your post @Digit89 As Walt has mentioned above, trials for the Affinity V2 apps on iPad are handled by the iPad App Store directly - however if you wish to trial the Universal License on Desktop at the same time, you can do so by using the below link: https://store.serif.com/get/universal-licence-2/trial/ Using a trial will not change your eligibility status for the V1 > V2 Upgrade Offer, therefore anytime during or after these trials, you can simply proceed with the upgrade through the Affinity Store, to purchase the full Universal License. I hope this clears things up!

Unfortunately I can't comment on the icon as I'm not personally certain how these are obtained and displayed by the app for each object currently, though I can verify the layer name (which is user definable) is a completely separate layer property, which has been present in the Affinity apps pre-version 2 - unlike the layer 'tags' - and therefore is completely independent. I can only provide the information I am given from our team internally, and based on the info I can publicly share, I understand that the cause of this issue is currently due to how artboards are handled within Affinity - as a sudo Rectangle object, therefore I don't believe this to simply be a change of text string within the Affinity codebase to resolve the tooltip issue, and that is what I wanted to clarify here. I don't disagree that the label should be correct and show 'Artboard' for these objects, so rest assured I have updated the development log regarding this issue for you once again.

Hi @tallonius, Thanks for your report! I can confirm this is known issue with Adjustment dialogs when using 'Floating' document tabs, whereby the Adjustment controls are drawn behind the 'floating' canvas window. Please navigate to Window > Arrange > Dock All, which will stop the canvases from 'Floating' over the UI and display the adjustment dialogs as expected. I hope this helps

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.

Hi @cjmcqueen, Thanks for your report & I'm sorry to see you're having trouble! I've tried replicating this behaviour with your file and it appears to function as expected for me - both the embedded document and 'parent' document view (where the file is placed) continue to display the text in the file after using the Release command. The 'Release' command simply moves all of the objects outside of the 'Layer Container' in the file, though it's possible during this action the layer order may be changing in your file, causing the Rounded Rectangles to be drawn above the text layers. Therefore can you please try the following for me and let me know if this resolves the issue? Try manually releasing the layers. After using File > Place to introduce the SVG file, double click the document to edit in a new window. Select all layers within the Layer Container, then click and drag these in the Layers Studio to be outside of the container. This will perform the same action of 'Release', but manually - 2023-10-20 13-47-21.mp4 Try changing the layer order, after using Release. After using File > Place to introduce the SVG file, double click the document to edit in a new window. Select all layers within the Layer Container, then use Release. (note in my recording the issue does not occur at this point). Select the Rounded rectangles where the text is missing in your file and select Move to Back, then check the 'parent' document to see if this text is now visible - 2023-10-20 13-49-49.mp4 Please do let me know how you get on here

Hi @khalifah iskandar, Sorry to hear you're having trouble! Can you please navigate to Edit > Settings > Performance and provide a screenshot of your settings here for me? Many thanks in advance

Hi @JWall, Welcome to the Affinity Forums & I'm sorry to hear you're having trouble launching the Affinity apps! I'd like to request a few files for our team to investigate this issue and provide a resolution. The below paths provided assume you are using Affinity Photo, but can be changed for 'Designer' or 'Publisher' as required. Can you please: Open Windows Run (Windows Key + R) then paste the following string, depending on your installation method, and press OK: MSIX - %userprofile%\.affinity\Photo\2.0 EXE - %appdata%\Affinity\Photo\2.0\ In the window that opens, please select log.txt, then attach a copy off this to your reply here. Secondly, please open Windows Run and paste the following string, depending on your installation method, and press OK: MSIX - %userprofile%\.affinity\Photo\2.0\CrashReports\reports EXE - %appdata%\Affinity\Photo\2.0\CrashReports\reports In the folder that opens, please select the 3 most recent .dmp files (if any are available) and attach these to your reply. Finally, I'd like to request a copy of your event viewer log, to generate this please do the following. 1. Open Windows Run and type the following - eventvwr 2. In the window that opens, select the Windows Logs drop-down list on the left and then Applications 3. With the Applications logs selected, navigate to the right side of the window and select Save All Events As... and save them as .evtx (the default option). 4. Attach this saved file to your reply here. Can you also please confirm that none of the following apps are installed on your PC? Your reply should hopefully include the log.txt, the 3 most recent .DMP crash reports, and the .evtx event viewer log. Many thanks in advance

Hi Fränz, Many thanks for the update here and I'm glad to hear you've found a temporary workaround! I've updated our development log with this information, as this is the first report I've seen where enabling this option within Windows has resolved the crashing behaviour, so it's certainly interesting to hear. This may indicate an issue with the Affinity apps using multi-threading on your CPU - do you know what settings you have in your BIOS in regards to CPU threading? You may also wish to perform a 'Health Check' on your systems power supply, as this could potentially be indicative of a power draw issue

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

Thanks for letting us know, I can confirm I provided an update to this issue in the below post yesterday: I hope this clears things up.

No problem at all, I'm glad to hear you've seemingly resolved this issue! Inspecting the Layers structure in the latest file provided certainly appears to be designed in a more sensible way for SVG export. I have included some links below for the Affinity resources, including our 'Quick Start Guide', video tutorials and online helpfile: Quick Start Guides: Photo - https://affinity.serif.com/learn/photo/desktop/quickstart/ Designer - https://affinity.serif.com/learn/designer/desktop/quickstart/ Publisher - https://affinity.serif.com/learn/publisher/desktop/quickstart/ Tutorials: Photo - https://forum.affinity.serif.com/index.php?/topic/170269-official-affinity-photo-v2-tutorials/ Designer - https://forum.affinity.serif.com/index.php?/topic/170248-official-affinity-designer-v2-tutorials/ Publisher - https://forum.affinity.serif.com/index.php?/topic/170254-official-affinity-publisher-v2-tutorials/ Online helpfile: https://affinity.help/ I hope this helps

Hi @David Wilcock, As can be seen from the list of supported RAWs in V2, the Lumix S5ii is unfortunately not currently listed - Affinity Photo uses LibRAW for RAW support, meaning we must wait for this engine to add support for your camera, at which point it will be officially compatible with Affinity Photo. For this reason I'm unable to give any estimated timeframes as to when support may be added. I hope this clears things up!

Unfortunately this issue has not been directly addressed in v2.2.1 - however from the internal development log it appears as though our team are working to have this resolved in our upcoming beta version 2.3. Many thanks for your continued patience and understanding here

Hi @leonMo, Thanks for letting us know - I can confirm our team have found this issue has been caused by the macOS Sonoma update directly and we've informed Apple of the bug introduced. We're working to address this as soon as possible, thanks for your continued patience here

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.