NathanC

Hi @joe_l, Can confirm I've replicated this issue, as well as the subsequent crash when attempting to change the view, this has now been logged.

Welcome to the forums @Rina Leto, This has now been replicated and logged internally with the developers.

Hi @ianrb, It's likely that you're running into a known bug currently logged with the developers. Clicking anywhere within the empty space in layers panel while actively recording a macro will trigger an immediate app crash, this will hopefully be fixed soon. Interacting with Layers within the panel (such as renaming) shouldn't cause the crash, but I understand it's fairly easy to unintentionally click in the empty area in the panel.

Welcome to the forums @eric4972, If the .TIF file exceeds 4GB, it will be saved out of the original software as a 64-bit BigTIFF file which doesn't have a unique extension. Photo 2 doesn't currently support BigTIFF files and will prompt the observed error.

Hi @Madeleine S, Looks like a possible bug/unexpected behaviour, so I've moved this thread and logged this with the developers for further review, thanks for providing a detailed report.

Hi @bbrother, I'm also observing it intermittently fail to update in the pages panel, I'll get this logged with the developers.

Hi @acacija Unfortunately, the file is not recoverable by any standard methods available to us, so it will be logged with the developers for further investigation. It's possible that the team may be able to recover your file, but this isn't guaranteed or something we're able to provide a timeframe for, as files are logged primarily for the purpose of improving the app's file handling. If possible, we recommend reverting to a backup, or if one is unavailable you may need to consider re-creating the file. If you could answer the questions outlined in the FAQ below to the best of your knowledge we can get this logged: Thanks

Hi @acacija, Looks like the document has unfortunately corrupted. If you don't wish to share the file publicly feel free to use the private upload link below and we'll see if it can be recovered. https://www.dropbox.com/request/7jk5iiViGlwXU4Tp9Jn4 If you could also answer the questions in the FAQ below to the best of your knowledge, this will assist the development team in case it needs logging:

Hi @EvaWebdev, This is a result of the paint brush tool using the black colour spot/well by default, and can be observed immediately after creating a new document and cycling between the tools without any other steps required, the paint brush tool automatically switches over to black. At this time, it's not possible to set it to the opposite colour spot (white) by default, but after switching to the paint brush tool if you use the 'X' shortcut to switch the Foreground and Background colour, this should be retained while working on that document moving forward.

Looks like the function will still show the bounds of the original base box, I don't think this view can be turned off unfortunately.

Hi @MmmMaarten, With the group layer selected, if you use the Select -> Cycle Selection Box command to switch to the regular bounds, you should then be able to set it permanently for the group layer via Select -> Set Selection Box.

Thanks, to rule out the possibility of a local app data issue, I'd recommend a full factory reset of the app via the Finder directories. These locations can be accessed via Spotlight Search (CMD + SPACE), ensure all affinity apps are closed before checking this: ~/Library/Group Containers/ Delete or rename the ‘6LVTQB9699.com.seriflabs’ folder ~/Library/Application Support/ Delete or rename the ‘Affinity Photo 2’ folder ~/Library/Preferences/ Delete or rename the ‘com.seriflabs.affinityphoto2.plist’ file Once removed, reboot your Mac and start Photo 2 to confirm if the Develop persona launches.

Many thanks, I've spotted two issues: - On Pages 2, 3 the image layer with FX applied appears to be causing all content below it to become flattened, this appears to be unexpected behaviour. To prevent this, I've rasterised the pixel layer (With preserve FX disabled). This is destructive, but does ensure that the layers below are not unexpectedly flattened to pixels while preserving the appearance. I'm in the process of reviewing this and seeing if it can be replicated on a new document. - On Pages 12, 13 the Pixel mask is clipped to the master layer, which will flatten the entire master layer's content on PDF export. To prevent this, I've selected the Master on Page 12/13 -> Edit Detached -> Clipped the mask layer onto the Ellipse object located at the top right hand corner. This will preserve the visual content on export without flattening to pixels. I'll PM you a copy of the updated document shortly so you can see the changes and re-export to PDF again.

