[Affinity MAC applications when I bought Windows versions?]

Hello,

I just got myself a MAC after last PC went to hell, but now I realize that I don't have the MAC apps available. 

Do I need to rebuy all of them again or can it be transferred to MAC software?

[Crashing constantly]

8 hours ago, Chris B said:

I assume you've tried disabling Explorer Integration?

Honestly I have no idea what updates may have caused it. I recall seeing it around the end of March when we started working from home.

 

It never was enabled.

 

[Crashing constantly]

6 hours ago, Chris B said:

I'm just checking those .dmp files now. I suspect I'll see the Nvidia dll referenced. 

WARP will be so much slower so I'd recommend only using it when you need to stitch/stack etc. I know it's a pain to switch and you shouldn't have to.

I've seen a few customers report uninstalling and reinstalling Capture One sorted it (it must reset the explorer integration or something). We've also reproduced the crash after installing a fresh copy of Capture One but on the second run it did not crash.

Please know that we are actively investigating this on a somewhat daily basis. 

Update - It is the nvwgf2umx.dll crash.

It's not that WARP is slower, it's a lot slower, and Affinity crash almost always when selecting GPU just when using curves or other things, so I'm stuck in WARP as long as that works.

This have to be a new bug, because this wasn't before 20H2 update of Windows AFAIK, so could it be GPU scheduling messing things up? Just a thought. I know Microsoft did something with GPU in the very latest upgrade. Could it be that GPU scheduling is locking that DLL to something?

I know there are thousands of people running 1904/2004(?) update (not 20H2) and running Affinity quite fine side by side with Capture One. I run "Capture One Technical Forum" over at FaceBook with 4000+ members, and quite a few of them ditched Adobe to use Capture One + Affinity. I've heard of no such problem like this before 20H2 came out.

I reinstalled Capture One and no bueno, crashing like nothing before. Stuck in WARP mode. Thanks, I hope for a fix.

 

[Crashing constantly]

2 hours ago, Chris B said:

WARP crashes? Can you provide a crash report please:

...

So far no WARP crashing, but oh god how slow it is even with Threadripper. At least I can blend my panos better again than LR ever could, but it is really damn slow. Got a 1080 Ti idling at 0% usage 😪

[Crashing constantly]

51 minutes ago, Chris B said:

WARP crashes? Can you provide a crash report please:

Affinity Store version - Go to %AppData%\Affinity\Photo\1.0\CrashReports\reports

Microsoft Store version - Go to %AppData%\Affinity\Photo\1.0 (Store)\CrashReports\reports

You can acccess the AppData folder by pressing the Windows key + R on your keyboard and then just type %AppData%

If your crash report shows the Nvidia dll crash then that is usually linked to Capture One's Explorer integration. I don't believe it has to be running.

Ehm, It could be that I forgot to restart application when I changed that, WARP seem to work now today when I'm making a screencast.

Anyway, here are two dumps with some distance between. I hope it's safe to share here.

b58da2f7-bd8b-427f-bc2b-1205e4d2b241.dmp 93bf9013-938d-405a-953a-228cd9f2c897.dmp

[Crashing constantly]

Just now, AiDon said:

At the moment, as this has persisted since v442.xx of the NVIDIA drivers, the only options we have are to use either a integrated GPU as the renderer ...  or WARP if you don't have one.

Oh.. I have a workstation with 1080 Ti, no integrated GPU. WARP also crash in Affinity.

[Crashing constantly]

13 hours ago, Mark Farrington said:

I'm getting exactly the same issues with fairly repeatable crashes when pano stitching; CO isn't running, and this persists after a fresh restart. Latest Affinity, Win10, nVidia Studio driver etc etc.

This is going to be a _really_ major issue for loads of CO-Affinity users who don't want to go down the Adobe route for whatever reason (e.g. Fuji shooters). Basically, we're all going to bale and go for DXO, or whatever...

I have posted an enquiry message on the CO forum support page, quoting selected messages on here, and it's going to be interesting to see what emerges. Like many people, I have a big CO commitment/investment, so we won't be switching from that.

