NathanC

Hi @Halex, This is a problem I have been able to re-produce on a Wacom BT S and the app in low precision mode, double taps do appear to trigger a full pressure stroke. I've logged this with the developers for further review and investigation. As you've identified using either High Precision or Windows ink avoids the double tap pressure issue, though I did not experience either of these even on a lower end GPU. Perhaps try setting the Retina Rendering setting to 'Automatic' instead of 'High Quality' in the app Settings > Performance.

It's good to hear that it works with OpenGL rendering without requiring a force redraw after every brush stroke. I'll raise your issue internally with regards to the Metal renderer to see if there's any potential factors causing this. However, we're more limited on Mac since the issue is evidently caused by Metal specific to your local environment, and performing basic steps such as a GPU driver re-install isn't really an option on Mac since this is handled via system updates unlike Windows. Since you mentioned that this only happened recently after an app update, I would be interested to hear if you roll back to your previous app version and then enable metal if it then works. This will help confirm if it is something external to the apps that has caused this. https://store.serif.com/en-gb/update/macos/photo/2/

Hi @Dave42, As well as the DMP file if you could send us a copy of your document we can confirm if the freeze can be replicated as well as any potential causes. I've provided a private upload link below. https://www.dropbox.com/request/cgZqysHPqDP4lqJjg6ib Thanks

Welcome to the forums @Michael Blechinger, I've just re-updated my Mac apps to 2.4.2 to check this and the context toolbar visibility state wasn't changed following the update, the only instance where it was missing was because I toggled it's visibility off before updating my app version so it's possible that this was the case, or there was a local issue with your app preferences file during the update but I can't replicate this.

Hi @Hangman, I've now logged these discrepancies with the developers. 👍

Hi @jweitzel, Thanks for the recording. If you first untick the 'Hardware Acceleration' option at the bottom this should unlock the 'Display' dropdown which you can then change from 'Metal' to 'OpenGL'. Once this has been done, close the interface and restart the app and then try again.

Hi @mannyarts, This does certainly appear to be unexpected behaviour when converting the mesh warp to curves, particularly as it occurs with the Mesh reset so no warping is applied. I've logged your file with the developers for further investigation.

Thanks for the update @jweitzel, As well as disabling Metal Compute in the app Settings -> Performance try setting the 'Display' setting to 'OpenGL' and then close the interface and restart for the change to take effect. Zooming in and out forces a redraw of the canvas area, this force redraw can also be triggered by holding and scrolling in and out of the canvas with the mouse wheel, but this should be happening automatically. Your setup sounds fairly standard to me, are you using a drawing tablet or any other notable peripherals? If it still doesn't work with OpenGL enabled, ideally we'll need a screen recording which shows the issue, if you don't wish to share it publicly I have added a private upload link below. Also, try having the Navigator panel open to see if your brush strokes appear in the navigator canvas preview. https://www.dropbox.com/request/4qvWoIJGCwndRcXKmKZU You could also try rolling back your app version if you found that this only started happening as of the last update, you can download the earlier versions from the link below. https://store.serif.com/en-gb/update/macos/photo/2/

Hi @nwhit, I've replicated and logged this with the developers, thanks for your report.

Willkommen in den Foren @MelaNico Wie wir sehen, haben Sie uns auch eine E-Mail bezüglich Ihres Druckproblems geschickt, worauf ein anderes Mitglied des Teams inzwischen geantwortet hat und die entsprechende Schriftartendatei und das entsprechende Dokument angefordert hat. Daher werden wir Sie weiterhin per E-Mail unterstützen.

Not that i'm aware of unfortunately, but it would certainly be helpful in situations like this. If you rename the file externally, for example in the Files app and change the extension from .cube to .cub it should still be detected as a valid LUT format, and then try importing it into the app again. If this works, you could also try exporting from Photo 2 to other LUT formats, such as .CSP or .3DL and then see if they import/load successfully going forward.

Hi @NotMyFault, I've replicated and logged this with the developers, many thanks. 👍