Hi @Iztok, I can't see any issue with your attached sample file, but I'd suggest selecting the object and checking the Fill Opacity slider is set to 100% in the Colour panel.

Hi @Joe Gavilan, Feel free to upload to the private upload link below if you don't wish to share the file publicly and we're happy to review this. https://www.dropbox.com/request/XeaEIOFVjzTtdZdf7ppJ

Welcome to the forums @Linktros, This is a known issue specific to RTX 50xx series cards currenty logged with the developers, the issue has been bumped internally with your report.

Hi @Maxdanger, Could you upload the TIFF/ARW files to the private upload link below? We can then confirm if the issue can be reproduced internally. https://www.dropbox.com/request/7BwywwaA3Nf3YrOvR2J9 Please let me know when the files have finished uploading, thanks!

Welcome to the forums @Nalla, Affinity Photo uses the Lensfun database to source lens corrections, it is possible to manually update Photos lens profiles folder prior to ensure you have the most up to date corrections, even before the apps are officially updated. However, it doesn't appear that Lensfun have added support for your camera's profile yet, I'd recommend reviewing this on Lensfun's website linked below, as it's possible that support for the profile will be added in the future. https://lensfun.github.io/lenslist/ Once supported has been added, you can follow the video tutorial below to manually update your profiles. https://www.youtube.com/watch?v=ahBF2_On_rA&list=PLjZ7Y0kROWitoJtnw0pdvjPmS8mYGvrBR&index= Unfortunately I don't have an another source I can provide for that particular profile.

Hi @Art51, I can confirm I've replicated this issue using a tablet and logged this with the developers.

Regardless of the age of the application or your device, it's important to follow the steps provided so we can rule out local affinity app data as a potential factor, particularly if the app was functional on your device at an earlier date. Please let me know the results once this has been reset. Additionally, if the issue persists please send a copy of the Log.txt file, which can be found in the following directory: %USERPROFILE%/.affinity/photo/2.0

Hi @Didier04, This issue is currently logged internally with the developers. This thread is tagged with the bug ref, so If there are any further updates on the issue, the Affinity Info bot will automatically reply.

Hi @Geoff Readman, I'd recommend following the guidance in the FAQ below to update your Graphics card drivers and disable Hardware Acceleration. If the issue persists, please provide the following: Screenshot of Edit -> Settings -> Performance in the app Recent crash reports (FAQ below) Many thanks!

Hi @John appleseed, Circling back to the original problem, constraints groups cropping strokes that exceed the bounding box is currently logged internally with the developers, I've bumped the issue with your report.

Many thanks, Could you run through the steps below to perform a basic app reset: Close all affinity apps Hold down CTRL and launch Photo 2 while continuing to hold CTRL A 'Clear user data' menu will prompt with three boxes ticked, additionally check 'Disable Hardware Acceleration' Press 'Clear' and the app should hopefully start If the issue persists, please follow the below to perform a full reset of the app's local data: Press WIN + R to open 'Run' command Enter the following: %USERPROFILE% In this directory, right click the '.affinity' folder and rename it to '.affinityold' Launch Photo 2 If the issue persists, could you confirm exactly what stage the app gets to before crashing, for example does the app splash/start screen show or does the main app User Interface launch prior to the crash? A screen recording would be very helpful here. Additionally, please send a copy of the Log.txt file, which can be found in the following directory: %USERPROFILE%/.affinity/photo/2.0

Hi @resunoiz, If you're experiencing the app crash on document creation or when opening an existing file, please follow the instructions on the FAQ below to update your Graphics card drivers and disable Hardware Acceleration. If the issue persists, please provide the following: Screenshot of Edit -> Settings -> Performance (if you're able to get into the application) Recent crash reports (FAQ below) Many thanks!