ceg

It's an annoying change, but I got it (somewhat) to work for a different software. I use PhotoMechanic and use (or maybe used) Affinity Photo as my default photo editor. I pointed PhotoMechanic to: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPhoto2_2.0.0.1640_x64__3cqzy0nppv2rt\App\Photo.exe but I had to initially run PhotoMechanic as an administrator to have access to the file. Now, unfortunately, Affinity wants to reset itself to its default settings when I call it from PhotoMechanic. There are two work-arounds: a) you can cancel out of the dialog box or b) start Affinity Photo before you start PhotoMechanic. It's a poor solution to something that worked perfectly fine before. :(

I have the latest version / build, and the problem persists in 1.10.04 1198. It crashes so frequently that it is almost impossible to create an index. Rather frustrating.

I reported the histogram bug in the curves dialog years ago. The bug has been ignored through several updates. 😞

It's sad to see that there has been one official response to this post since it was originally posted on February 24th. The astrophotography stack was advertised as a big thing. Now nobody seems to care that it doesn't seem to work as advertised for some folks. Correction - doesn't work at all for some folks. I have no way of telling how big of a problem it is, but the lack of a response is disheartening. I am so looking forward to all the features that won't work in the next version of Affinity Photo.

Sadly it still crashes in 1.9.2 😞 - I had high hopes. Hopefully the feature will work in the next update.

I haven't been able to use the stacking feature either. My progress bar doesn't even get as far as the one shown in the image. 😞 I hit "stack", the progress bar appears, and a fraction of a second later AP crashes.

This "improvement" is an annoying step backwards. Double-clicking is always faster than clicking on two different places on the screen, so please revert to previous method.

I've never had much confidence in AP's histogram, but had hoped it would get some improvements in AP 1.9. No such luck. 1. The histogram in the curves adjustment tool is absolutely useless. It only shows where all three channels overlap. It's been a bug for years, but yet ... it's still there. 2. The regular histogram during Raw development is questionable. Attached are histograms for an image that was composed in camera to have a well-centered histogram. Photo Mechanic creates a histogram from the jpeg, which looks about like the in-camera histogram DxO Photo lab (no corrections applied) shows a very similar histogram for he RAW file. Only Affinity is special. 😞 The image also shows screenshots of the image preview for all three versions. I am using AP on a windows desktop. Christoph

Glad you two agree. 🙂 I had copied it to the desktop with a note to delete it in a month. I noticed that the old folder was almost half a gig in size: it dragged some "autosave" files around forever. Are these necessary (I guess not), and is there a way to delete them in a more elegant way than manually going into the folder?

Thanks Chris B - that did the trick.

When rotating an image in the develop persona for the first time the color changes. Developing the image returns it to normal. When returning to the Develop persona the rotation works fine. I am using AP 1.8.4 under Windows 10, latest build. display_issue_when_rotating_an_image.mp4

Problem still persists with latest build (1.8.4). Pointer disappeared after processing 2-3 images. 😞

Uwe, Mark, I followed the recommendations of the link, and they are utterly ineffective. 😞 Function keys (all of them) do nothing, drivers are up to date. Some elaborate wireless keyboard and mouse software (to enhance functionality) didn't do anything beyond what already had. It took a few images (to process) until the pointer disappeared again, but disappear it did. It works fine in every other application (including AP 1.8.3.641), but does not work in the beta version (691 and previous one). As far as I can tell, the failure is rather unpredictable. The problem persists with the mouse and the trackpad. I know, Mark, that's not what you like to hear, but that's where I am right now. Christoph

Thank you both. Uwe, I will check out the link. I wouldn't put it past MS to mess it up, though it would be odd that only one beta application is affected. Mark, I do not use a pen on this computer, though the screen is a touch screen. The problems occurs frequently, but seemingly randomly. For a while I thought that closing dialog boxes with the mouse would prevent the problem, but ow I am not so sure any longer.

I am using build 693 under Win 10 (latest version 2004). My mouse pointer disappears on a regular basis. On a fresh start everything works normal for the first image. Once the first image is closed the mouse pointer disappears. The screen shot image does not show the pointer in the correct place. In video 1, I almost never see the pointer. The software responds to where the pointer "should" be, but I see nothing, and the screen shot image places it in a completely different location. Video 2 shows what happens with an open image. What I see is not what is captured on the screen in the video. I see a pointer on the main canvas, on the (empty) menu bar and when I hover over the AP icon in the upper left corner. Unfortunately that's about it. Christoph missing mouse pointer 1.mp4 missing_mouse_pointer_2.mp4

Dan C, well, you won't like the answer: it works just fine right now (and I tried!). I do not remember the tool (I think I used several), but what happened is that the switchover from the tool icon (hand, brush icon etc.) to the regular pointer arrow did not seem to work. Whenever you leave canvas area (not sure what you guys call it and move over to a tool bar or palette, the cursor disappeared) I had to use my touchscreen to make it work. I'll post in the appropriate forum if I experience it again. Thanks again for your help!

Thank you Dan C - the update seems to help. So far every image loaded correctly. As far as the beta goes, it does not always display the mouse pointer. (am I opening a can of worms here?) Christoph

Thank you Alfred and Dan C. Alfred's is easy: WIN 1909 - up to date, but the big update "is managed by my organization" which sounds rather Orwellian. Makes sense though. We are a school, and IT does not want any experiments during the school year. They told me they'd get to it soon. On to Dan C Correct, my screen can display HDR video, but that's about it. No support for apps etc. (see bonus image) see image 6 see image 7

Dan C thank you for your help! I am using Windows 10, whatever the latest Microsoft applied update is. The problem, however, has occurred in the past with older versions of windows. The camera that got it all started: a Sony RX100 V. After that: camera did not make a difference. See images - I made no adjustments simply opened and developed No ICC profiles were installed recently. It also drove me almost crazy because this morning the develop persona behaved just fine. But (I regained my sanity - phew :-): 1) Opening a Sony ARW file leads to a very dark, contrasty preview in develop persona. See image 1. This image has been simply opened in AP. I also show the Assistant Manager: nothing fancy has been applied. Simply hitting the "develop" button gets you image 2. This image looks very similar to the embedded preview in the RAW file. This was a Sony ARW file from a Sony RX100 V Opening a Olympus ORF file shows the same issue (image 3). ORF files are my bread and butter files - they have opened just fine in the past. Again, simply hitting the develop button yields image 4 so far so good (or bad). Now I happened to open a tiff file to work on. When opening the same ORW file again the Develop persona displays the image properly (image 5) In all these images I did not adjust anything. They are simply opened or developed using default presets. And for good measure: one of the offending ARW files (DSC-CEG_16018.ARW) Christoph DSC-CEG_16018.ARW