Hello, thanks for adding your issue too. It seem like there are more and more having this issue the more I try to find fixes for it, but it's good to know too because there might be a fix sooner or later then. Well, that's what I'm hoping for anyway before I'm forced to keep Adobe for a whole year again.

I can reproduce every time I try stacking, it just crash completely. What's more random is the crashing while using filters and other functions in the program. I can't reproduce that with accuracy.

Yeah, this is already a major issue. I was going to edit a couple shoot's I've done and use the frequency separation and some pano landscapes, but it just crash so much that I had to resubscribe to Adobe again to get Photoshop back on track. For me the DxO isn't enough, I need either Affinity or PS. I need something that works so that people who pay me actually get their product by a reasonable time. I can't sit around waiting for a fix for weeks or months, people would use other photographers then, and it is hard enough right now as it is with this Corona plague.

Good. I hope there will be some answers or help. So far no-one's asked me about logs or anything. If I had problems with any other application (Capture One for instance), the developers would be early asking for those logs to see what happens.

Please keep me updated if you find any hotfix, I'm running out of time before I have to keep Adobe for a whole year. Cheers

Aleksander

 

[Crashing constantly]

1 minute ago, Chris B said:

We believe Capture One is calling some Nvidia dlls which are in use which is causing Affinity to crash. As far as I am aware, this is something we cannot fix and it's a problem with their Explorer integration. 

But Capture One isn't running and isn't listed in "task manager", so I find that strange if this is happening. Hm

[Crashing constantly]

I went so far as reinstalling Windows. Still same errors on a fresh install.

I guess I'm off Affinity then - again. I wish it was usable and we could trust it, but it is simply not good for people with Windows workstations then.

Cheers

[Crashing constantly]

On 11/9/2020 at 3:41 PM, Chris B said:

@atefoto - You might be seeing the nvwgf2umx.dll crash that we have been seeing. This has been typical with HDR merging or Panorama stitching etc. Do you have Capture One installed?

@Ricky Taylor - This is the Windows forum and you're on a Mac so your issues with be unrelated to what I suspect atefoto is seeing.

If you're crashing or hanging with what sounds like a number of different things, I'd recommend resetting the app:

Mac App Store:
Please go to this location - \Users\username\Library\Containers\com.seriflabs.affinityphoto\ and rename affinityphoto to affinityphoto.old

Affinity Store:
Please go to this location - \Users\username\Library\Application Support\Affinity Photo\ and rename Affinity Photo to Affinity Photo Old

Trying again in case you didn't see it. I'm desperate to get it working.

Yes, I have Capture One as my daily driver as main RAW converter because of workflow and out of office edits. Does that matter? Are there some files affected by having Capture One installed?

I do notice crashes in other tools too, but it's mainly as you say - when stacking brackets.

[Crashing constantly]

1 hour ago, Chris B said:

@atefoto - You might be seeing the nvwgf2umx.dll crash that we have been seeing. This has been typical with HDR merging or Panorama stitching etc. Do you have Capture One installed?

@Ricky Taylor - This is the Windows forum and you're on a Mac so your issues with be unrelated to what I suspect atefoto is seeing.

If you're crashing or hanging with what sounds like a number of different things, I'd recommend resetting the app:

Mac App Store:
Please go to this location - \Users\username\Library\Containers\com.seriflabs.affinityphoto\ and rename affinityphoto to affinityphoto.old

Affinity Store:
Please go to this location - \Users\username\Library\Application Support\Affinity Photo\ and rename Affinity Photo to Affinity Photo Old

@Chris B Yes, I have Capture One as my daily driver as main RAW converter because of workflow and out of office edits. Does that matter? Are there some files affected by having Capture One installed?

I do notice crashes in other tools too, but it's mainly as you say - when stacking brackets.

 

@Ricky Taylor Me too, I hate the subscription model. Oh, I guess I have other issues then like @Chris B mentioned above, probably because of my Capture One or whatever. I hope so, I got all the errorlogs but no tool to read it, and lack of care and understanding to do so 😅

 

Cheers

Aleksander

 

 

[Crashing constantly]

3 hours ago, Ricky Taylor said:

