mzboray wrote:Thanks for your help on this.
I tried those flags, but the result was the same. I've noticed from the stack trace and some console logging that the error occurs before the call to the Cef.Initialize where the command line args are passed into CEF, so they probably aren't even having a chance to take effect. Here is the error with stack trace:Exception:System.IO.FileNotFoundException: Could not load file or assembly 'CefSharp.Core.dll' or one of its dependencies. The specified module could not be found.
File name: 'CefSharp.Core.dll'
at CefBasic.Program.Run(String args)
at CefBasic.Program.Main(String[] args) in C:\Users\mzboray\source\repos\CefBasic\CefBasic\Program.cs:line 29
I have some console logging right at the start of Run so I can tell it's not even entering the method. I realize now its failing at the stage where it actually loads CefSharp.Core not just failing when calling into Cef.Initialize(). I think there probably isn't a simple workaround with flags passed down to CEF.
I tried to screenshot chrome's gpu and version settings. The version page doesn't seem to load properly (or maybe its just delayed) and I didn't see much difference in the gpu settings between server core and windows 10, but I can keep at it and see if I can get more info on this.
It's possible that if the dll is delay loaded then some command line flags to avoid the features that require dxva2.dll might be possible (totally untested)
Users browsing this forum: Google [Bot] and 68 guests