You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version: Electron.NET API 23.6.1, Electron.NET CLI 23.6.1.0
.NET Core Version 6.0
Node.js v18.12.1
Target: Windows
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.AppendSwitchs 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 appendSwitchs to the main.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 the Configure method - with no success.
This worked:
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.
I also tried on Discord: same thing.
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
I am having a similar issue (need to run WebGL shader code on VM but lack GPU so I need to set ignore-gpu-blacklist switch).
Would you accept a pull request to try to address this issue? And if so, how long do you think it would take you guys to review and merge? Anything that I could do to make it easier on you?
Asking humbly as I know you guys are busy and supporting open source can be thankless..
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: