DarkClown

Hey Timo,
That's great to hear. I'll get the team to investigate that. It seems as though that may have been the likely cause... we will do some further testing. 
Edit - saying that, I use special characters in my password but not the ' so that's perhaps what we need to be testing - extended special characters.

Hi Chris, thank you for your reply!
I'm not using password managers and already deactivated all firewalls as described above.
But changing the password for my account did the trick! So finally my license got activated and the programms start again as expected. Maybe your system is struggeling with some special characters. I used a  ' as one of my password characters what might lead to confusion on some systems. If this was the problem you should exclude this as a valid character for password entry on your website.
Cheers, Timo
 

Hi @DarkClown,

no, it's not an individual problem, I have the same issues with the trial universal license. First all applications are unable to connect, but are still working "as a gesture of goodwill", and some days later every application stops working. I signed up for the license via Affinity store.

Things I checked:
Verified my credentials, they work. Wrong credentials cause different errors. Reviewed my license inside Affinity store to make sure it exists. Switched off Windows Defender, no difference. Made sure that there's no other firewall which would restrict. All other installed applications, all other apps on other devices don't have connection issues. To the Affinity staff: that's the worst kind of publicity you can be responsible for. Your apps are great, but those circumstances with not being able to login and applications stop working completely (!) is a no-go. And the fact that customers are being left with their problem raises fears that it would happen again and again, f.e. when support ends, due to release of V3. 

Please take actions to solve this problem as fast as possible.

Jep, it's really nasty ... tried it on the forum for some days but this seems to be an idividual problem without priority. So I send them an email.

Wasn't aware that there were more differences - but you are fully right. I have to be more precise in my wording here!

In this case Mike was right. I just did not expect this setting to be misplaced somewhere completely apart from all the other settings. But I found it! I's a bit like searching for easter eggs

Those were not the impatient ... those were the grumpy
But I guess your assumption is most likely right ... and knowing about state of development will not increase the speed ...

Or to say it cinematic:
 

Many thanks for providing these for me!
I've been able to replicate this in Affinity Photo, however I also tried these images in PS 23.4 and received the following results:


Therefore I believe it is the source images used here causing confusion with the stitching algorithm.
In my testing, I found if I cropped the images to remove the brown border at the bottom, leaving the page only in the image, then exported out to .TIFF and stitched these cropped images together, the result was correct:

I'll be logging your files with our developers to help improve our stitching algorithm, but using the above crop method should allow you to complete this in Affinity Photo

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

Hi Lee, thanks for your answer.
I do understand where you are comming from. But as well I think we both agree that sharpening of a highres 24MP picture does not make sense if you need to have it sharpened for e.g. 800px web resoloution. Since I use a lot of live filters that sadly enough can not be resized (gaussian blur or perspective) without readjusting the parameters for each of them after resizing (which is not sensible for a non-destructive workflow) I was told by serif staff that I simply should not resize the picture and instead use the export persona for getting the proper output format. Apparently here the image gets flattened first and adaption of live filters can be avoided. But in this case I'm struggeling with the sharpening issue. So I'd be interested what would be the appropriate non destructive workflow from serif point of view?
Cheers,
Timo

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

Regardless ... Its got beautiful plumage!

Those were not the impatient ... those were the grumpy
But I guess your assumption is most likely right ... and knowing about state of development will not increase the speed ...

Or to say it cinematic:
 

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

I can confirm that it is the cropped group causing the issue, attempting to export a cropped group will ignore the crop shape on the group and will export the entire selection. This issue is currently logged with the developers for resolution.

Hi @DarkClown,
Feel free to upload your file to the below private dropbox link if you don't feel comfortable sharing here and we'll investigate further. 🙂
https://www.dropbox.com/request/QjfmPuewWwQwp4bUnseD

I wonder if the photoshop 8bi (additional file format) support is planned in the future. This would resolve some of the often discussed issues with non-suported file formats e.g. WebP since 8bi PlugIns are available already. 
Cheers, Timo

It's been more than 2 years people are requesting support for variable fonts. I'd like to bring this topic up since it seems not getting any attention. Of course this affects all Affinity products and not only Affinity Publisher.

And if basic font support does not make it to the essential feature requirements please make sure to handle this failure/bug with a bit of dignity (even Photoshop 6 disables the styles for variable fonts and does not display random nonsense)


 
Cheers, Timo

Yep, that caused it ... I had the node tool active and that caused the issue - works fine with the move tool. Same for the transform panel as well as the layer menu entries. Hard to undestand why transformation is not available with a different tool since it is a global layer operation. But obviously my mistake.

Thx Walt!

Thanks. For the Transform panel, make sure you have the Move Tool active. (Not at my computer at the moment, so can't try it myself, but that has caught me before.)

This is a valid point. Just as a suggestion for an easy to implement intermediate (or maybe even final) solution: Why not include a checkbox in the export dialog that will automaticall open the exported file in a new document in AP for further devekopment?

Ohh, don't bring up the old stuff ... Only gets me into trouble. I always get a shitstorm for reposting
But frankly spoken I had the impression that 5 years gone by justifies to put up a little reminder .... and we are not asking for functions to construct frequency separated intersections between penguins and octagons.
<sarcasm on>
And I guess it's still a huge surprise for serif that there are people out in the world that try to productively use their tools
<sarcasm off>

But as I said - let's hope for AP 2.0

@DarkClown I fully agree with you — it would be nice to have a kind of output sharpening parameters section somewhere in export options. Having to go through multiple rounds of exports seems very inefficient.
Btw, I found your thread from 2017 with the same question: 
Unfortunately, it seems like nothing has changed in this regard.
Hopefully we'll see some improvements in next versions.