Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I've a problem where in fullscreen mode the game just shows only a quarter of the screen in the upper left corner:
https://i.imgur.com/e2f1eID.png
When forcing into windowed mode via display manager it's fine.
When launching through proton fullscreen mode works fine.
OS: Arch Linux
DE: KDE Plasma
GPU: Nvidia 980Ti 495.44
EDIT: Ah ok, editing package.json in the game folder and setting the native resolution fixes this
EDIT2: actually setting fullscreen to true in the package.json without changing the resolution also works. It seems that fullscreen: false aka windowed mode is broken.
The settings we've gone with seemed to work on Steam Deck, Windows and the Linux flavours we've tested, though naturally Linux exist in wondrous variety so I'm keen to start building up some kind of list of known problematic cases.
If you've got a workaround that works for you, then that's great! I'm surprised the resolution thing fixes it; you *might* run into issues in-game with things not scaling correctly - the game has to be 720p, though obviously the viewport can stretch to any size.
Yeah, I thought as much that touching the resolution could create some issues down the line. But setting fullscreen to true should be alright I guess ?
For what it's worth CrossCode which is another nw.js game does not exhibit this broken fullscreen thing.
Thank you! I ran into the same issue as well. Setting it to fullscreen seems to fixed the issue for me.
Maybe it is a resolution issue... when I lower the resolution on the monitor (to around 720p), I was able to see the game (although there was a white bar on the bottom).
I was running the game on the following:
Distro: Fedora 35
Desktop Environment: Gnome
Graphics: GTX 1060 (4.6.0 NVIDIA 495.44)
We'll keep making note of these sorts of issues and will try to push out a fix once we have more examples and can find a universal solution.
https://i.imgur.com/5ujJtAc.png - fullscreen (it starts like this)
https://i.imgur.com/kP0qvLX.jpg - pressed F4 (it went to windowed mode and looked perfect), then made it a bit larger and started looking like this
https://i.imgur.com/6BfqJKq.png - no clue if it helps but I pressed F3 and made the window a bit smaller
I'm on KDE, X.org, Kubuntu LTS.
Not a game-breaker, I actually prefer windowed mode.
Would it be possible for you try the workaround above, and see if that works for you?
For what it's worth I also tried it on my Surface Go tablet, with Gnome, Fedora, on both X.org and Wayland. On there it worked perfectly in all cases: fullscreen, windowed, resized windowed, etc. I couldn't reproduce the bug at all.
And on a side note, touch input on the tablet was a bit awkward; it worked, but couldn't figure out how to escape from menus.
That's great news! And you should be able to exit with a two-finger-tap. That being said, we don't *technically* support touch input; the game is using a form of mouse emulation so if it works, great, but we don't list it among our features for that reason.
Have you tried your printscreen key? I *think* the game should still spit out screenshots to a subfolder when you do this.
Yeah, I noticed the subfolder LegalEagle_Windows/Screenshots. I can also take screenshots with the DE integrated screen capture. The thing is if one wants to upload screenshots through steam and link them with the game, it needs to go through the steam overlay.
About the fullscreen problem, I noticed that the nw binary is invoked with the --in-process-gpu flag.
So I tried bypassing that by putting in the launch options of the game:
(basically steam offers a macro in the form of %command% that is replaced with the command set by the dev to start the game but here it's commented out using the # so as to not invoke it and instead use my own way)
This invokes nw without any command line flags and I don't have the fullscreen quarter cutout problem anymore, it all works as intended :)
So, basically the --in-process-gpu flag seems to be creating the issue.
EDIT1:
I'm trying to research a bit why steam's overlay doesn't want to work.
Mango HUD manages to overlay its counters and graphs:
https://i.imgur.com/vUDoahT.png
EDIT2:
The following is cleaner as launch options in my opinion (otherwise it completely bypasses the steam reaper process)
EDIT3:
Adding --single-process (without removing --in-process-gpu) fixes the fullscreen issue too but does not get the steam overlay working.
Thanks for all this! All of this makes sense. The way Steam handles command-switches is a bit esoteric though.
Based on what you've said above...
https://imgur.com/LYDZhLg
... what do you recommend we put in the "arguments" box?
Alright so for the arguments it seems that removing --in-process-gpu altogether OR appending --single-process fixes the issue.
Checking the command line switches on this page : https://peter.sh/experiments/chromium-command-line-switches/
It's not completely clear what cancels out what or what the best course of action is, or what using --in-process-gpu was for ?
All I can confirm so far is that removing --in-process-gpu or adding --single-process fixes the fullscreen issue.
My understanding is that --in-process-gpu is necessary for the overlay to work on Windows.
I assumed it would be the same, so I just kept it.
So in that case, we need to pick which of those two command switches is best? I guess?