Tom Lachecki

PDF is never going to be a perfect format for exchanging files with Adobe users. I would far rather that Affinity produce PDFs that print exactly as I created them than create imperfect PDFs that are more editable in Illustrator.

This problem arises because a page layout program like Affinity is creating a PDF for printing and viewing accuracy, not for editing. PDF is a presentation format, not a file exchange format, so you won't always get perfect results and some programs are better at it than others. Just because Illustrator can't open it properly doesn't mean Affinity is doing anything incorrectly.
Download PDF Expert (there's a free version) and you'll be able to open the file for editing without problems. You could resave from it and then try to edit it in Illustrator.

Heh, not a bad idea. We'll start with collapsing the space left over by hidding preferences not relevant in the current app, and see how it goes  

Here for y'all to post on the forum like an intercom at retail: "Who owns the PC with the janky 4 monitor layout with varying resolutions and an Intel Arc+AMD combo. Your alarm is going off and your log is full. Please turn it off."

it's a UI oversight on iPad, will be enabled in the next build, and already is that way on desktop. I will add it to the Known issues list above

Hi, don't know about the iPad betas but on my Mac there is an option under general in preferences send anonymous usage information, I don't see this option in the release version. 

@DeepDesertPhoto Can you please attach the raw file? This likely requires a similar but slightly different fix specifically for your Nikon.

Thanks; that's a regression!
These will be added later. 👍

Thanks; that's a regression!
These will be added later. 👍

There are seemingly 2 issues.
1. Add-ons that require downloading through browser are not shown unless "Show incompatible packs" are selected. This is a regression since v1, where one didn't have to select this option to see them.
2. Some add-ons are not shown at all, e.g:
- Publication Typefaces Collection
- Wallington Pro – Typeface
It seems it's the case also for v1.
I uploaded screenshots from Photo v1 and v2 showing 1st issue. It's impossible to show 2nd one.
Issue applies to all Affinity apps, not only Photo.

For what it's worth, it does work using Import Content on Windows and on iPad.

Thanks!
It does indeed appear to have some useful information in the Makernotes, so we should be able to start applying that to the Date Shot field during parsing (when it's missing its own timezone indicator), then everything will be fine.

It doesn't, but only the new editable date/time widget in v2 shows anything in your local time.
v1 just parroted what you're seeing in the Detail tab - i.e. "whatever the camera told us" without any maths

This ought to be fixed in the next build, thanks  

This is by design. Content migrated from v1 is not "linked" across the apps, and there is currently no way to "link" Document Presets.

It looks like with the upgrade to macOS 13.1 this week Apple has forced a name change on all applications. Preferences is now named Settings to match System Systems.
I just updated my system last night and yesterday this was named Preferences for me. Serif is going to have to update their documentation.
Cheers

If the proxy exe, which is a zero byte exe, doesn’t work when calling from the application you are using please notify that applications technical support as it is a part of the windows system.
For example, ON1 products don’t work with this system but they are looking at updating ON1 Photo RAW to support zero byte exe’s. At this point in time Capture One does work and picks up the proxy in its plug-in list.
Obviously older applications that don’t work with proxies you will need to use alternate ways of calling. 
So my suggestion is that you use the alternate ways described on this forum and ask your application provider, e.g. like DxO or RAW Therapee or image viewer apps like XnView, to update their apps to support Windows features.

There is no v2.03, only a beta v2.03. Affinity mistakenly dropped v2.03 when it shouldn't have. They pulled it when they noticed. Some were able to update because they were opening their Affinity software during the hour before the mistake was discovered. Those discussing it on that book of faces thing got lucky.
When v2.03 is available they'll let us all know.

Sorry, Amber, that's my fault - I gave Dan incorrect information! The insert option absolutely should be enabled - this is fixed for the next update.  

There are no fonts bundled with the Affinity applications (except maybe in some add-ons which you would have installed manually).

So whatever fonts I see are those bundled with my computer, or else ones I've downloaded from elsewhere. Well that resolves that!
Thank you, Garry.

That one is also not a font file, and too small.
I think you will need the designer to send you the fonts they used.

Sorry, Amber, that's my fault - I gave Dan incorrect information! The insert option absolutely should be enabled - this is fixed for the next update.  

That preference applies to new categories (i.e. "Create Category").
Imported categories will always be linked by default.

This has been fixed for the next update; sorry!