AiDon

Just for reference, the Renderer doesn't have any impact on the Hardware Acceleration. The Renderer is just the device that we use for presenting the final document to the screen.

The nvwgf2umx.dll crash? That's unrelated to the hardware acceleration but we do keep seeing it pop up a lot. Hopefully it will be resolved in due course.

The range is -100 to 100. For 32-bit Documents support.

Hi there. You are correct. That's wrong. I will fix that asap.
Thanks for letting us know.
Chris

Thanks Chris, it was just to give you a heads up as it is a general issue with Nvidia drivers at the moment where Affinity doesn't play well except with really old ones. I have a Intel HD630 I use as the primary renderer but it would be nice to be able to use the Nvidia GPU as it has dedicated vRAM. 😉

I'm locking this thread as it's getting off-topic/personal and it's already served its purpose as feedback/suggestion to implement full Photoshop plugin support.

No, what I am suggesting is that we be able to use images already open in the Photo Persona, doesn't matter where they come from, as input to any File-> New ... Process (except Batch) because the images have already been processed. There are also limitations such as afphoto images cannot be used to those processes.
Basically I don't see it as a new feature as the images are already open and they can be processed in any Persona so why not any other process that is part of AP as the fact is that you can open RAW images in those processes but those images are not processed in the same way as Develop Persona.

Link to previous here: 
 
The current situation is that there is no change to the issue of Hardware acceleration using Dual GPUs and extended displays.
1) Continual crashes with GTX 1050 as renderer giving a nvwgf2umx.dll 0xC00000FD: Stack overflow (HW A NO.JPG)

2) Works acceptably when using the Intel HD630 as a renderer. (HW A OK.JPG)

Comments are as follows:
Reverted the NVIDIA Drivers to v442.92 and the crash occurs in libpersona.dll 0xC0000005: Access violation reading location 0x00000219E6CCEB40. (Dump file is attached)
All crashes using the GTX 1050 as the renderer occur when CPU usage hits 100%, using the Intel HD 630 CPU usage stops before hitting 100%.
Also have attached details of the OpenCL used by each of the GPUs, they are different versions.

15c2d24c-1414-419a-b9eb-e71619eb99e4.dmp

Hi AiDon,
I got the black bar to appear for a second or two with OpenCL on. Will pass this over for investigation—thanks! 

Hi @AiDon, the retail versions are hosted on locations throughout the world to increase download speeds. The betas are hosted in the US, so may not be as quick, depending on the connection. Hopefully in the future we can improve the beta locations too, but for now, this is an issue between your ISP and Amazon in the US I guess.

Just download the driver directly from the NVIDIA website. There seems to be issues with the lastest drivers from NVIDIA.
The other option you have, if you have an alternate GPU (usually integrated), is to use that as the renderer in the performance settings or you can also use WARP.

Hi, As detailed in this thread the crash is now happening in the latest PRD version.
 

If you want some more I can also attach as it only seems to work for CR2/CR3 images. Sony & Fujifilm images have the Show AF Focus greyed out.

Have you tried it with the latest Beta, 1.8.4.676? On my system using 2 monitors there's no problem remembering my layout over both.

So, in summary, if I use the internal GPU as a renderer on either monitor the crash doesn't happen ... if I use the high-performance GPU as the renderer then the crash occurs. Driver is:

Hi Chris, the crash hasn't happened again but the lens adjustment should adjust the Vignette to 0 rather than 100 for APS-C lenses attached to the FF Sony cameras.
Regards, Don

Hey AiDon,
Apologies for not responding to the linked thread.
We are having issues accessing the FIle Request section of Dropbox. I have added it as a priority to my list. 

Note that this also happens in the Beta version so I have reported there. I also see it happening if I have any 3 images open at the same time in develop, the following I can reproduce:
uncompressed RAW from the A7M3 causes a crash compressed RAW from a A6400 doesn't crash CR2 from both 5DsR and 5D Mark III cause the crash CR3 from a M50 doesn't crash There is a dump from the Beta version that I have uploaded there.

Hi,
Crashing reported in the PRD version is happening with the  latest Beta (v1.8.4.665), the Beta created a Crash Dump which is attached.
 
e5c83c16-44bc-4115-908f-3087231a2dc3.dmp

Just a request to include corrections for the Sony FE 200-600 mm F5.6-6.3 G OSS (SEL200600G) to the lens corrections database. 

The problem started after the last update. Since reinstalling an older version of the program did not make any difference, my conclusion was that the bug must sit somewhere in my computer, maybe in the registry, So I used REVO Uninstaller to uninstall the program and really clean up the computer from all  'silly rests'. This worked: after reinstalling 1.8.3 evrything is normal again.
PROBLEM SOLVED!
Thanks for your tips 🙂, I had to try them out  before I concluded that there was an other problem.
Attached:
1.Opening the RAW file in Develop Persona
2. After pushing 'Develop' (without making any ajustments) how it opens in Photo Persona
No diferences, this is how it should be 🙂
 

Chris B
If you have an image that has a ratio of 1440:600, or you crop an image to that ratio, then when you set the long side to 1440px in the export dialog, the short side will automatically change to 600.  How do you wind up with 960 ???

Make sure they are copied to the Default Plugin Folder or the NIK program install folder is included in the Search Folders in the Plugin settings and choose Allow "unknown" plugins to be used ...

Thanks--didn't know if you saw my post a couple of posts up, earlier today, I'm using Adobe DNG.  Also using Bridge as a DAM and metadata tagger.   Between those freebie tools, Darktable for RAW processing, and AP for everything else, pretty good toolset.  
Would love it if now a few more things happened:
AP 1.8 adds the improved metadata editing they're working on.  And in the future, a DAM application, or integration with an existing DAM application.   Darktable adds native support for CR3.  

Hi Joe_cool,
Welcome to Affinity Forums
No eta for v1.8 (retail), sorry. There will be more new features added to v1.8 beta before the final release.