Spud

NVidia 1050Ti with the latest Studio Driver. Hopefully all this info will help Serif find the little gremlin that is causing all this hassle. BUT it is only causing problems with Affinity, my other 3 photo processing software are running perfectly. I was almost going to try a clean start of W10 and everything else, then I remembered about 2004 on the horizon and decided against it.

I've been able to revert from WARP to my NVidia GPU (with the latest driver) for rendering after Windows 10 (1909) update yesterday to OS build 18363.1016. All I need now is for the Wacom pen pressure problem to be sorted.

I've also been having problems with my Wacom pen pressure - it don't work. So I uninstalled Affinity 1.8.4.693, the Wacom tablet and I rolled back the NVidia driver to 4274 as suggested in a post in another topic. Uninstalling was done via a commercial software package which cleans out all remnants of the programme. When I re-installed Affinity, it worked perfectly - insofar as Opening RAW file and progressing to Develop is concerned. There was no crashing and no blank screen for several seconds as mentioned above AND I've been able to change back to my GPU for rendering instead of falling back on WARP Then I re-installed the Wacom and the first thing I noticed was that the blank screen returned. To rub salt into the wound, the pen still didn't provide pressure sensitivity. (It's not on mouse mode and ==legacy etc doesn't work either). The Wacom driver is apparently incompatibility issues with Affinity. I've now uninstalled my Wacom and await Serif sorting out the problem. May try installing the latest NVidia driver when I feel like a bit of dangerous living.

Still don't work for me. I've now lost my pressure pen and have to go to WARP for rendering since updating. Someone up there doesn't like me!

Now ain't that weird!!! Same adjustment - opposite result.

It would seem evident that, from all the post in this Topic and other similar ones, that Affinity does not, in many cases, respond to pressure sensitive pen, despite Mark Ingram proclaiming that pen input is greatly improved. I even went back to NVidia driver 442.72 as suggested in another Topic, but to no avail. So much for Beta testing.

I tried this and it stopped pressure sensitivity in the 'Wacom Pen Settings' panel. Intuous Pro (M) pad about 6 years old, so had to undo. Pen pressure does work on another of my photo processing programmes. Pad drivers are up to date. Windows10 Home.

Thanks Chris. WARP + the System profile I showed is getting the job done. I can now open RAW files in Develop and then progress to Photo. Interestingly, I've just downloaded the latest 'Retail' version. Whereas the Beta performed as expected, the retail version has a 3 sec (approx) blank screen going from Develop to Photo, then the Develop tab with the blue dotted line does its thing. Presumably, at some update in the future, I will be able to come out of WARP drive and revert back to my 1050 as the renderer.

OK Chris. Job done as requested. See screenshot. Perhaps I'm being too demanding for a smooth transfer from Develop to Photo. I'm just trying to help by describing what I see. I have uninstalled the graphics driver a couple of days ago, swapped to the 'games' driver, uninstalled that and gone back to the Studio driver, restarting each time.

I haven't the faintest idea what WARP is, but it seems to have done the trick. Both AP and AP Beta now perform without crashing (tested 20 images with each) all with 'Apply Tone Curve'. However, the histogram doesn't populate instantly and the changeover from Develop to Photo makes the image go 'blocky' for an instant. (Can't recall whether this happened before the current problem started). So where do we go from here?

Hi Chris, As I've said before, the issue does NOT appear to be with individual files. This fault is GENERAL across all files, .nef,.dng,.arw. The file loads and then crashes. The appearance is as if the Tone Curve hasn't been applied. I've tried the Beta but the problem persists. Indeed, for some inexplicable reason, the problem of not being able to progress from Develop to Photo has returned. See screenshot of just before AP crashed. This is the 'darkening' I referred to earlier. Note, the histogram does not correlate with the image. The image was much brighter whilst the Develop tab with the moving blue line was operating. It darkened once that stopped. The blank, or under exposed histogram appears in the Develop persona. As I've stated earlier, there is an approx. 5 sec delay between the image loading and the app closing down with the histogram blank or showing underexposed. There are no selections in any of the cases. I've got an i5 8600 CPU with 32GB of RAM with an M2 drive. More than adequate to deal with the job I would have thought. Task Manager shows the CPU operating below 90% but, just after the programme crashes, the GPU spikes to 100%.

Hi Chris, Did the convert. No improvement. The only reason I mentioned the 'darkening' is because it precedes AP crashing when going from Develop to Photo. To summarise, my problem is that AP crashes in a random manner, either when opening a RAW image, or when the image is transferring from Develop to Photo. It may be my imagination but a crash when opening an image is usually preceded by a blank histogram for 3-4 seconds and the crash occurs when the histogram appears. GPU useage spikes at 100% when app closes. Also noted that AP power useage is 'very high' when opening files in Develop or going to Photo. It stays 'very high' for up to 5 secs. Other software seem to have blips at 'very high'. Just more observations in an attempt to help solve the mystery. I have carried out a clean uninstall of Affinity Photo, removing every trace from my PC. As a result, once I can get an image to load into Develop and the programme not crash, I can now proceed to Photo, which is an improvement. However, I still have severe problems getting RAW files to load. Some load straight away, but most need 2.3.4 or more attempts. In every case of the programme shutting down, the histogram is blank or indicating an underexposed image. I get a greater success rate if I turn off 'Tones' in the Develop Asst' prior to loading. If I then turn it on. I get a really well developed image. The new installation of AP still doesn't produce crash reports. However, I attach the latest user setup files in case they are of help. Can I have some feedback/help Chris? SetupUI.log Setup.log

Chris, forgive my ignorance but, search as I may, can't locate where to find the Convert panel shown in your screenshot. However, I enclose a screenshot from Device Manager for the 1050Ti and it shows something I don't understand. Don't know whether it's relevant or not. I also show a screenshot from the Colour section of Preferences. Finally a screenshot from my Control Panel Colour Management.

Thanks Walt, you live and learn..... David

Hi Chris, Noticed that if, in Develop Assistant, I change 'Apply Tone Curve' and 'Apply Exposure Bias' to 'Take no Action', when the programme crashes and I re-open it, my settings have been negated. David