Tom Lachecki

Hey DCC, welcome to the Affinity Forums.
Are you clicking Apply in the Lens Distortion dialog?
I've noticed if you leave the dialog open and go to File > Save, once the file has saved, the distortion will reappear. 
If that isn't what is happening, would you mind doing a screen recording so we can see what you are seeing?  

Can you try the following to add Photo as an allowed app and then try saving again. I assume that saving locally to another location or the desktop is unaffected.
Type Windows Security into the search field on the taskbar then > Firewall & network protection. Now select Allow an app through the firewall, then on the Allowed application window select Change Settings > Allow another app > Browse. Now browse to C:\Program Files>Affinity>Photo, select the Photo.exe and click Open and then Add and OK, close the other windows.
 

Hi p10n,
We are aware the Edit With > Affinity Photo isn't working. This issue is logged to be looked at. The extension however should work correctly. Have you renamed or moved Affinity Photo from the root of the Applications folder to somewhere else?

Hi @Chris_Pearson, thanks for your feedback. The Affinity apps will load colour profiles from 4 places:
1) Profiles attached to a monitor
2) System profiles in Windows (C:\WINDOWS\system32\spool\drivers\color)
3) Installed profiles in Affinity Photo (C:\Program Files\Affinity\Photo\Resources\icc)
4) User profiles in Affinity Photo (%APPDATA%\Affinity\Photo\1.0\profiles)
There is a bug with loading profiles from (4) at startup, in that it is only checking for *.icc files. This should be trivial to fix, to allow *.icm files as well. Importing a profile via File | Import ICC Profile will filter for *.icc files, but if you type *.icm into the filename box it should work as expected (until you restart the application). I'll fix this as well to add the *.icm filter.
With regards to the "loading of profiles from the network", that's more of a feature request than a bug. How does Photoshop work? I looked at their documentation and it suggests that they only load colour profiles from the system (1).
Thinking of a work around for your problem, perhaps you could setup a symbolic link from (4) to your network share. That way we would load from the linked network location, rather than AppData.

Look at the Options pulldown at the bottom of your post, next to the Quote and Edit buttons.
Now that I've replied I don't know if it will work or not. If not, just Edit and delete the post content.
Or, perhaps best, leave it as a reminder to someone else who thinks they have the same problem, but really just made the same mistake. Nothing to be embarrassed about.

Yep, beta release has fixed the problem. Thanks for sorting it out.

Today, a new end user version of Photo was released. so the last Beta is older than the release Version and won’t work any more. A new beta isn’t availabe at the moment. So just check the AppStore to update your copy!

As I wrote: The final version 1.7.1. IS already released. Simply have a look into the Mac AppStore!

Just a little suggestion for betas... It would be nice if all betas from now could have a Beta sign in their icon as there was for the early betas of publisher... it helps easily recognizing them in the dock... 

Just an update after doing some testing last night with 1.7.1.385, and the ongoing denoising/demosaicing issues (not sure which was causing the problem) which made Merrill (SD and DP Merrill series cameras) barely usable, now appears significantly improved. Before, there was so much noise evident (mostly chroma, but also some luminance) even with reasonably well exposed images, that to get rid of sufficient noise resulted in also removing so much detail that the output almost looked like a stylized cellphone oilpainting filter. NOTE: this problem only occurred with the Sigma Merrill cameras, and did not affect earlier Sigma cameras, which performed normally.
Now, it is possible (for well lit areas within an image) to adjust the denoising so that you can just apply enough to get rid of widespread noise, but through the currently available controls, selectively adjust the extent applied such that a balanced amount of detail can be retained (meaningful noise:detail tradeoffs). It still needs a fairly bright exposure, but it is no longer prohibitive. I don't know if this was due to the hard work of Affinity or LibRaw, but thank you very much.
I ran out of time, but images captured as pure BW may still be opening in AP as colour. I will test with .390 this weekend. But this is a huge quality improvement for all Merrill users.

Hi abarkalo,
All changes we made are first implemented in the Customer Beta version so a large number of users can also test them and report issues if they want. We then release an update for the retail versions which include all those fixes. If you don't want to use the Beta (and you shouldn't if you are using the application for critical/commercial work), uninstall it from your system and just use the retail version you bought. Minor updates/fixes like these will be quickly available as an update soon.
Only the major 1.7 release took exceptionally more time due to all the code changes/integration necessary for Publisher.

