Dwaine Maggart wrote:It looks like that laptop should have an adequate GPU for Resolve 14.
Without a Resolve Diagnostics log, it's hard to know what the issue might be.
You might try updating the NVIDIA driver. If 12.5. works and 14 doesn't, that would be a likely suspect.
Under 12.5, transitions are jerky, but I treat that as the wages of using a low-end GPU. Since it's in a laptop, I'm stuck with it (some versions of the machine can be updated; I don't have one). Rendered, everything's fine.
With 14, unless the presence of some version of the driver effectively crashes Resolve before reaching the main screen, I doubt it's the video driver. NTL, I'll give it a try.
Stepping through the sequence of events again:
Resolve 14 launches and shows the expected splash screens and "loading xyz module" messages. Task Manager shows Resolve is a background process (same thing under 12.5).
The project selection page is displayed, with the expected existing projects as well as the unnamed project. Task Manager shows Resolve as a foreground process (ditto under 12.5).
Selecting any project, named or not, removes the project screen, as expected.
Here's the point where 12.5 and 14 diverge.
Under 12.5 the main screen opens and is functional. Task Manager shows Resolve remains a foreground process.
Under 14, the project page is closed but the main screen doesn't show up. Task Manger shows Resolve as a background process, using less and less CPU time, until it goes to 0%. At that point the process closes, goes away, ceases to be. No error messages, no nothing. It's the Cheshire Cat fading away until only grin remains, and that disappears, too.
A footnote: 12.5 will also, with no obvious warning, change to a background process, at which point the main page's functionality degrades in different ways. Task Manager shows Resolve sitting in the list of background processes, using 0% of CPU resources. Unlike 14, the process doesn't spontaneously end. I have to end it and relaunch to get back to work. Relaunching 14 only produces the results described above.
- - - - -
I found the way to get logs without being able to access the Help menu. I'll stress test 12.5 to get the "spontaneously becomes a background process problem" logs and post them on a separate thread.
I'll re-load 14 and try to capture logs from its failure and post them here.
Having stumbled upon the truth, he continued on as if nothing had happened.