starred/Electron.NET
1
0
Fork 0
mirror of https://github.com/ElectronNET/Electron.NET.git synced 2026-02-05 21:24:33 +00:00
Code Issues 668 Packages Projects Releases 20 Wiki Activity

Electron.App.CommandLine.AppendSwitch does not seem to be working propertly #932

New Issue
Closed
opened 2026-01-29 16:52:14 +00:00 by claunia · 5 comments
claunia commented 2026-01-29 16:52:14 +00:00
Owner
Copy Link

Originally created by @Yuvix25 on GitHub (Feb 2, 2024).

  • 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:

Electron.App.CommandLine.AppendSwitch("disable-gpu-compositing");
Electron.App.CommandLine.AppendSwitch("disable-gpu");
Electron.App.CommandLine.AppendSwitch("disable-software-rasterizer");

However, when loading the chrome://gpu page to see that these arguments were applied, it appeared that wasn't the case:
image
I then tried manually adding the flags (electronize start /args --disable-gpu-compositing --disable-gpu --disable-software-rasterizer), which gave me this result:
image

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:

diff --git a/src/ElectronNET.Host/main.js b/src/ElectronNET.Host/main.js
index 0e4079c..179e0d9 100644
--- a/src/ElectronNET.Host/main.js
+++ b/src/ElectronNET.Host/main.js
@@ -26,6 +26,11 @@ if (app.commandLine.hasSwitch('watch')) {
   watchable = true;
 }

+app.commandLine.appendSwitch('enable-transparent-visuals');
+app.commandLine.appendSwitch('disable-gpu');
+app.commandLine.appendSwitch('disable-gpu-compositing');
+app.commandLine.appendSwitch('disable-software-rasterizer');
+
 let currentBinPath = path.join(__dirname.replace('app.asar', ''), 'bin');
 let manifestJsonFilePath = path.join(currentBinPath, manifestJsonFileName);
Originally created by @Yuvix25 on GitHub (Feb 2, 2024). * **Version**: Electron.NET API 23.6.1, Electron.NET CLI 23.6.1.0 * .NET Core Version 6.0 * Node.js v18.12.1 <!-- What target are you building for? --> * **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](https://github.com/electron/electron/issues/40515), so I tried adding the following flags: ```c# Electron.App.CommandLine.AppendSwitch("disable-gpu-compositing"); Electron.App.CommandLine.AppendSwitch("disable-gpu"); Electron.App.CommandLine.AppendSwitch("disable-software-rasterizer"); ``` However, when loading the `chrome://gpu` page to see that these arguments were applied, it appeared that wasn't the case: ![image](https://github.com/ElectronNET/Electron.NET/assets/58216719/c8828758-1e34-4881-9912-602b4853bf31) I then tried manually adding the flags (`electronize start /args --disable-gpu-compositing --disable-gpu --disable-software-rasterizer`), which gave me this result: ![image](https://github.com/ElectronNET/Electron.NET/assets/58216719/5c3c95f6-6e80-4285-b956-c3cbd57e49b2) 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](https://github.com/Yuvix25/ReHUD/blob/97ea359951529fc9177ac3648eeb9237caeb0867/Startup.cs#L95) (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 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: ```js diff --git a/src/ElectronNET.Host/main.js b/src/ElectronNET.Host/main.js index 0e4079c..179e0d9 100644 --- a/src/ElectronNET.Host/main.js +++ b/src/ElectronNET.Host/main.js @@ -26,6 +26,11 @@ if (app.commandLine.hasSwitch('watch')) { watchable = true; } +app.commandLine.appendSwitch('enable-transparent-visuals'); +app.commandLine.appendSwitch('disable-gpu'); +app.commandLine.appendSwitch('disable-gpu-compositing'); +app.commandLine.appendSwitch('disable-software-rasterizer'); + let currentBinPath = path.join(__dirname.replace('app.asar', ''), 'bin'); let manifestJsonFilePath = path.join(currentBinPath, manifestJsonFileName); ```
claunia added the bug label 2026-01-29 16:52:14 +00:00
claunia commented 2026-01-29 16:52:15 +00:00
Author
Owner
Copy Link

@ezorzin commented on GitHub (Apr 12, 2024):

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.

Thanks

@ezorzin commented on GitHub (Apr 12, 2024): Hi, I have [a similar problem](https://github.com/electron/electron/issues/41763). 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. Thanks
claunia commented 2026-01-29 16:52:15 +00:00
Author
Owner
Copy Link

@FlorianRappl commented on GitHub (Apr 12, 2024):

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 commented on GitHub (Apr 12, 2024): 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).
claunia commented 2026-01-29 16:52:15 +00:00
Author
Owner
Copy Link

@SemanticStudios commented on GitHub (Apr 16, 2024):

@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..

@SemanticStudios commented on GitHub (Apr 16, 2024): @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..
claunia commented 2026-01-29 16:52:15 +00:00
Author
Owner
Copy Link

@FlorianRappl commented on GitHub (Apr 17, 2024):

@SemanticStudios PRs are always welcome - I can have a look quite fast and if reasonable we can surely make a release.

@FlorianRappl commented on GitHub (Apr 17, 2024): @SemanticStudios PRs are always welcome - I can have a look quite fast and if reasonable we can surely make a release.
claunia commented 2026-01-29 16:52:15 +00:00
Author
Owner
Copy Link

@FlorianRappl commented on GitHub (Oct 31, 2025):

Outdated - use ElectronNET.Core and ElectronNET.Core.AspNet.

See Wiki / What's New.

@FlorianRappl commented on GitHub (Oct 31, 2025): Outdated - use `ElectronNET.Core` and `ElectronNET.Core.AspNet`. See [Wiki / What's New](https://github.com/ElectronNET/Electron.NET/wiki/What's-New).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
api
applications
bug
bug
dev-experience
discussion
documentation
duplicate
enhancement
examples
Feature
Feature
good first issue
help wanted
In progress
information
infrastructure
invalid
javascript
macos
more-information-needed
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#932
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?