thedakota

This is fabulous news, thank you, I really appreciate that you are listening to your customers. The launcher workaround got my workflow back on track over the weekend, and now I can look forward to the MSI installer once you've completed the necessary work behind the scenes. NGL, I was looking at the price of Affinity Photo V2 + DxO upgrade and it was almost exactly the same as a year's Adobe subscription. I was this close to going over to the dark side.

Thanks @Hans De SmaeleI agree your approach. Affinity have now acknowledged the problem and promised a solution early next week. I'm crossing my fingers this was just a tiny blip that we'll all have forgotten about.

Sadly still doesn't work in ACDSee. It opens Affinity Photo 2 (yay!) but then attempts to open every parent folder as though it was an image, so I get a series of "failed to open file" errors. I think I'll wait for this to be formally patched.

@Mark IngramI hear what you're saying. This is someone else's problem. But it isn't. Your suggested solutions don't work. If I abandon Serif and move to another application such as Photoshop, it's very much your firm's problem. I'm signing off now. Thank you to everyone in this thread including @Mark Ingramand other Serif staff. I appreciate you have to follow the party line, and your patience is very much appreciated.

Same error message. I'm also following this thread with interest. Looks like Serif has a lot of unhappy customers.

That exactly matches what I was already doing. I get an error message that prevents either DxO or ACDSee opening Affinity.

Which doesn't work for many users, including me. I get the error message "the file cannot be accessed by the system". That's why folks all over the internet (Ive seen threads on Facebook, Reddit, Digital Photography Forums and elsewhere) are looking for solutions that work. Is this an acknowledged bug that your Devs are trying to resolve?

I'd come across this method but decided against it because of teh security issues which @myclay highlights. I've found another way that doesn't involve changing folder ownership. 1. Create your .bat file as highlighted above and save it in a folder 2. Navigate to that folder in ACDSee to add it as an external editor 3. When you reach the folder, ignore "exe files only" and type the full name of your batch file - mine is called openaffinity.bat 4. Click OK This works with DxO Photolab too. For me, anyway. Curious to find out if it works for others.

Ah, thanks for the suggestion but I get the same result as @Grumpy Hec - a permissions issue prevents ACDSee from opening Affinity.

This is a deal-breaker for me. Hopefully they'll fix it in 2.01. Still can't believe they launched without a solution to this issue.

Joined the forum to report that this is my experience too. Using Windows 10. Film Pack works fine. Perfect, in fact. Thanks guys, much appreciated. But any changes I make in Viewpoint disappear when I click Save to return the photo to Affinity.