for a short while i was using a AMD WX7100 eGPU  but stopped as it was running way too slow (i now understand why..).  changed the base preference in AP to only use the internal GPU that comes standard / build in.   two weeks ran fine, until the past few days.   if i use a plugin ''crash' a simple live filter 'crash'  a small file of a few layers 'crash'. - on and on it goes....i'm at a loss as to what is happening.    I consider myself a rather advanced user of the Affinity apps,  and i feel i can confidently state something is whacked on the software side right now,     wondering was there an update?   

Maybe there was a Windows update, I'm guessing you're on Windows right?

I'm on latest Windows and using nVidia. Fairly new install of OS and system too. I have tried everything from Adobe, Luminar, On1, Exposure X6 and Capture One, but Affinity seem to be the only one having issues.

It crash when I try to stack, doesn't matter RAW or JPEG. If I try to stack then it just exits to desktop.

It also crash randomly using regular filters and tools too, and I don't get a lot of work done before it crash so it is getting useless to open this software.

I'm a novice in Affinity but have years with Adobe. I had to reactivate my subscription just to get some images finished, and it's a bit sad when I hoped to not pay mothly at this time with this little work. If it's not fixed within 29(?) days then I can't abort the subscription again without paying rest the full year. 😕

[Crashing constantly]

20 minutes ago, Ron P. said:

Sounds like you're running the current Beta, 834. I can't run it with Hardware Accel active (OpenCL). IF you are running the Beta, either disable hardware acceleration or just don't use the Beta version. There's not any way to set hardware acceleration in the current retail version, that's why I'm thinking your running the Beta.

I have tried these two in standard version.

 

And I have installed and tried BETA too since you mentioned BETA, same crashing there.

[Crashing constantly]

1 hour ago, Ricky Taylor said:

Also for me,  the last two days has been a joke!   it does not matter what function i'm using it will stall and enter 'AP is not responding' - leaving me to 'force quit' i'm on MAC OS 
I've deleted the application, reinstalled and still issues. 

I'm on a spec'd out MAC so can't be down to the computer.

I'm a heavy user of this app, never had issues like this before, what the hell is going on?  i have work to do and need a functioning application ! 

Thanks Rick

Are you using nVidia card in your Mac? I'm trying to sort out if its OpenGL/CL or whatever else it can be... The problem increases with more GPU intensive operations - in only Affinity Photo. Rest of my apps are fine.

[Crashing constantly]

Crap...3rd day in row since I installed it and still crashing.
No solutions, tried it all. Guess I'm heading back to Photoshop 😕

[Crashing constantly]

Hello,

I have issues with latest Affinity Photo. I just installed it on Windows 10, latest version.

It randomly crash when using HDR merge, sometimes when using tools in tonemapping, sometimes it crash after 1 second if I select "automatically remove ghosts".

I have tried this so far:

* Reinstall of application

* Reinstall of nVidia driver

* Adding TdrDelay = 8 in regedit

* Changing from GPU to CPU/software in Preferences.

It also crash when editing regular RAW files in tonemapping or randomly when adding adjustment layers. This is driving me nuts.

Please help

Aleksander

[Apply Image]

Too bad video on that post is gone

[Apply Image]

On 7/24/2019 at 1:29 AM, ErrkaPetti said:

Look here @atefoto

 

Thanks, and sorry for late answer..

I'll have a look at it and reply tomorrow or so

Cheers

Aleksander

[Apply Image]

Just now, ErrkaPetti said:

Yeah, this function is there somewhere...

I’m away from my Win-laptop & iMac, but it should be pretty easy to find under filters...

I’ll be back to tell you more later...

I found one, but It's not close to what I need or know from before I just wonder if I missed something or if there's another one similar to Adobe's PS CC "Apply image".

[Apply Image]

Hello.

Is there any "apply image" function in AP similar to PS CC's own "apply image"?

I want to use it for "apply one channel of N layer to current selected mask", or "apply one channel to another channel for RGB mixing - with different opacity and blend modes", etc.

It's one of my most used functions in PS CC.  I use it almost daily in the winter when it's dark outside, just to give blue channel better SNR by replacing whole or part of the noisy blue channel.

Thanks

Aleksander

 

[GPU, disappointed]

