Steel Rat

Count me in as needing DDS support. Yes, Gimp supports it and is free, but it doesn't support the newer DDS formats that newer games are using.

Doesn't seem to be consistent. I tried it. Created a new .aphoto file. And opened the export screen. As soon as I changed one of the options, it said the file was modified. Tried again with another existing file, and it didn't show as modified when changing the export options.

I see. So it only happens if I change the export options, not just exporting itself.

I searched for this, but could not find anything. When I'm editing a .aphoto image, and save it, then when I export, it then shows the .aphoto file as "modified", when no modifications were made. Why would an export be a modification?

So... imported styles have worked for everyone else?

A PNG base layer. I have a macro which applies the style and crops, done it thousands of times. But when imported, the style portion of the macro didn't work, neither did the style work manually. I had to create a new style, and new macro, and both work now.

I tried searching for this, but nothing relevant came up. When I installed Photo V2, it asked if I wanted to import all my custom stuff from V1, and I said yes. They came in, but the styles don't do anything. I had one that I used often for a simple outer shadow with specific settings, but nothing happened with a layer selected and clicking the style. Anyone else seen this?

I always turn off startup panels in every app, lol. I didn't block emails from Affinity, because they weren't sending me stuff daily. If they had been annoying, I would have unsubscribed. So I saw the V2 email and purchased.

I've been using XNView for close to 20 years now. At the time, I tried others, like ACDSee and FastStone, but XN did what I wanted it to in an easier way, for me at least. I'd also be interested in an Affinity-based image manager.

There's no reason you couldn't install it now, and uninstall it when the MSI is available. Unless you had other reservations about the MSIX in general.

Thank you Mark, and the rest of the staff!

You don't even need the cd command. Since the alias already points to that. only the second line is needed. I just tested it and it works fine. Better than your first suggestion (which does work and I was using), which will break after the first update. The bat file should be good indefinitely.

The aliases did not work for me. I had to use the actual executable buried in Program Files\WindowsApps, which is typically hidden by Windows. I know that path name will change on an update, but I see that They are going to offer traditional MSI installers for those who want it, so I'm happy to wait.

In it's current form, it is of zero benefit to me. I won't spend time on workarounds that may or may not work.

It doesn't. If it did, I would never have found this thread.