Hi betrained,
Just a quick update, our QA team raised this with one of the Devs and he's fixed the issue today and the fix will be in the next beta of Affinity Photo    Not sure when that beta will be starting but it will be posted here in the beta section of the forums  

Thanks so much for your files, which all show more examples of the issue found and reported internally last week.
So this turns out to be an (unintended) consequence of a (late breaking) change to the code made for Affinity Publisher. It only affects compressed (like JPG) files.  Although Affinity 1.7.0 files are much bigger they will not continue to grow and grow, this should be a one off jump.
We will look at fixing this, but right now we are making Release Candidates of Publisher 1.7 now (with 1.7.1 updates for all other desktop apps due at the same time). So this close to Publisher release the developers do not want to risk putting a quick (untested) fix in. Therefore the 1.7.1 Photo and Designer updates next week are unlikely to be able to address this, sorry, but it will not be forgotten and there should be a beta soon after that addresses this issue.

Hi Everyone in this thread
I've spoken with the Dev team and the issue with the AF regions being in the wrong place for @Ron P. has been resolved and should make it into a future update/beta.
For the Nikon users (myself included) there is still some work to be done in this area, the AF data is there, it's not in a format that Photo can currently read.  So hopefully this will start working over the next few builds  

I solved my own problem in an "EUREKA!" moment. Maybe my blunder will help someone else. It has been awhile since I have edited photos & I forgot an essential step in my workflow. What I did was upload pics from my camera to the "Photos" ap on my Mac, then I dragged a photo directly from "Photos" onto the AP icon on my Mac's taskbar. What I was SUPPOSED to do was EXPORT the photos as original files from "Photos" to my Mac, THEN drag these exported photos onto the AP taskbar. All is now well. BTW - I'm impressed with your really prompt reply!

It looks like quite a few users are experiencing an issue with plugins that would load in 1.6 but are failing in 1.7. Please see this reply from Mark who has stated that we will attempt to reach out to the plugin developers to see if we can reach a solution.

1. New Document > Photo > 4D (6 × 4.5 in)
2. Press ‘OK’
3. Choose ‘Resize’ from the Document menu
4. Choose ‘Canvas’ on the Context toolbar
5. Make sure the aspect ratio is locked
6. Change the height from 4.500 to 7.500
Expected: Width changes from 6.000 to 10.000
Observed: Width changes from 6.000 to 9.333
Tapping on the Width control brings up the keypad, displaying 9.333 as expected. Tapping to dismiss the keypad (whether via the ‘OK’ button or not) makes the height drop to 6.750.
Edited to add: AD 1.7.0.7 (mis)behaves in exactly the same way.

Thanks Alfred. Logged with the developers.

I keep having a problem and it's just occurred to me that it is because Affinity apps behave differently to most other apps.
The problem is that when I 'Save as' or 'export' that the directory / folder location defaults to the last location used for saving as or exporting rather than the location the file that is currently being worked on which, as far as I can tell, is the default Mac behaviour.
We have numerous projects, each with a standard folder structure.
The result is that I keep saving files the wrong locations because, at a glance, it looks correct (ie 'photos' folder) but is actually the photo folder in a completely different project.
It would be great to be able to toggle this in the settings.

This issue has been fixed in the latest beta build. Thanks for your help finding this.

From practice out I can say the leatest beta on windows 10 is more stable then ever before.  Yes There are glitches there is a beta for. 
So Affinity team you are on the right way.

No, Affinity software doesn't come with any Adobe software (we're two different companies). However, you should check out our Publisher application, which is designed for this purpose:
https://affinity.serif.com/en-gb/publisher/

Did you restart the machine after changing the display scaling to 150%?

Andy...
I know this is more a cosmetic change than a functional one, but thank you (!) for adding "Focal Length" to the EXIF Summary. It was the one piece of data I thought was missing, and it's nice to have it so readily available. I continue to enjoy this application so much!

Sorry, I did it wrong, I think I have left that directory earlier in Resources. Now I have copied my compact-panasonic.xml to the right path, and it works fine. Thank you!