Nina Aquila: Legal Eagle, Season One

Nina Aquila: Legal Eagle, Season One

View Stats:
 This topic has been pinned, so it's probably important
Tanuki-sama Studios  [developer] 24 Nov, 2021 @ 10:16am
v5 Bugs & issues go here!
Hi all, if anyone observes any bugs or issues in the v5 version (i.e. any time after *now*) please post them here, and we'll see if we can fix them or provide workarounds.

KNOWN ISSUES & WORKAROUNDS

Savegame flow issue - prompting savegame deletion after chapter completion

We pushed a new build to fix this (the update was ~88kbytes so would've been near-instantaneous for players). This issue may still affect players who have saves which pre-date the update, but please read the notice below as this isn't as bad as it sounds.

Players may find that the game prompts them to wipe their savegames the next time they finish a chapter.

If this happens to you, don't worry! The game won't wipe that you've finished the chapter; it only wipes your interim saves, not your bigger save file which controls your chapter unlocks. You can just carry on to the next chapter without problems. Please just ignore it.

Following the above update, this shouldn't happen to you more than once, so please run through it once and after that, it shouldn't happen a second time.

Apologies for this, also. This is the first time we've updated a live game and although we tested the save validity functionality beforehand, obviously on-release we're finding many cases that we weren't able to account for as so many more people are using it.

Steam Overlay does not show on Linux

Presently the Steam Overlay does not show on Linux, and at the moment there is no workaround for this. We would invite anyone who has experience in this area in broader game development (or specifically nwjs/RPG Maker MV) to get in touch if they have a solution.

Windows is unaffected by this.

Savegame issue for users who have saves from older versions of the game

Some users who owned the game prior to the update are not being asked to delete their old saves.

We've found if those saves are in the courtoom parts of the game, you may have to play for a few moments before the prompt appears; it's meant to happen on-load but it appears the courtroom functionality is rigid, and it's waiting for a "gap" for the prompt. We apologise for this, please just go through the motion once prompted. The best workaround however would be to use the NEW CHAPTER option, which will always prompt you immediately; once you've been through the process, you're good-to-go.

We *may* try and fix this, but it only affects users from prior prior builds and it's reasonably likely that v5 will be the final game-data update for the SEASON ONE release (any remaining changes will be more about compatibility and these hopefully won't require another save-wipe), so we ask that people use the above workaround, as the problem will gradually fix itself as people update.

OLDER ISSUES WE BELIEVE ARE RESOLVED

Linux fullscreen issue

We believe this is now fixed. If you're still having problems, try the workaround below, but please let us know too, as we're still trying to fully understand the scope of the issue.

Some Linux desktop users have found the game does not correctly run in fullscreen for them, though our testing has found that this varies depending on OS/hardware factors. If you're having this problem, check the "package.JSON" file in the game's folder; inside there's a line saying

"fullscreen": false,

please change this to

"fullscreen": true,

For now this is the workaround; we'll look into providing a proper fix in the future once we've had more people on varied hardware play the game and we can devise a more universal solution.
Last edited by Tanuki-sama Studios; 29 Nov, 2021 @ 7:28am
< >
Showing 1-15 of 22 comments
popsUlfr 24 Nov, 2021 @ 12:22pm 
Thanks for the Linux version!
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
... "width": 2560, "height": 1440, ...

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.
Last edited by popsUlfr; 24 Nov, 2021 @ 12:49pm
Tanuki-sama Studios  [developer] 24 Nov, 2021 @ 12:58pm 
Interesting. Yeah; the game uses its own fullscreen functionality which is a step deeper than in the package.json; this has to do with how Steam Deck, Windows & most Linux distros handle fullscreen. There's no single set of values in the package.json which work equally well on all three platforms (using the fullscreen option on Windows causes the game to not boot properly).

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.
popsUlfr 24 Nov, 2021 @ 1:07pm 
Originally posted by tanukisamastudios:
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.
CuriousTommy 24 Nov, 2021 @ 8:44pm 
Originally posted by popsUlfr:
Thanks for the Linux version!
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
... "width": 2560, "height": 1440, ...

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.

Thank you! I ran into the same issue as well. Setting it to fullscreen seems to fixed the issue for me.


Originally posted by tanukisamastudios:
Interesting. Yeah; the game uses its own fullscreen functionality which is a step deeper than in the package.json; this has to do with how Steam Deck, Windows & most Linux distros handle fullscreen. There's no single set of values in the package.json which work equally well on all three platforms (using the fullscreen option on Windows causes the game to not boot properly).

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.

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)
Tanuki-sama Studios  [developer] 24 Nov, 2021 @ 11:28pm 
Thanks @CuriousTommy, and it's good to know that the workaround proposed by @popsUlfr works for others.

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.
Whyte 25 Nov, 2021 @ 10:21am 
Also had this issue, and wanted to contribute with some screenshots in case it helps:
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.
Last edited by Whyte; 25 Nov, 2021 @ 10:23am
Tanuki-sama Studios  [developer] 25 Nov, 2021 @ 10:41am 
Originally posted by Whyte:
Also had this issue, and wanted to contribute with some screenshots in case it helps:
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.
Hi there,

Would it be possible for you try the workaround above, and see if that works for you?
Whyte 25 Nov, 2021 @ 10:55am 
Originally posted by tanukisamastudios:
Would it be possible for you try the workaround above, and see if that works for you?
Oh, yes, it works, with the workaround it shows up full-screen and looks perfect. But then F4 no longer works, and I prefer windowed.

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.
Tanuki-sama Studios  [developer] 25 Nov, 2021 @ 11:00am 
Originally posted by Whyte:
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.
popsUlfr 25 Nov, 2021 @ 3:33pm 
Noticed that the Steam overlay is not working in the linux version. Noticed it when I wanted to take screenshots.
Tanuki-sama Studios  [developer] 25 Nov, 2021 @ 11:23pm 
Originally posted by popsUlfr:
Noticed that the Steam overlay is not working in the linux version. Noticed it when I wanted to take screenshots.
Hmm, that's a shame. This *was* something which was inconsistent across our Linux testers during pre-launch, but we weren't able to figure out why.

Have you tried your printscreen key? I *think* the game should still spit out screenshots to a subfolder when you do this.
Last edited by Tanuki-sama Studios; 25 Nov, 2021 @ 11:24pm
popsUlfr 26 Nov, 2021 @ 2:45am 
Originally posted by tanukisamastudios:
Hmm, that's a shame. This *was* something which was inconsistent across our Linux testers during pre-launch, but we weren't able to figure out why.

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:

./LegalEagle_Windows/nw # %command%

(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

mangohud ./LegalEagle_Windows/nw # %command%

EDIT2:
The following is cleaner as launch options in my opinion (otherwise it completely bypasses the steam reaper process)

bash -c 'exec "${@/--in-process-gpu/}"' _ %command%

EDIT3:

Adding --single-process (without removing --in-process-gpu) fixes the fullscreen issue too but does not get the steam overlay working.

bash -c 'exec "${@/--in-process-gpu/--in-process-gpu --single-process}"' _ %command%
Last edited by popsUlfr; 26 Nov, 2021 @ 3:55am
Tanuki-sama Studios  [developer] 26 Nov, 2021 @ 6:47am 
Originally posted by popsUlfr:
Originally posted by tanukisamastudios:
Hmm, that's a shame. This *was* something which was inconsistent across our Linux testers during pre-launch, but we weren't able to figure out why.

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:

./LegalEagle_Windows/nw # %command%

(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

mangohud ./LegalEagle_Windows/nw # %command%

EDIT2:
The following is cleaner as launch options in my opinion (otherwise it completely bypasses the steam reaper process)

bash -c 'exec "${@/--in-process-gpu/}"' _ %command%

EDIT3:

Adding --single-process (without removing --in-process-gpu) fixes the fullscreen issue too but does not get the steam overlay working.

bash -c 'exec "${@/--in-process-gpu/--in-process-gpu --single-process}"' _ %command%

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?
popsUlfr 26 Nov, 2021 @ 7:32am 
Originally posted by tanukisamastudios:
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/

  • --in-process-gpu: Run the GPU process as a thread in the browser process.
  • --single-process: Runs the renderer and plugins in the same process as the browser

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.
Tanuki-sama Studios  [developer] 26 Nov, 2021 @ 10:40am 
Originally posted by popsUlfr:
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?
< >
Showing 1-15 of 22 comments
Per page: 1530 50