Dan C

I'm certainly sorry to hear this - as we aren't receiving reports from other users regarding this since releasing V1.10.6 so it may be machine specific. Are you able to attach a copy of a file that crashes on load, and a copy of a crash report (if one is generated) when the app crashes? Have you recently updated your GPU drivers? If not, I'd recommend ensuring you have the latest version, directly from the manufacturers website. Many thanks in advance

Unfortunately this issue remains open currently in both V1 & v2 - a fix was implemented for V2 according to our developers, however this was failed by our QA and returned to the devs. I will 'bump' the issue for you now, though our plans for V1 remain as follows; Therefore I'd be unable to guarantee that this will be resolved in V1, my sincerest apologies.

Welcome to the Affinity Forums roxana I have replied to your post regarding this below - I hope this helps.

Hi @roxana, Welcome to the Affinity Forums & sorry to hear you're having trouble with this file! I have attempted to repair the document, however I have been unfortunately unable to - as there is a large 'chunk' of the file which is missing, shown in the HEX data from the file below - Unfortunately with this much data missing from the file, our dev team would also be unable to recover the document, my sincerest apologies. May I ask, why are you using V1.9.2 over V1.10.6 (the latest V1 update)? As we only officially recommend running the latest updates for either V1 or V2, to ensure you have the latest stability updates and bug fixes to avoid such issues. As you've also mentioned, unfortunately our team don't recommend saving/loading directly to an external USB drive, due to the way Affinity loads documents and handles memory, if an external device is disconnected for even a moment whilst the file is loaded, it can cause issues with a document saved directly to it. I will be sure to log this file with our developers as we keep a track of any corruptions for statistics and monitoring purposes, but I would not expect the file to be reparable due to the missing data mentioned above. Please accept our sincerest apologies for any inconveniences caused due to this. If you have any backups of this file, I would recommend restoring this to continue your work, where possible.

No problem, many thanks for the further information provided - I'll be sure to pass this through to our team with the bug report now. I'd like to also try one more step on your machine to see if this alleviates the issue, under Preferences > Performance can you please change the Display option to Software, then restart the app and follow your steps in your file once again. The app may be slower to respond, but I am hoping the rendering issue will not appear. Does the same issue still occur please? This should help indicate to our team on a base level, if the issue is between Affinity and your GPU or Affinity and your RAM

No problem at all, I'm very glad to hear this and we sincerely appreciate your kind feedback. We always love hearing our users are enjoying using the apps as much as we enjoy making them Should you have any further questions, please don't hesitate to start a new thread!

I've been informed that converting/assigning the document to the CMYK profile within the app (before printing) and then in the Print dialog selecting Colour Handling - Performed by device/printer should provide the same results as V1 with the app performing colour handling, though I'm not currently able to directly confirm this internally - so please do let me know if this helps. Thanks @thomaso, I can confirm that 'AFB-7034' is the same issue as I logged here for RGB profiles not appearing in this list and was closed as a duplicate - if you are unexpectedly seeing RGB profiles in this list then I'd recommend reporting it in a new thread, so it's not missed by our team and can be investigated separately

My sincerest apologies for the delayed response here once again and many thanks for providing your file! I have tested this on the following setups: iMac 2019, 6 core i-5, 16GB RAM & Radeon Pro 580X 8GB Mac Mini, 8 core M1, 8GB RAM Windows 10, 4 core Xeon W3520, 16GB RAM & GTX 1050 Unfortunately on none of these devices have I been able to directly replicate the Merge Visible issue, however I can clearly see the issue in the layer you generated in the file provided, and interestingly when zooming in/out on Windows repeatedly, I was able to see the mipmap issue rendered on the canvas, before performing the 'Merge Visible' step. Therefore I'm getting this logged with our developers now, as it may require the same (or more similar) GPU as you have in your setup to replicate - though as I've been able to recreate the same preview when zooming, it certainly indicates an issue with how the app is processing your layers. I will be sure to update you here with any further information from our developers and we hope to have this resolved in a future update

Hi @Nicolas.yax & @super_average_gunpla, Sorry to hear you're both having trouble here - I've tested this using my GTX 1050 with both 516.94 & 527.56 using JPEG & TIFF files, in both 8/bit & 16/bit - unfortunately in none of my tests have I been able to replicate this issue, my apologies. Firstly, I'd recommend reinstalling the latest Nvidia drivers, using the 'Clean Installation' option, as outlined here - https://help.bethesda.net/#en/answer/57037 Secondly, can you please attach a source file that shows this issue, such that I can test with your files directly? Thirdly, can you please confirm for me, do you have a custom screen ICC profile applied to your monitor, through the OS settings? This would certainly indicate that it's an issue caused by Nvidia, rather than Affinity directly - however I will also be sure to test this at home where I have access to a 3080tito ensure this is not an issue specific to 3000 series cards, for example. Many thanks in advance

