OzNate

Same. I think I started in '95. At first I thought CC was cool, but that didn't last long. My only regret was not upgrading to CS6 perpetual and staying there. I went from 5.5 to CC.

Not going anywhere yet. I think it's way too early to tell how it will all pan out, but if the most dreaded things happen, then we'll for sure be back to looking for alternatives.

Ooh, you're right!

I'm sorry to be like this but the first thing I did was to run a comparison of the EULA from before and after. Given recent developments. They are the same.

Exactly

I support that

I feel like I've been here before. Adobe bought Macromedia, who made my favourite software. It didn't end well. That was before subscriptions, which is worse and why I'm here. I'll still be a user for now because you're still the best option but I will be keeping an eye solidly on open source and other alternatives. I think it's fair to say many of us feel no enthusiasm at all whatsoever about this.

FYI, yesterday I allowed Windows 10 to run an update and today I had this problem again. 🤔 After resetting in Publisher (via holding Ctrl and choosing to reset including "Deactivate" option), it would no longer start or show a splash screen, but Photo and Designer gave a splash screen, then an error: "Sorry, there was a problem launching the application. Cannot communicate with other Affinity apps. Please ensure the app is up-to-date and that your firewall isn't blocking local network traffic." Restarting the system fixed the error message and apps now work again (obviously had to reactivate). So it seems to be a problem with activation, and brings back nightmares we used to have with a certain other creative software company's products, so I do hope this can be fixed. 🙏🏻

Solved my issue by choosing the last option when you hold Ctrl while starting up - "Deactivate Affinity 2 apps" After this I was able to step through reactivation and the apps started normally.

I'm having this issue but it's not newly downloaded for me, I have been running V2 for some time. I don't know if it's related to the other threads about files opened from server but I sometimes do work with Photo files on a server. But all three apps are not responding upon attempting to open them. I have tried uninstall/reinstall and clearing settings via holding down Ctrl. I have also updated from 2.03 to 2.04. No success so far. I have installed from MSIX and I'm on Windows 10.

Thank you, this was the issue that brought me here to the forums. Typing in font selection box causes immediate crash.

I agree that placing multipage PDF would be great as we used to do in InDesign.

Hi, I came here looking for solutions and I do see that Layer > Convert to Picture Frame works for me to restore a lost outside stroke as long as I don't then crop it again. Let me just say that this should all be a bit more intuitive. Pixel vs Image object is a distinction that I'm going to have to get my head around. I am laying out a newsletter where I am dragging images in from a file browser and applying a style to them, and sometimes cropping where necessary. I just want it to work. :-) Cheers, hope the developers can help us out a bit. :-)

The way I understand it, the only thing that makes a Designer file different to a Photo file or a Publisher file is the filename extension. Inside they're all the same. You can try it if you like. All apps will open all files. The difference you'll experience is how each program works with that file and the options and tools it exposes. So that's why it's tricky to add something to Publisher, because you're also simultaneously adding it to Designer and Photo, and on all platforms.

That quote from Affinity in Peter's post above is what has me worried. A killer feature for Affinity apps is that they are so interoperable across all apps and platforms, with the same file format for everything. I am just hoping that as we move into more Publisher-specific features like footnotes, data merge, etc, that this killer feature doesn't become the achilles' heel.