Hypnospace Outlaw

Hypnospace Outlaw

View Stats:
lil'thang Aug 27, 2020 @ 10:51pm
No more true fullscreen / Display scaling issues since Plus update
Pretty much all of the issues stated here, but not for Linux/MacOS: https://steamcommunity.com/app/844590/discussions/0/1835685838087054532/

I am running Windows 7 and ran into absolutely no display scaling issues prior to the Plus update. Now however, it seems the game no longer has a true fullscreen option, and this is causing scaling issues for me.

Here is a screenshot of the game in fullscreen mode[i.imgur.com]. Here is what it looks like immediately after unchecking the display scaling option, whoooo-weeee![i.imgur.com]

Note that there is a bar at the top of the window, as if the program is still windowed. This is after having pressed alt+enter (or alternatively using the fullscreen button within the ingame settings once a save game has been loaded). Having the bar at the top pushes the display scaling down a little (as you can see from the small bars on the left and right sides as well) and makes all text really awkward and hard to read[i.imgur.com].

Any advice on how to get true fullscreen functionality back? (other than 'lOl jUsT UpGrAdE tO WiNdOwS 10")
Or maybe the "force source"/"force scale" advanced options? I fiddled around with those and they both just seemed to make the screen different kinds of illegible.


EDIT: Oh and also... Steam no longer recognizes that the game has closed. Once I exit out of the game, and HypnOS.exe is nowhere to be found in task manager, Steam still thinks its running, and I click the 'stop' button in steam but it does nothing . It appears to still increment my Steam hours played counter. I have to exit out of Steam for it to recognize that Hypnospace is no longer running.
Last edited by lil'thang; Aug 27, 2020 @ 10:56pm
Originally posted by TetroniMike:
I have another temporary, possible fix for you. Please follow steps 1-4, and at the top of package.json change
"frame": true,
to
"frame": false,

Screenshot: https://1drv.ms/u/s!AnfGCnwpFF_Yg6wONDVRSuOUXBCglw?e=Iwli6w
< >
Showing 1-15 of 18 comments
TetroniMike  [developer] Aug 28, 2020 @ 10:44am 
That's really odd!!! I have a feeling it has something to do either with the engine driving our executable (NWJS) or the settings we use to make it display properly. If you're up for an adventure, I've actually prepared a few different beta test tracks with different versions of NWJS, and have a couple other ideas you can try.

1) Right-click Hypnospace in Steam and go to Properties
2) Local Files tab
3) Verify integrity of game files
4) Wait for it to complete, then try again

If that doesn't work, try uninstalling the game completely (your save files will be fine!) and installing it again.

If that doesn't work, you can access the beta tracks by doing the following:

1) Right-click Hypnospace in Steam and go to Properties
2) Betas tab
3) Enter the following passwords, clicking Check Code each time:
hypnospacetest45
hypnospacetest46
hypnospacetest47
4) Choose testing45 in the "select the beta..." drop-down menu
5) Wait for it to install and try again

Repeat 4-5 for testing46 and testing47. My tests show that 46 and 47 are not awesome when it comes to performance, but who knows maybe you'll have a different experience!

If none of the above works for you, let me know and I will be back with some more advanced ideas involving changing some Chrome Args in our executable files.
I'm in the same boat, except Steam does recognize when it's closed.

-Windows 7
-Played through to completion before Plus update with no issues
-Text after reinstalling is tiny and garbled and weird and I can't read anything

The game starts in a super small window that becomes fullscreen, but it doesn't use all the available space. I used a Youtube video as a guide for what button to press to get into the BIOS options and used the screenshot in this thread to check the display scaling options and things are readable again. I tried hynospacetesting45 and 46 but neither changed anything in terms of text readability.
Last edited by keelsheatingthignsup; Aug 28, 2020 @ 2:29pm
TetroniMike  [developer] Aug 28, 2020 @ 3:18pm 
Alright Windows 7 folks, I have something for you all to try, but it will take some semi-advanced techniques to perform. First, please disable all beta tracks, then do the following:

1) Go into the Hypnospace game files: from Steam, Right-Click Hypnospace -> Manage -> Browse Local Files
2) Rename "package.nw" to "package.zip"
3) Open package.zip
4) Open the "package.json" file inside the zip, in Notepad
5) There is a list of Chromium Args at the bottom. For each one of the args at the end of these instructions:
5a) Delete the arg
5b) Make sure there is only one space between the args before and after the one you deleted
5c) Save package.json back to the zip file
5d) Continue steps 6-9
6) Close out of package.zip
7) Rename "package.zip" to "package.nw"
8) Launch Hypnospace
9) If it doesn't work, please add the arg back to the list where it was originally, and try deleting another arg.

LIST OF ARGS TO TRY STEPS 5a-5d:
--disable-windows10-custom-titlebar --in-process-gpu --disable-direct-composition --force-device-scale-factor=1

(Note that some of these may affect Steam Overlay or have other unintended consequences)

BACKUP LIST OF ALL ARGS IN ORDER:
--disable-windows10-custom-titlebar --disable-plugins --disable-internal-flash --disable-popup-blocking --enable-gamepad --enable-html5-camera --allow-file-access-from-files --ignore-gpu-blacklist --limit-fps=60 --disable-devtools --in-process-gpu --disable-direct-composition --force-device-scale-factor=1

I tried deleting each of those one at a time while restoring the others and minding spaces, and the end result looked the same each time. I took screenshots of the BIOS for each arg removed, and they're all identical. It looks moderately better than the "better" looking one in the OP, (the "NOTE: For the sake of..." in the bottom middle looks more readable for me) but the HYNPOS in the upper right is cut off the exact same way, and going to the main menu and trying to start a new game has similarly cutoff letters.
TetroniMike  [developer] Aug 28, 2020 @ 4:29pm 
Shoot. I'm going to do my best to find an answer to this, but in the meantime does the game run as intended when windowed or maximized (NOT fullscreen) with Non-Integer Scaling turned OFF?
Last edited by TetroniMike; Aug 28, 2020 @ 4:32pm
The author of this thread has indicated that this post answers the original topic.
TetroniMike  [developer] Aug 28, 2020 @ 4:56pm 
I have another temporary, possible fix for you. Please follow steps 1-4, and at the top of package.json change
"frame": true,
to
"frame": false,

Screenshot: https://1drv.ms/u/s!AnfGCnwpFF_Yg6wONDVRSuOUXBCglw?e=Iwli6w
lil'thang Aug 28, 2020 @ 5:09pm 
Thankyou so much for the prompt technical suggestions TetroniMike, I will try all of these when I am back home tonight and report my results. <3
Looks like that did it! I verified the integrity of the game file to restore all the args back to normal, then made the change of frame to false, and it looks great now with and without scaling enabled (the text looked identical with this change regardless of whether non-integer scaling was toggled). When windowed, it's really tiny but the text isn't garbled, and when fullscreen, all the text is completely readable and nothing is cut off or weird looking. Let me know if there are any screenshots you want me to take/settings you want me to try to verify things.
Last edited by keelsheatingthignsup; Aug 28, 2020 @ 5:46pm
TetroniMike  [developer] Aug 28, 2020 @ 6:10pm 
Wonderful!!! And yes screenshots of everything would be great :) Windowed, maximized, fullscreen, integer, and non-integer
https://imgur.com/a/jnBoz9N

I'm actually not sure how to "maximize" as with this mode there's no HypnoOS option to fullscreen, minimize, maximize, etc. I toggle between fullscreen and windowed using F11
lil'thang Aug 28, 2020 @ 11:54pm 
PERFECT! That last fix did it for me. I thought I'd try with that one first, seeing as it worked for keelsheatingthignsup, then work through the other solutions if it didn't. I can 100% confirm changing "frame":true to "frame":false has fixed this issue for me.