Welcome to the forums @Christian L., Do you have any other apps on your iPad that are capable of importing or opening .Cube files that you've used before? In previous instances we've seen this for other specific file types that are normally importable are showing as 'greyed out' in the apps, and this is caused by file association permissions on iOS. The first app that is installed is then associated with that file type, and other iPad apps are locked out of selecting this file type. I've similarly seen this with DXF/DWG when CAD apps are installed as an example. From our understanding the only way to resolve this is to temporarily uninstall any app(s) that are holding that file association, and you should then find that they're accessible in Affinity, but also bear in mind that there is a bug in the LUT adjustments panel where they will fail to show up after importing them as Walt mentioned.

Hi @jweitzel, If the edits are visible in the layer thumbnail or navigator panel but not the canvas this does sound like a rendering/draw issue. I'd initially recommend disabling Metal Compute in the App Settings -> Performance (last checkbox) and then restart then app when prompted. Once this has been done, see how it goes moving forward. If the issue persists, when this next happens it would be helpful if you could provide a screen recording which demonstrates it happening. Thanks

Witamy na forum @M4_d_83 Jeśli nadal masz trudności po wykonaniu samouczków dotyczących maskowania, pomocne byłoby dostarczenie zrzutów ekranu, nagrania ekranu lub przykładowego pliku, w którym występują problemy z maskowaniem, abyśmy mogli dalej pomóc. 🙂 --- If you're still struggling after following the masking tutorials, it would help if you could provide screenshots, a screen recording or a sample file where you're running into masking issues so we can assist further.

Hi @dantaylr, I've logged your file with the developers for further investigation. 👍

Hi @Hangman, Good spot, I've logged this with the developers for correction. I think 'Spread Properties' is it's own separate dialog and should remain as such when accessed from the pages panel. It gives specific config settings for amending the properties of the spread, whereas Document setup contains tabs relevant to the entire document scope such as colour space, model etc. that are not necessarily relevant to the selected spread(s) I've chosen to amend.

Hi @NotMyFault, I've replicated and logged this with the devs, thanks for your report.

Hi @Tom Zimberoff, As NMF has mentioned we'll really need to see a screen recording and a file with the history saved when this next occurs to allow us to look into it further, as this isn't something I've seen reported before nor have I observed this behaviour when using the tool. If you would like a private upload link let us know. 👍

Welcome to the forums @Onett_AC, Double clicking to select a page will automatically move the view to the selected page and fit the full page on your app window size on screen. As far as I'm aware there isn't a way to change it to retain your current zoom level or a pre-defined value when double clicking a page, you'd need to set this manually, for example using the CTRL + 1 shortcut to set the zoom level to 100% after selecting the page.

Hi @pioneer, The setting essentially offloads certain tasks from the CPU onto the GPU, which normally results in a performance boost. It's primarily beneficial in raster based tasks and workflows, and I normally see the benefit when using Live filters. The help guide below gives a good general overview. https://affinity.help/photo2/English.lproj/pages/Extras/hardwareAcceleration.html As far as I'm aware there isn't a need to make a specific program profile in the Nvidia 3D settings panel for the apps, let it just use the Global settings.

Hi @MikeTO, Thanks for your report, I've now replicated and logged this with the developers.

Hi @MikeTO, Thanks for your report, I've replicated and logged this with the devs.

You'll probably need to convert the file's to a compatible RAW format, such as using Adobe's DNG converter tool. https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html#:~:text=download the dng converter RAW support relies on the LibRAW decoder supporting the format first, it's possible that support will be extended to the High Efficiency format. If support is added it will be reflected on the official supported formats thread linked below.

Welcome to the forums @IvashistaI, Support for the Z8 RAW format in Photo covers standard compression formats only. If your Images were shot with the RAW recording set to 'High Efficiency' this will be the reason the file fails to open as this isn't supported. I've linked the manual below which details how to change this setting on your Camera. https://onlinemanual.nikonimglib.com/z8/en/psm_raw_recording_123.html