NathanC

Welcome to the forums @foobstootsmittens, Sorry to hear that, If the app fails to create a new document/open any existing files, this is normally an indication of a GPU/Driver based issue on your device which is causing Affinity to crash when rendering. I've provided some potential solutions below to run through below in order: Disable Hardware Acceleration Within the apps under Edit > Preferences > Performance try disabling Hardware Acceleration (The last tickbox) and then close the interface and restart the app when prompted to and try again. Update your GPU Drivers Make sure that you have the latest available drivers installed for your GPU, I've linked the AMD driver search below. If possible, perform a clean installation of your drivers if given the option. https://www.amd.com/en/support Reset drivers via DDU If it still freezes/crashes, try doing a complete uninstall of your graphics card drivers using a dedicated tool for this purpose (Such as DDU linked below) and then restart and install your graphics card drivers (using the links above to search) to completely refresh them. https://www.guru3d.com/files-details/display-driver-uninstaller-download.html — If you’re still having trouble, could you send me a DXDIAG report? To do this, bring up run command (Win + R) and then type in the following: DXDIAG and then press enter. On the new window, press ‘Save all information’ and then save it to a text file on your device and send me a copy of the .txt file. Could you also send me a screenshot of your in app performance preferences? If there’s any recent crash reports for the app(s) available, could you also send me these? I’ve provided a link to an FAQ post below on finding crash reports. https://forum.affinity.serif.com/index.php?/topic/168448-where-do-i-find-crash-reports-for-affinity-v2-apps/#comment-963913 Many thanks

Hi @EaZy5D, This is because the 'Auto select' function is always enabled by default, as stated in the excerpt from the 'Selecting Objects' help guide below: https://affinity.help/designer2/English.lproj/pages/ObjectControl/select.html With it being a default setting in the app, it won't be remembered between app/document sessions, for example if you were to close and re-open the same document it won't remember the status of the setting, it will just default to checked as stated. This is the same as other contextual tool settings, if you have a separate document tab open and turned it off in that document, it will remember the tool state because that document session is still open, it just won't remember it if you close and re-open the document or start a new app session as per the above.

No worries, I've now moved it over to the V1 section 🙂 I'd suggest trying the below to factory reset the app by forcing it to re-create your local user settings (including the preferences) to default: Press Win + R to bring up 'Run' Enter in the following: %APPDATA%/Affinity and press Enter Rename the 'Photo' folder to 'Photo.old' Launch Affinity Photo Try changing any of your preferences (And disable Hardware acceleration) Restart the app when prompted and confirm if the changes have saved. If it still fails, see if you can manually modify the PerformancePreferences.xml file to disable Hardware acceleration by following the initial post's guidance in the FAQ below: If it still refusing to change, could you confirm if you have any antivirus software installed that could potentially be interfering with the app and preventing it from read/writing to your preference files?

Hi @PeterB., There was a bug prior to v2.1 where the resource manager would fail to update the Colour space after the profile of a linked resource was changed externally, the ICC profile would correctly update as expected but the Colour space would remain the same resulting in what's shown in your screenshot. This was fixed in v2.1 and I can't replicate this within the current v2.2.1 version as expected. Is this .afpub file possibly created in an earlier version of V2 or is it quite recent? If you were to file > place this same linked resource into a different document, or even delete it and place it back into the same doc, does it fix the UI issue or does it persist? While I understand you cannot share the doc publicly I would also be grateful if you could provide the .afpub doc along with the problem resource file so we can inspect it further, I've included a private upload link below. The doc will only be used for the purposes of testing this issue. https://www.dropbox.com/request/lJWVwW4f75SqEMWLnIc4 Many thanks

Hi @marciomendonsa, Please see the FAQ below for a full list of where the resource files/preference file locations (Including the MS Store). If you did originally purchase the apps from the MS store and you registered them against an Affinity ID, you can log in on the Affinity store and download the alternative versions (MSIX which is essentially the same as MS store, and the .EXE/MSI installer files similar to V1) so you're not just limited to downloading via the MS store.

We don't have one that is publicly available unfortunately.

Hey @PeterB., This is a known issue with pinned/inline objects from a master page currently logged with the developers, the initial application of the master page to a spread (e.g using 'default master' on a new document) will correctly show the pinned object on the page from the master, but any subsequent application of the master or clearing and then re-applying a master page will fail to apply add master page pinned object on that page/spread, which will likely explain why it's missing on a few random page ranges in your doc if they had a master re-applied. I've bumped the existing issue with your report.

Hi @Joalmama, After disabling Hardware Acceleration (OpenCL) under Preferences > Performance, are you closing the preferences dialog and saying 'Yes' to the restart prompt? If so, I would expect the settings to update when the app is next launched. The bug you've made reference to (white stripes/artefacts on export) is more prominent in V1 but you've posted in the V2 Bugs section of the forums, could you also confirm which specific app version you're using? There are multiple ways to disable Hardware Acceleration even outside of the app, in V2 one simple way to do this is following the below: Close all affinity apps Hold down CTRL and launch the Affinity V2 app while still holding CTRL A 'Clear user data' menu will appear with three boxes ticked, in addition tick 'disable hardware acceleration' Press 'Clear' and the app will now launch, check your performance prefs have been updated.