3 minutes ago, Frozen Death Knight said:

Have you tried a 1x1 px canvas yet?

No, does this mean it is user error?  

 

[GPU, disappointed]

12 minutes ago, Mark Ingram said:

If you run out of VRAM then the OS has to page from system memory which has an enormous performance penalty. If you want to access memory from a GPU other than the one you're currently running on, then you have to transfer it across the PCIe bus, to system memory and then back out across PCIe to the other GPU. Again, there's a huge cost there.

At least my nVidia 1080 Ti got 11 GB Vram, so it can't be that  

 

[GPU, disappointed]

 

8 minutes ago, R C-R said:

Yes it should, but that takes us back to the number of hardware configurations, drivers, & so on that Serif is trying to support on the Windows side. They can use all the help they can get with that, including providing as much detailed info about the configuration as possible.

Just sayin'.

I agree, but I also think "the Apple Approach" which some people use is the wrong way to do it, blaming the users or hardware before considering bugs or optimization. I've lost count how many times people suggested this to me - including on this forum under current or my old user.

I got no problem sharing logs and config with Affinity to give them more to work with, but I'm told "you're doing it wrong" or "your pc is configured wrong" quite often, even on fresh installs  

I  saw one guy on this forum getting told he got a bad or slow "PSU" (Power supply unit) and thats why it laggs.. Go figure.

15 minutes ago, Frozen Death Knight said:

I'm on PC, just like atefoto.

Yay, Winblows. Wuuu

-----

Time to get out hiking and shooting some, later

Aleksander

[GPU, disappointed]

14 hours ago, walt.farrell said:

There was at least one thread about Affinity performance issues specific to Threadripper, here. However, that was resolved as being an issue with G-sync and drivers, I think, so may not be relevant to @atefoto's performance issue.

Thank you for linking, but I'm afraid I need a G-Sync or FreeSync monitor to fix that issue. I "only" got a "normal" AdobeRGB monitor. No place to disable Gsync or 

Aleksander

[GPU, disappointed]

13 minutes ago, Bryce said:

I have CaptureOne and I dont' find it that smooth on the Mac. It's fast and does a great job but I don't find it near as smooth. Adobe products certainly aren't that smooth even with video acceleration turned on - at least not like Affinity. Even the 2015 MacBook Air is smooth in Affinity so it does not have to be an expensive or new machine. I even have it on a 2009 iMac that does not have any acceleration for Metal and my one employee likes it a lot better than Indesign.

Your system looks great and is better than pretty much anything that people are running it on here. Now I do wonder if maybe there is a setting in your video card drivers that is causing the issues by not having 2D acceleration turned on.. Can you assign app refresh rates? Part of the issue looks like refresh is not high enough, like playing a game on a bad screen or maybe worse. I Have windows 7. If I can get Affinity to let me use one of my keys for Windows, I'll see what it does.

CaptureOne is the fastest app I got except for Photo Mechanic. I can have 10 layers with luminosity masking, curves, sharpening, etc, and still no slow-dows.

""Now I do wonder if maybe there is a setting in your video card drivers that is causing the issues by not having 2D acceleration turned on.""
Then I would have problems in the 10+ other editing apps I own, wouldnt I? But no, only in the 3 apps of Affinity.

""Can you assign app refresh rates? Part of the issue looks like refresh is not high enough, like playing a game on a bad screen or maybe worse.""
Yes, 60hz on my BenQ SW2700PT QHD 99.6% AdobeRGB monitor.

I don't believe for a second that this have anything with a setting or misconfiguration. All nVidia settings are default and Affinity is just as slow before and after reinstall of Operating system. The PC is built by professionals.

I can edit 4k and 6k videos no problem while watching Netflix and run a game, and only then I'll notice CPU have to work.

It's no logic that Affinity Photo or Designer should be like this when it's the only open Window I got, and the picture is only 400px.

We are talking about I can do everything else in the world on the PC flawlessly, except have a great experience with the Affinity Apps, so for me it is quite obvious that its not a setting, its not bad this or bad that, it is simply not support for real hardware acceleration. My reasoning: CPU; never above 30% and GPU never above 15%.

Aleksander