Integer scaling and non integer scaling look to be identical as per the other users experience. Only slightly fiddly thing there is that when you uncheck the box, the window becomes tiny and unreadable, but pressing alt+enter to fullscreen again fixes this.


Also including this just for a laugh[i.imgur.com]. At first when I renamed the package.nw to a .zip and tried to update the json inside through windows explorer, saving the json was only updating the file in an extracted copy in temporary files. So I figured, OK, I'll extract the zip to a folder, update the file, then repackage the zip with 7zip, then rename that to .nw and we'll be all hunky dory. Well yeah, that wasn't the case lol, not all zips are created equal!!

The "Steam still thinking Hypnospace is running after it has closed" problem persists, but is the most minor inconvenience possible so I don't really mind. At least I can read stuff now! Thanks so much TetroniMike! ଘ(੭*ˊᵕˋ)੭* ̀ˋ ❤❤

Edit:

Here is a video capture[drive.google.com] of me flicking through the windowed options with "frame":false, and demonstrating the Steam still thinking the program is running thing.
Last edited by lil'thang; Aug 29, 2020 @ 12:15am
TetroniMike  [developer] Aug 29, 2020 @ 2:32pm 
Really glad this works for you two! I'll see if there's a way to programmatically toggle that setting upon going fullscreen/windowed. Thanks :)
TetroniMike  [developer] Sep 4, 2020 @ 9:53am 
Hey Win 7 folks, would you be so kind as to try the following:

0) Undo what we did before and change "frame":false to "frame":true
1) Launch the game
2) Wait until the text based boot-up sequence after the logos
3) Hold B to enter the BIOS, enable the console (top-left)
4) Click EXIT
5) During the text boot-up, hold D+E and press B to enter Debug mode. Then let go of all three keys.
4) Wait for the main menu screen
5) Load up a save file
6) Wait until your desktop is visible after the splash screen
7) Hold D+E and press B (again) to enter ACTIVE Debug mode (you should see some text on the top-left)
8) Press the tilde ~, backtick `, or the § key to enable the console (depending on your keyboard)
9) Try the following commands, one at a time. Copy it below, paste it in the console with Ctrl+V, and press Enter/Return.
10) When trying the "toggle" commands, run the command again to exit that mode

(I recommend not experimenting with "execjs" commands outside of this test as you can break your save file and possibly other things)

execjs:nw.Window.get().toggleFullscreen()
execjs:nw.Window.get().toggleKioskMode()

If either of the two commands work, I'll see about adding an option to BIOS for enabling this new fullscreen mode.
Last edited by TetroniMike; Sep 4, 2020 @ 10:07am
lil'thang Sep 6, 2020 @ 3:27pm 
Hey TetroniMike, sorry for not seeing this sooner.

I have just tested the above:

reverted "frame":false back to true in package.nw/package.json
enabled console in HypnOS bios
click 'exit' in bios, restart in debug mode (debug mode enabled text at bottom of bios screen)
load up saved game
toggle console with '~'
pasted "execjs:nw.Window.get().toggleFullscreen()" (without quotations)
-- nothing happened --
pasted "execjs:nw.Window.get().toggleFullscreen()" (without quotations) again to 'toggle off'
pasted "execjs:nw.Window.get().toggleKioskMode()" (without quotations)
-- nothing happened --
pasted "execjs:nw.Window.get().toggleKioskMode()" (without quotations) again to 'toggle off'

I tried another time with all of the above steps but starting with toggleKioskMode() instead of toggleFullscreen(), but the same result, no dice unfortunately.

i've reverted back to package.nw/package.json "frame":false
TetroniMike  [developer] Sep 7, 2020 @ 7:06pm 
Did you hit D+E+B the second time at the HypnOS desktop? You should see "debug enabled" or similar at the top-left when you do.
< >
Showing 1-15 of 18 comments
Per page: 1530 50

Date Posted: Aug 27, 2020 @ 10:51pm
Posts: 18