Dan C

Hi all,
We're looking into a better implementation of Lens Correction in the develop persona, as there can be slight inconsistencies between the Lens ID as per the .xml files, as well as EXIF data supplied by the camera.
In many cases, the firmware of the camera may be older than the lens, so although the lens is 'supported' the EXIF data written is incorrect or inconsistent.
For outlier cases such as these, I've personally requested that the Develop Persona is given the same manual choice list that you can access through Filters>Distort>Lens Correction. This would allow users to manually select the Lens profile from the imported XML, even when the EXIF/XML doesn't detect the correct lens automatically.
In regards to a workaround for the time being, the XML file contains the values needed for the Lens Correction panel in Develop, so you could input these values and save this as a Preset in Develop, then apply this preset manually to any images using this lens. I hope this helps!

Amazing!  Thank you for such a detailed response.

If anyone is still having issues with StudioLink, please follow the below instructions:
If you're unable to access StudioLink in Affinity Publisher, make sure you have installed the 1.7.1 updates (as described here) for both Affinity Photo and Affinity Designer. After you have installed the 1.7.1 updates you will also need to run the apps at least once before reopening Affinity Publisher to access the StudioLink feature. If StudioLink still doesn't work, please try the following:
If you're using Windows go to %ProgramData%\Affinity\Common\1.0\appinfo\Release and rename the Photo Release.appinfo and Designer Release.appinfo files. (as Photo Release OLD.appinfo and Designer Release OLD.appinfo respectively) Once renamed, re-run both Designer and Photo and try StudioLink again.
NOTE: If this works for you PLEASE can you upload those renamed files to us to investigate further.
If you're using macOS, make sure that all Affinity apps ( Publisher, Photo & Designer ) are in the root of the Applications folder.
 
Please create a new thread if you can't link the apps after trying the above, so we can investigate this further, many thanks!

Hi Waltr,
Welcome to the forums
This is possible in Affinity Publisher, using the Layout- specifically 'N-up' -and Scale options of the Print dialogue. I've attached a video showing this in an 8page A4 document, laid out to print across 2 A4 sheets of paper. I hope this helps! Nup Printing.mp4

The second part of that (searching for a hunspell dictionary) will work fairly well, Dan.
However, there's an issue with the first part (using the OpenOffice or LibreOffice site), which is also mentioned in the Publisher Help (which should be updated).
In current OpenOffice and LibreOffice versions the dictionaries are all downloaded and installed as OpenOffice extensions, and they download with a filetype of .oxt which users won't know how to handle. At least one user has found that confusing already, as I saw a mention of .oxt files a day or two ago here in the forums.
What needs to be explained: A .oxt file is a kind of .zip file. To use it with Publisher:
Rename the downloaded file from <whatever name>.oxt to <whatever name>.zip (and accept any warning that Windows or Mac might give you). Unzip the renamed file into a new directory. From that directory, take the 1 or 2 .dic files and the .aff file and feed them into your instructions above. By the way, the hyphenation file is a .dic, not a .aff as you indicated above.
Thanks!

Thanks Dan C
Yes it was operator error as I later found. Your summary is correct I was not on the background layer. Coming from LR without layers so I have some things to relearn.
Thanks for your help
 

Hi Cecil
Thanks for your suggestion, this has been put forward by members of our staff here also, as we've spilt the Feature Requests, Bugs and Beta forums up into Application and device type, however as the Questions section encompasses all of the app, and many of it's behaviours, settings etc are shared between the three apps, we decided to keep this as one subforum so that new users could try and find an answer to their question, even if it wasn't posted for their specific app. I hope this makes sense!

Uh, right. [couldn't resist it emoticon]

If you switch on View > Show Text Flow, frames in stories with overflow should get red round markers in the main view. The markers are located where the link handles would be if the frame were selected - they effectively turn into the triangular handles when the frame is selected (and stay red for overflow).

Excellent response, while not OP, the Select>Grow/Shrink and grow the selection by 2 pixels. Now go to Edit>Inpaint and the selected areas will be filled with content aware pixels from the image, is key. Thank you. This procedure works if you select,  crop, straighten and find you have transparent pixels in your crop.

Well, then I would suggest making a change for the "Affinity Support & Question" subsection.
Where, at least,  MANDATORY check boxes are displayed for "Start new topic", that indicates the application for which the question or comment is intended.
And then put the choice made in front of the title.
e.g. [APho], [ADes], [APub]
I think that this should be possible and does not require that much effort to realize it ... (I suppose)
 
Me neither. and I think we're not the only ones.

Appreciate any change that would narrow the search group and also selectively allow members to modified their notifications.  As is, one should just turn notifications off and just read all unread.
I think this totally made sense initially with fewer programs and users.  As Affinity increased applications, StudioLink  and users (two million), things change.  I do thank you and totally realize each change is based on usability based on international community and OS.

Hi Gnobelix
We don't currently have plans to enable Plugins in Publisher AFAIK. The option under Filters has been made aware to our dev team and this should be removed in a future update!

Hi ArWi,
Welcome to the forums
Are you referring to the Welcome screen (seen below)? This isn't designed to automatically close unless a document is opened or created.

Did you install Designer onto a different HDD/SSD than your other Affinity Applications? If you've installed all apps on your C drive then your app data for Designer should be here.
I recommend trying a clean uninstall, then re-downloading the latest EXE and installing this again to try and help your performance issues. Please use the following Microsoft uninstaller tool to remove Affinity Designer and let me know if this helps.
https://support.microsoft.com/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed
https://store.serif.com/update/windows/designer/1/
 
Hi @Jorge Domínguez,
Welcome to the Affinity forums also!
Please try following the reset procedure below and let me know if this helps with your system performance
You can reset your app back to its default settings by holding down the CTRL key while launching the app. When the Clear User Data window appears, click Select All and then Clear. The app will now open.
Be aware that resetting your app back to its default settings will lose any custom settings such as keyboard shortcuts and brushes etc. To backup such settings before resetting the app, please watch our Affinity - Exporting User Settings and Keyboard Shortcuts video. https://vimeo.com/189596577

Thanks for that, I can see your issue is replicated with this file but I still cannot figure out why this is, as my document created adding the same masks/adjustments does not exhibit the same bug - therefore I've escalated this to our QA team and moved the threads to our Bugs section, one of our team members should reply shortly.

Thanks for your reports, we've been able to reproduce this and will have it logged with our developers now!

Thanks for your time and appreciate your response. This hot key makes a difference. Learning curve like with anything else, hard to complain as people like to expect everything to be a clone, just because they got used to other software for years. I purchased the whole 'holy trinity' of affinity software, eventually hoping to forget the trauma of years with adobe. People see a new chance and a new start and everyone wants to know 'where is that thingy I used for years in this software?". So excitement and irritation to be expected

Thanks for your reports, we've been able to reproduce this and will have it logged with our developers now!

I have now found out the method after seeing video on line and have started changing pictures to size I want.

Thanks, as I suspected a very basic error from my side

But until Photo gets a complementary "Edit in Publisher," there is no simple way to bring the edited version back into Affinity Publisher. There is also a risk of losing some work done in APub because of that, as I mentioned here.
EDIT: I added a reply to the topic I linked to above, which basically says I have been unable to repeat the steps that made it impossible to save unsaved changes in the 'parent' Affinity Publisher document after using 'Edit In Affinity Photo.'
So possibly the risk is minimal or non-existent, but it is still probably a good idea to save the .afpub document before using either 'Edit in' option.

Hi pawelcichonski
Not by default, but you can add one yourself in preferences. See my below video for it's location:
Defaults Shortcuts.mp4
There's no such option currently, I recommend posting in our Feature Requests section of the forums.
If you're referring to the Vector Brush tool you'll need to select the drawn curve with the node tool to add/edit the fill.

Thanks Dan, it overwrote the last version successfully without any work on my part whatsoever. V1.7.1.404 an excellent execute. Thanks so much. Now time to explore.

HI,
I've manage to fix it.  It seems that it had deleted the old affinity but left the short cuts, so I just downloaded the program rather than the update from my downloads and its all installed fine.  It's also working fine with publisher.
Thanks for your help.  Looks like it might be just a glitch on the update

Fixed it. Thanks for the help