Hi @Linslusen, As Pšenda mentioned using the MSI (.EXE) version of the apps should sort both problems out, but before proceeding with the installation I would strongly recommend that you uninstall your existing .MSIX Affinity V2 apps first via Windows settings > Apps & Features as it's possible to have both versions installed on the same machine concurrently. The MSI V2 app installer will allow you to create a desktop shortcut during install, designate a custom installation folder allowing you to link 3rd party apps to launch the .EXE file directly and also will show an app icon thumbnail similar to V1 so long as the correct V2 app is assigned to open affinity files by default. How to download the MSI installer FAQ: Are you saying that the problem is that you get thumbnails for v1 but not for v2, or that you get thumbnails for v1 and v2 but they look the same so you can't tell which version the file was created in? It will likely be this little app icon that appears on .AF file thumbnails that they're referring to, I believe the MSIX version of the apps doesn't show this, which is logged with the devs.

Da das Problem monitorspezifisch ist, kann es ein Problem mit dem Standard-ICC-Profil sein, das mit dem Dell-Monitor geliefert wird und Farbkonvertierungsprobleme mit farbverwalteten Anwendungen wie Photo verursacht: 1. Drücken Sie die Windows-Taste + R, um den Befehl Ausführen aufzurufen 2. Geben Sie Folgendes ein: colorcpl und drücken Sie die Eingabetaste 3. Wählen Sie im Farbverwaltungsfenster Ihren zweiten Dell-Bildschirm aus dem Dropdown-Menü aus 4. Markieren Sie "Meine Einstellungen für dieses Gerät verwenden". 5. Drücken Sie auf "Hinzufügen" und scrollen Sie in der Liste nach unten, um "sRGB IEC61966-2.1" zu finden, und drücken Sie auf "OK". 6. Wählen Sie das Profil sRGB 2.1 und drücken Sie auf "Als Standardprofil festlegen". 7. Wählen Sie das Dell-Profil und drücken Sie auf "Entfernen". 8. Schließen Sie die Benutzeroberfläche und starten Sie neu. Versuchen Sie danach erneut, das Bild zwischen Windows Fotos und Affinity zu vergleichen.

Hi @JIGSr, Sorry I'm not sure what happened with my previous upload link as it appears to be invalid, I do think that the app is/was intermittent having issues verifying the location of the data source file when it is stored on your iCloud, so any action (either generating from it or removing it) is then causing the app to crash, I'd still suggest just keeping your .afpub and spreadsheet files local for now and then moving them to a synced iCloud location/folder after just to prevent this happening while working, but if you could upload the spreadsheet and .afpub document, along with a few recent crash reports i'll see if there's anything identifiable. Where to find crash reports: Upload link: https://www.dropbox.com/request/jcz9kaT7nG2uRwVmrvjA

Hi @JIGSr, Could this be another situation in which your template .afpub files and data merge source/spreadsheet are being actively stored on an external storage location (e.g cloud, network storage, USB) when you generate the data merge? Unfortunately I was not ever able to re-produce the crash with your prior documents on iCloud after some trial and error. I would just initially confirm that all the files you're working with are stored and being opened from a local location and then try generating the merge again. If the files are stored locally and you're still encountering the crash it could be a problem with the contents of the file, if you can provide the .afpub and data merge source for inspection along with a recent crash report that would be great, I've added an upload link below. https://www.dropbox.com/request/TaJ51mWsGCFQExo97LUA Where to find crash reports:

Welcome to the forums @jordaan, I've just installed the latest 2.1.0 update for Topaz Photo AI on a Windows 10 machine and confirmed both Photo V1.10.6 and V2.2.1 were both capable of launching the plugin and applying the settings back on the original image in Photo. With it being a problem with a 3rd party plugin crashing it can be quite difficult for us to advise on, but you could try uninstalling your existing version and then download your previous working version from their community forums to verify that it works after setting it up in AFPhoto again. I've found and linked their latest releases forum board below where you're able to download earlier versions. https://community.topazlabs.com/c/photo-ai/photo-ai-releases/85 Failing that, I would suggest also contacting topaz labs directly and if you haven't already raising this on their community forums.

Welcome to the forums @MikeGebert, It's unlikely that your app crash problem will be related to the light mode UI problem as that is specific to Sonoma so I wouldn't recommend following the FAQ guidance if you're running Catalina. If you to go the Applications folder in Finder your app version should be easily identifiable as the V2 apps by default will be listed with a '2' on the end, so 'Affinity Photo 2' or example, while the V1 apps will only be listed as 'Affinity Photo' with no version number after the app name. If you could initially provide us with some crash reports that would be great, the FAQs below detail how to find these. How to find V1 crash reports: How to find V2 crash reports: Many thanks

