-
-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Electron.App.CommandLine.AppendSwitch does not seem to be working propertly #830
Comments
Hi, I have a similar problem. I cannot run webgpu through electron on Linux apparently because I cannot set the "--enable-unsafe-webgpu" and the "--enable-vulkan" flags. As in my comments of the issue I linked to this discussion, it looks like they are not in the list of flags supported by the app.commandLine.appendSwitch method of electron. Any idea how to fix this? I got no solution from that issue, actually they closed it without a satisfactory answer. Thanks |
Hi @ezorzin I would love to help you on this one, but unfortunately this seems to have to do with Electron directly and not the Electron.NET wrapper (which has a more general problem with the append switch; nothing to do with the WebGPU). |
@FlorianRappl |
@SemanticStudios PRs are always welcome - I can have a look quite fast and if reasonable we can surely make a release. |
I'm building an app which is using a window with transparent background. While I did get it to work (thanks to #748 ), some users are seeing a black background instead of the transparent one. After doing some research, I stumbled upon this, so I tried adding the following flags:
However, when loading the
chrome://gpu
page to see that these arguments were applied, it appeared that wasn't the case:I then tried manually adding the flags (
electronize start /args --disable-gpu-compositing --disable-gpu --disable-software-rasterizer
), which gave me this result:So either I'm adding the
Electron.App.CommandLine.AppendSwitch
s wrong, or they do not work.You can find the full source code of how I'm adding them here (note that you will only find the
disable-gpu-compositing
flag there, I added the rest locally without pushing yet)If there is indeed a bug, is there any way I can get around this to force these arguments to always be passed?
Edit:
When manually adding the
appendSwitch
s to themain.js
file in ElectronNET.Host, they do work. I also made sure that the append switch message sent from Electron.NET is received in Electron.js, so I guess the issue has something to do with the time of appending the switches. I also tried appending them right at the start of theConfigure
method - with no success.This worked:
The text was updated successfully, but these errors were encountered: