[NTE] Launcher and Game goes all black #14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Compatibility Report
System Information
I confirm:
(Did this but file did not generate, sorry)
Symptoms
Opening the launcher using my Nvidia RTX 5070 Ti (Mobile) as main GPU makes the launcher launch either black or white. I can click and hover over buttons (Cursor changes) but unable to see anything.
Same thing happens once you go inside the game and try to log in. All black.
However when launching the game using my AMD iGPU the problem is no longer there and I can browse around menus without much issue.
Reproduction
I have a hunch that this issue could be related to something similar that happened to a ceeertain game, that had a certain issue regarding WebView browser (the ones used by some gacha games to render web conent such as news and login related content, as well as launchers).
Or perhaps I just need to update my drivers (unlikely, I am currently using stable drivers, but I could give it a try).
Does anyone have this same issue? I'm gonna still be able to launch and play but probably anything related to WebView is not going to work or even worse, hinder the play experience.
Just wanted to share this with everyone since I'm probably not going to be the first one with this issue!
Thank you for your support!!
image
Haven’t seen this around yet so let’s keep the issue open for now. Does using Steam help though?
QTWEBENGINE_CHROMIUM_FLAGS="--disable-direct-composition --single-process"you should give this a try, it might get rid of the issue.Thank you for your help, sorry, I have not tried Steam. I am running Lutris!
Tried, but no effect :(
Thank you!
@yozorawolf wrote in #14 (comment):
Do you mind trying to add NTEGlobalLauncher.exe to Steam and running with dwproton from there? That way, it will be much easier to generate a log. You can just use
PROTON_LOG=1 WINEDEBUG="" %command%as launch options and that will generate a steam.log file in your home directory that you can send, so that we can maybe see whats going on.@NelloKudo wrote in #14 (comment):
Here it is!
Incredibly enough running it through Steam with dwproton solved the issue with the WebView instances. (Which would make the screen go black ingame and the launcher completely black).
Still I will leave you my logs. I could be missing something, but at the very least I can confirm that dwproton + Steam works to solve this issue.
As for running it under Lutris? I have no idea I may have to dig deeper or wait for someone to have an answer to this!
Thanks @NelloKudo ! This helps a lot! 👍
@yozorawolf wrote in #14 (comment):
Very nice! The logs do indeed look fine on Steam. I'll leave you the choice to close this if it's solved or whatever, let me know if any other issues occur 🍻
@NelloKudo wrote in #14 (comment):
Thanks again!! For now I'll leave it open in case I find a solution to this issue. Or someone else does.
But for now, anyone that has this issue: you can just use dwproton latest + Steam and it should work ok.
I'm not sure if it's related but I noticed everything worked fine when using Steam + dwproton latest, per this thread. Initially when using other launchers like Faugus the installer just exits after trying to install the launcher. But when I use the prefix that steam created in Faugus (launcher installed and game updated in Steam) everything seems to work fine and I can launch the game without issues, both in Steam and in Faugus. Everything is using defaults and no launch options and commands were used.
System: 5800X3D + RX 7900 XT
OS: Bazzite
@seiren wrote in #14 (comment):
I was tinkering around too, and this might be possible since Steam does ship its own libs and dependencies which are made for these cases. But programs like lutris use their own or system libs which are probably not compatible or have issues with it. I'm still trying to find a solution, but thanks for confirming this, at least there is a workaround.