When I tried to work on very large images, the problems were worse. For example, I have a pano that is something like 26,000 x 6,000 pixels and it was impossible to do any DM changes.
Can you help elaborate on this on the issues that you ran into when you did it?
I think I did a clean install when I switched to the Creator drive around August 1st but I may reinstall just to make sure.
Just to be clear, are you recommending switching from the Nvidia Creator driver to the Game driver? From Nvidia's web site, I thought the Creator driver was recommended for Adobe products as well as other 'creator' products.
With respect to the pano issues, i have a panorama that is 22675 pixels by 8903 pixels. With the GPU enabled, I was pretty much unable to do any edits to that image. Moving sliders seemed to make no difference in the displayed image or make crazy changes. Here is a screen capture showing the problem. The first image is when I first go into the develop module. The second picture is what is displayed after barely moving the temperature slider.
The worst part is it isn't consistent. If I touch the temp slider and move it a little in the opposite direction, either nothing changes, it goes back to a normal display or it changes in some other unpredictable way.
Also, though it seems to happen much faster with the large pixel dimension pano, I see similar issues with other, smaller images over time.
It almost seems like moving a slider is acting like a different slider is being moved...
Hi Walt, we currently do not support SLI mode, so the first step I would suggest is to turn that off. But it sounds like you already tried that, and it seemed to make things worse.
This is not what I expect, and the NVIDIA 1080 Ti card is one that we've tested in-house and should support. We have been using the game-ready drivers (at the time of development, the creator ready drivers were actually a little older).
Would you mind running dxdiag (the diagnostic tool built into Windows) and sending us the log file for that?
As I said, I thought I'd done a clean install when I first installed the Creator driver right after it came out but I'll be able to a reinstall in a little while just to test that out.
I'm relatively technical and willing to try things or check things out at a deeper level if it will help.
Do you recommend using the 'default' settings for lightroom.exe in the Nvidia control panel 3d settings?
Thanks, Walt
------------------ System Information ------------------ Time of this report: 8/29/2019, 18:16:49 Machine name: THEMIS Machine Id: {56946B3C-5044-4C74-9A88-A2B46777C693} Operating System: Windows 10 Pro 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202) Language: English (Regional Setting: English) System Manufacturer: Alienware System Model: Alienware Area-51 R3 BIOS: 1.0.4 (type: UEFI) Processor: AMD Ryzen Threadripper 1950X 16-Core Processor (32 CPUs), ~3.4GHz Memory: 65536MB RAM Available OS Memory: 65418MB RAM Page File: 59671MB used, 15473MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 144 DPI (150 percent) DWM DPI Scaling: Enabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: Unknown DxDiag Version: 10.00.18362.0267 64bit Unicode
------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Input Tab: No problems found.
Ok, did the clean reinstall and at first I thought it was working but after going into and out of the DM a few times and a round trip through Photoshop on one of the images, problems returned. Here are two screen captures of a different image which is 11648px X 8736px. I took it into DM and made some small changes and the displayed image got patchy. When I go back to LM, it displays correctly but if I go right back into DM it is still patchy.
When I first went into DM, 9.4GB out of 11GB of VRAM was being used. After going into and out of DM and the round trip through PS, VRAM usage is up to 10.4GB. I could be wrong but it seems like the problems start showing up when the usage is over 10GB.
Walt, thanks for the info. Out of curiosity, do the problems occur if you stay only within Lr (without going into Ps)? Or, do they still occur when going into & out of the Lr Develop module.
The driver package that you have should work correctly -- that's the same one I have in my dev machine, which is also running a GTX 1080.
The 4K display should be no problem. We've been testing internally on displays up to 8K. On my 1080 system I also use a Dell 4K display (a slightly older model than yours).
Ok, I think I have a little more info. After doing the clean re-install and sending you the images above, I noticed SLI was re-enabled so I disabled it again and rebooted. Things seemed to be a lot better and VRAM usage was down a bit to ~9.5GB. I did a couple of round trips through PS without a problem but then I did an "Open as Smart Object in PS". After that, problems started showing up again and VRAM usage was up to ~10.7GB.
So it may be an issue between using the Camera Raw code via the DM in LR and then opening the same image as a smart object in PS. I do this quite often.
I'll reboot again and see if the problem appears if I don't open as a SO in PS.
I know it's hard to prove when something isn't going to happen but it seems like I can do a lot if I stay in LR and the only anomaly I see is if dehaze is non-zero, some of the other sliders such as WB temp or tint are very laggy (wasn't this an old problem that got fixed?). I also seem to be able to go in and out of PS as long as I used a rasterized object, not a smart object. After making the round trip as a SO, i can work a little bit but other problems always start to show up, especially zooming in and out. It will eventually stop working and all I get is a gray screen when I try to zoom in. I'll keep experimenting tomorrow and see if I notice any other patterns.
Ok, thanks Walt for the additional info. We'll look into it further on our end (using the key step of further editing as a smart object in Ps to repro).
1. For clarity, you mentioned the Nvidia Creator driver, now at https://www.nvidia.com/Download/index... I see the option for Studio Driver (SD) or Game Ready Driver (GRD) not Creator. Studio driver is described as being for creatives. Perhaps another link. Studio shows up as v431.70, Game Ready as v436.15.. Note that the Studio driver is almost a month older. Apparently a name change by Nvidia, Creator changed to Studio?
Sorry, yes, the driver I have installed is the Nvidia Studio Driver version 431.70. On their web site they call it the Studio Driver for Creative Applications and I picked up the creator part. I thought Nvidia promoted the Game Ready driver as being more leading edge but the Studio Driver was more stable and tested with the major creative apps. That's why I installed the Studio Driver. If you think the Game Ready driver is better and well-tested, I can easily switch to that one.
Just noticing the difference in release dates. However, when you look at the release notes for the latest Game Ready One, nothing is mentioned on fixing LRC issues.
Given what I've found so far, I think I'll stay with the current Studio Driver to reduce the variables. It seems like there is something between LR & PS when I use smart objects. That seems to be the constant at least so far. I have a lot of work to do in LR today so I'm going to see if it's stable if I don't take an image into PS as a smart object.
The pano images were both from the DM and the artifact appeared after barely bumping the WB temp slider. The second set were also from the DM after zooming in to 1:2, 1:1 and Fit.
Before doing a clean re-install, I was also getting some weird preview corruption which I fixed a couple of times by rebuilding the preview. However, I was also seeing anomalies where I would start an edit by hitting the "R" key from the Loupe view but the image in the crop preview was the previous image I had been working on. Nothing I tried would fix it until I exited and restarted LR.
Updates to Camera Raw, Lightroom Classic, and the Lightroom Ecosystem were released yesterday evening and contain a fix for this issue. Please install the appropriate update and see if it solves this problem.
21
Replies
AdChoices