Ingenious question, Callum! Turns out I has a textured brush selected, once I switched back to basic brushes, everything behaved normally again. I would still suggest though to treat this behavior as undesirable. The numerical brush size does not correspond to the actual size. I am sure there is a programming reason for that, but from a user perspective it's less than ideal. Thank you! Christoph

The image displayed in the develop persona is way off: contrast is much too high, overall exposure seems to dark. The developed image looks pretty much like the image preview embedded in the RAW file. Everything worked fine until last week. Now, developing an image is impossible. I am using v. 1.8.3.641.

Oddly enough, the brush size cannot be properly adjusted using the right/left brackets, the brush size slider or numerical input. For example, starting with a 3000 x 2000 px image, setting a brush size of 4096 px should result in a brush larger than the image. Unfortunately, the brush remains tiny, probably the equivalent of a 100px brush. The brush scales, but is way too small. Erasers, burn brushes etc. scale properly, the problem is confined to the paint brush and color replacement brush. (those are the ones I found not working - there may be more). I m running version 1.8.3.641

I am glad I am not the only one who has this issue. The histogram function is often a hit or miss. Sometimes it seems to work, other times it doesn't. I hope it gets fixed soon.

Thanks MEB not sure whether that's all that useful to see all these masks at varying scales throughout the document. Even though it's a small quibble, I'd prefer them on a consistent scale.

speaking of the mask icon being a bit off: the black and white adjustment was only masked for the foreground rock at the lower left, though the mask icon shows a big black blob in the middle of the image. Maybe I don't understand those mask icons, but it seems counter intuitive.