Many thanks for letting me know Alex, I'm certainly glad to hear this

Of course, please upload the file to the below link for me, then reply here with a list of steps taken once uploaded: https://www.dropbox.com/request/TH4cVjlg2oqzzBCL4MGc Many thanks

Thanks for updating us here @TonyO & my apologies for the delayed response. I can confirm this is still logged with our developers as a bug, and I'll be sure to 'bump' this for you now - our apologies for any inconveniences caused here due to this. I will be sure to log this separately as an improvement request with our devs for you also

Apologies for the delay here - many thanks for your continued patience! I have spoken with our development team, who have confirmed the following: However, I do appreciate that when previously selecting these profiles, you were able to print to the 'correct' colours, which you can no longer replicate with an RGB profile - therefore I have requested further information from our team as to the suggested workaround following this change - and I'll be sure to update you here with any information I'm provided

Welcome to the forums @Collizma & our apologies for the delayed response here, Sorry to hear you're having trouble! I have tried replicating this issue and thus far have been unable - are you able to provide a screen recording showing this occurring for me? If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks in advance

Hi @Wizaerd, Thanks for your further report and I'm sorry to hear you're experiencing this issue also - as confirmed above this is a known bug which is logged with our development team. I will be sure to 'bump' this issue for you now, and we hope to have this resolved ASAP. I hope this helps

Hi @finevine, Our sincerest apologies for the delayed response here - can you please provide a copy of an .afpub file where this issue occurs, and the exact steps you are taking that crashes the app? Many thanks in advance!

Hi @CB1978, My sincerest apologies for the delayed response here! I can confirm that unfortunately Affinity Designer V2 doesn't yet support plugins, though this is something our developers are still looking into and hoping to support in the future. I hope this clears things up

Thanks for letting me know @DerekC and apologies for the delays once again - I've tested this here in both V1 (1.10.6) & V2 (2.0.3) and I'm seeing the same behaviour in both apps, the below recording is from V2 - 2023-01-03 13-11-23.mp4 As can be seen, CTRL + Page Up/Page Down is moving to/from the next/previous pages at different zoom levels, as expected. Is this the same behaviour you are seeing please? If not, are you able to provide a screen recording of the different behaviour?

If you're referring to the Resource Manager, this is now found under the Window menu in V2 - which is expected behaviour. If I've misunderstood this, please don't hesitate to let me know

@Willy Pimentel, I'm certainly sorry to hear you feel this way - I can confirm that this issue is still logged with our developers, however I am in the process of once again bringing this to their attention to request an immediate fix, as I absolutely appreciate how critical this issue can be. Should our team require any further information, we'll be sure to respond to you here and we appreciate your continued patience and understanding in the meantime.

I have checked with our team and they have confirmed they're seeing the same (correct) behaviour that I'm seeing here - and are also unsure of any reason this would be different on your devices. Are you able to provide a screen recording of the full workflow you're taking, when this text style is not created please? If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks

Although I'm glad to hear this resolves the issue for you, it shouldn't be required and still doesn't align with the behaviour I am seeing here with the option disabled (ie the new Text Style is listed as expected). This option provides the following functionality: With this option disabled, any Paragraph or Character Styles should show in the Text Styles list, shown in your screenshot. With this option enabled, you can select the created style from either the Character or Paragraph context toolbar options available when you have a text frame selected, allowing you to selectively apply a Paragraph Style as a Character Style, and vice-versa (and this is working correctly for me here). The following recording shows me creating a Style based on a previous Paragraph style and changing the font size. This then appears in the Text Styles list. I then created a text frame, and on the Context Toolbar checked both the Character and Paragraph Styles options. The Style only appears in the Paragraph list. After editing the newly created Style and enabling 'Show in both lists', this style can now also be selected in the Character Styles dropdown from the Context Menu. RPReplay_Final1672750133.MP4 However, I appreciate this does not provide a reason that the same workflow is not working for you - and I'm unsure of the exact cause of this currently. I will speak with our QA team to request to investigate this further and I will be sure to update you here ASAP!

Unfortunately this issue is still logged with our developers and I will be sure to raise this with them once again for you now as I appreciate how critical this can be. Our sincerest apologies for the continued inconveniences caused here.

Unfortunately Designer (Desktop) simply doesn't support the Merge Layers operations, my apologies.

Hi @Sabz, Apologies for the delay here! You can upload your file to the following link for me - https://www.dropbox.com/request/Lw8Bf9ptXWy5TfalALLM Once uploaded, please reply here to let me know. Please also note the following from Garry, as this is the usual cause for TOCs updating unexpectedly