View Issue Details

IDProjectCategoryLast Update
0019348Starward RogueCrash/ExceptionJul 2, 2018 9:22 am
ReporterInhibit Assigned ToChris_McElligottPark  
Severitymajor 
Status resolvedResolutionfixed 
Product Version1.750 
Fixed in Version2.001 (Die A Fiery Death, Audio Crash) 
Summary0019348: Won't Start on Second Start-Up After Update
DescriptionAfter updating to 1.750 on Steam (Linux system) Starward Rogue fails to start. Once the Unity "~/.config/unity3d/Arcen Games, LLC/Starward Rogue" file is removed, startup works normally, once. Also, if you change the variable:

<pref name="Screenmanager Is Fullscreen mode" type="int">1</pref>

to

<pref name="Screenmanager Is Fullscreen mode" type="int">0</pref>

it appears to fix the issue.
TagsNo tags attached.

Relationships

related to 0019674 assignedChris_McElligottPark Freeze on Startup / Blank Screen on Startup 

Activities

Chris_McElligottPark

Jan 25, 2018 11:34 am

administrator   ~0046712

Hmm -- is 2.000 not available for you now?

Inhibit

Jan 25, 2018 11:48 am

reporter   ~0046714

Hold on.. it might be 2.000. I wrote that when it wasn't starting as I was punching through a few options to see if I could make it work.

Apologies, it is "Starward Rogue 2.000 Steamworks Enabled!"

Also, I just noticed that it changed my option for fullscreen back to "1" after playing and quitting a game.

Chris_McElligottPark

Jan 25, 2018 1:12 pm

administrator   ~0046715

Hmm, that's surprising that it changed it back, too. Is it still running okay after it changes it back, or dead again?

Chris_McElligottPark

Jan 25, 2018 1:14 pm

administrator   ~0046716

Oh, and I just realized that's not our own internal settings -- that's some something belonging to unity, grr. Our own settings should be overriding that, OR if you go into settings.dat in the RuntimeData folder of the game, OR if you go into the game settings themselves, then setting it to be non-fullscreen should override their thing.

Unity might say "go fullscreen" still, but then ours kicks in right after that. Knock on wood. ;)

Inhibit

Jan 25, 2018 2:01 pm

reporter   ~0046717

Okay, so if I uncheck "fullscreen" in the in-game settings it will then start reliably after a few tries. It also leaves the pref file set to "0" for that option. That seems to work to lock it out of fullscreen mode and work around the problem once I've manually set it once in the pref file.

If "fullscreen" is checked in the in-game settings it fails to start and I'm stranded on the screen "Game Version 2.000 GUI INIT..." (although steam's overlay is working).

Inhibit

Jan 25, 2018 2:02 pm

reporter   ~0046718

Or rather, read that as "if I uncheck "fullscreen" in the in-game settings it will then start reliably; I have tried it a few times in a row"

Chris_McElligottPark

Jan 25, 2018 2:54 pm

administrator   ~0046719

Last edited: Jan 25, 2018 2:54 pm

Okay, that's good to know. I wonder if there's a driver issue on your particular machine regarding the fullscreen mode -- I'll keep an eye on this, but I'm not sure I want to default everyone into windowed mode just yet.

edit: Thanks, by the way!

Inhibit

Jan 25, 2018 4:09 pm

reporter   ~0046721

Absolutely. For the record it's a Debian 9 (probably updated through 6,7, and 8) release running a 1920x1080 display on an Intel i3 integrated graphics controller. The OpenGL driver is listed as Intel Open Source Technology Center. Darned if I can find the Xorg driver name at a glance; although that's been changing since I did any casual development work involving Xorg (or whatever it's become) proper.

Also, there's *probably* a secondary graphics output that's unused and that I disabled in some way (a ways back) while not in use. This unit has a projector built in that acts like a second display.

If it proves to be a wider issue I'll troubleshoot on a greater array of systems to see if the problem re-occurs on particular hardware. Otherwise I'll ignore it. Thanks for the follow up!

Chris_McElligottPark

Jan 25, 2018 5:31 pm

administrator   ~0046722

Thank you! That's fabulous debugging info. :)

abram

Jul 2, 2018 12:50 am

reporter   ~0047671

This still exists in 2.002. I cannot star Starward Rogue twice in a row on Ubuntu 18.04 with SW 2.002 x86_64.

I can reliably start it up by doing the following

SW$ cat start.sh
#!/bin/bash
sed -i 's#<pref name="Screenmanager Is Fullscreen mode" type="int">1</pref>#<pref name="Screenmanager Is Fullscreen mode" type="int">0</pref>#' \
    ~/'.config/unity3d/Arcen Games, LLC/Starward Rogue/prefs'
./StarwardRogueLinux.x86_64

SW$ bash start.sh

If I don't do that I get 1 of 2 behaviours.

1. Black screen with mouse cursor that disappears
2. Maybe just maybe a picture of the base and the star that flickers black and doesn't load.

But if I set this value at startup consistently I can run the game consistently. That said (ha) I am using sed on XML which doesn't feel right.

Issue History

Date Modified Username Field Change
Jan 25, 2018 11:10 am Inhibit New Issue
Jan 25, 2018 11:34 am Chris_McElligottPark Note Added: 0046712
Jan 25, 2018 11:34 am Chris_McElligottPark Assigned To => Chris_McElligottPark
Jan 25, 2018 11:34 am Chris_McElligottPark Status new => feedback
Jan 25, 2018 11:48 am Inhibit Note Added: 0046714
Jan 25, 2018 11:48 am Inhibit Status feedback => assigned
Jan 25, 2018 1:12 pm Chris_McElligottPark Note Added: 0046715
Jan 25, 2018 1:14 pm Chris_McElligottPark Note Added: 0046716
Jan 25, 2018 2:01 pm Inhibit Note Added: 0046717
Jan 25, 2018 2:02 pm Inhibit Note Added: 0046718
Jan 25, 2018 2:54 pm Chris_McElligottPark Note Added: 0046719
Jan 25, 2018 2:54 pm Chris_McElligottPark Note Edited: 0046719
Jan 25, 2018 4:09 pm Inhibit Note Added: 0046721
Jan 25, 2018 5:31 pm Chris_McElligottPark Note Added: 0046722
Feb 5, 2018 10:03 am Chris_McElligottPark Status assigned => resolved
Feb 5, 2018 10:03 am Chris_McElligottPark Resolution open => fixed
Feb 5, 2018 10:03 am Chris_McElligottPark Fixed in Version => 2.001 (Die A Fiery Death, Audio Crash)
Jul 2, 2018 12:50 am abram Note Added: 0047671
Jul 2, 2018 9:22 am Chris_McElligottPark Relationship added related to 0019674