Hi @MikeV, Thanks for sending over the RAW files, since we're now on 2.2.1 I decided to check through a few of the .TIFF files you sent me originally, and after opening them in Photo 2 to my surprise the colour profile/cast issue was no longer present! Opening the .TIFF files in Photo 2 was no longer assigning them the sRGB 2.1 profile which was causing the blue cast problem in 2.2.0, and after placing them into a Publisher document it was correctly retaining the ProPhoto RGB profile. I've also just verified this on a separate Macbook pro, on 2.2.0 your images would fail to open with the ProPhoto RGB profile assigned to them, but following an update to 2.2.1 this was being correctly retained on import. Therefore if you havent already I'd suggest updating your Apps to 2.2.1 and then try opening one of the .TIFFs in Photo, if this correctly retains the ProPhoto RGB/16 profile try placing that same image into a new publisher document to confirm the colour issue is no longer visible.

Welcome to the forums @tamiam, Sorry to hear that. If you could upload the problem document (and any external linked resources used) to the private upload link provided below we can look into this further. https://www.dropbox.com/request/7wfLtkSXNovvIIPK6sJM Let me know when the file(s) have been uploaded as we are not automatically notified.

Hi @SrBrits, If you're on Mac you could try Unsyncing and then re-syncing the app to iCloud From System Settings > iCloud > iCloud Drive > Apps Syncing > Toggle the Affinity App off > Done > Go back in and Toggle the app back on > Done. Once you've done this if you open up the Affinity App and go to File > Save as, you should have the option in the Finder sidebar to save to the App's iCloud folder. There is a known issue currently logged with the developers with the iCloud app folders not becoming available on the iCloud web app so it's possible that the folder may not be available when viewed on the Web. Personally i'd suggest just creating a folder on your iCloud drive manually and saving your docs that, as this avoids potential issues, and i'm not aware of any major advantages to using the app generated iCloud folder.

Welcome to the forums @Dave Eagle, No news to share currently i'm afraid, this thread is tagged with the issue number so if there are any further updates in regards to the issue the Serif Info Bot will automatically reply to the thread.

Hey @Daniel Finch, I would suggest using the Flood Select/Magic wand tool set to 'Contiguous' and at a low tolerance value (~5%) for your initial selection, and then use the Selection brush tool after set to 'Subtract' mode to clear up the areas on the Santa Hat/Deer which were also selected before outputting to a mask, if any bits have been missed you can edit the mask using standard brush tool.

Wenn die Datei nur 6 MB groß ist, sollten Sie in der Lage sein, sie an eine Antwort im Forum anzuhängen. Wenn Sie jedoch Probleme haben, können Sie sie über den Dropbox-Link unten hochladen. https://www.dropbox.com/request/qpVONdRueAtNsLlmqI7q Heißt das, Sie fügen manuell eine Helligkeits-/Kontrastanpassung in Affinity Photo hinzu, um das Problem zu beheben?

Hi @gerley, I'm also seeing the same unresponsiveness when the Selection brush tool is immediately selected in your file but it is a file specific problem, the brush tool freezes when I delete all objects in your document on an empty canvas. I'm also on Windows so it doesn't have anything to do with your specific device. However, If I opt to select another selection tool (such as marquee or lasso) first and then draw out a selection area anywhere on the canvas and then switch over to the Selection brush tool this prevents the issue from occurring, so the app may have been having issues with a certain setting/value set on the tool but it's difficult to say for certain at this point. I'm then also free to deselect the area and switch to the tool without it freezing any further, I've saved a copy of your same file below where the app should no longer freeze when the tool is selected as I've already done this. We'll take a further look into your file and get it logged internally for investigation. Re-saved file again.afphoto

Welcome to the forums @TomLL, We don't have any news to share regarding .AI file export support currently. Feel free to voice your support on the existing feedback request thread linked below.

Hi @mr.jebs, I've replicated this shortcut issue and it's now been logged with the developers. As an alternative workaround, the 'Hide others' shortcut works from the Layers panel context menu (3 line burger menu).

Good spot, there's actually two separate issues logged internally per OS which are linked/related which I hadn't noticed earlier. On MacOS you get the incorrect 'Select an RGB Pixel Layer' message, but there is also a separate issue logged for Windows where it does allow you to enter the persona while recording but after you press 'Apply' it will prompt the 'Cannot record Tone map' toast and anything you did in the persona is not recorded. Windows definitely has it worse of the two, as it allows you to enter the persona only to tell you you've wasted your time after applying, I'll bump this issue.

Danke für die Klarstellung und die Bereitstellung der Screenshots. Ich würde meine Kommentare zu HDR vorerst ignorieren, da Ihr Bild eine sRGB/8- 2.1 JPEG-Datei zu sein scheint und Ihre Windows-Anzeigeeinstellungen darauf hinweisen, dass HDR auf dem Monitor nicht unterstützt wird. Könnten Sie mir zum Vergleich eine Kopie der JPG-Datei von Ihrem ersten Screenshot schicken? Vielen Dank!