View Issue Details

Jump to NotesJump to History
IDProjectCategoryDate SubmittedLast Update
0019278AI War 2GUINov 2, 2017 7:58 pmNov 7, 2017 9:33 am
ReporterBadgerBadger Assigned Tokeith.lamothe  
Status resolvedResolutionfixed 
Product Version0.601 
Fixed in Version0.602 
Summary0019278: Quit button no longer works
DescriptionI hit Esc->1->3 and nothing happens. Save And Quit also doesn't work
TagsNo tags attached.

Activities

BadgerBadger

Nov 2, 2017 8:00 pm

manager   ~0046567

This does not affect OSX, only linux.

BadgerBadger

Nov 2, 2017 8:01 pm

manager   ~0046568

Huh, now it's not happening anymore. Weird....

Chris_McElligottPark

Nov 2, 2017 8:01 pm

administrator   ~0046569

Glitch in the matrix...

BadgerBadger

Nov 2, 2017 8:07 pm

manager   ~0046571

Okay. this seems to happen "sometimes". I've definitely managed to recreate it a few times. No obvious pattern so far

BadgerBadger

Nov 4, 2017 1:01 pm

manager   ~0046573

As a demonstration, I updated the Window_InGameEscapeMenu.cs thusly
        public class bExitGame : ButtonAbstractBase
        {
            public override void GetTextToShow( ArcenDoubleCharacterBuffer Buffer )
            {
                base.GetTextToShow( Buffer );
                Buffer.Add( "Quit Game" );
            }
            public override MouseHandlingResult HandleClick()
            {
              ArcenDebugging.ArcenDebugLogSingleLine( "quit requested at " + World_AIW2.Instance.GameSecond + " seconds into game", Verbosity.DoNotShow ); <==== some logging
                Engine_AIW2.Instance.QuitRequested = true;
                return MouseHandlingResult.None;
            }
            public override void HandleMouseover() { }
            public override void OnUpdate() { }
        }

Here's a matching debug log
11/4/2017 12:58:39 PM Successfully opened host socket
11/4/2017 12:58:41 PM quit requested at 0 seconds into game <== this one worked
11/4/2017 12:58:43 PM Shutting Down Socket
11/4/2017 12:58:43 PM PLAYER DISCONNECTED 0.0.0.0=>0
11/4/2017 12:58:43 PM World Created, Launching Server
11/4/2017 12:58:43 PM Successfully opened host socket
11/4/2017 12:58:48 PM quit requested at 3 seconds into game <=== this one worked
11/4/2017 12:58:49 PM Shutting Down Socket
11/4/2017 12:58:49 PM PLAYER DISCONNECTED 0.0.0.0=>0
11/4/2017 12:58:49 PM World Created, Launching Server
11/4/2017 12:58:50 PM Successfully opened host socket
11/4/2017 12:58:57 PM quit requested at 2 seconds into game <== this one worked
11/4/2017 12:58:59 PM Shutting Down Socket
11/4/2017 12:58:59 PM PLAYER DISCONNECTED 0.0.0.0=>0
11/4/2017 12:58:59 PM World Created, Launching Server
11/4/2017 12:58:59 PM Successfully opened host socket
11/4/2017 12:59:11 PM quit requested at 4 seconds into game <=== uh oh, nothing happens this time
11/4/2017 12:59:13 PM quit requested at 5 seconds into game
11/4/2017 12:59:15 PM quit requested at 7 seconds into game
11/4/2017 12:59:16 PM quit requested at 9 seconds into game
11/4/2017 12:59:17 PM quit requested at 9 seconds into game
11/4/2017 12:59:17 PM quit requested at 9 seconds into game
11/4/2017 12:59:17 PM quit requested at 10 seconds into game
11/4/2017 12:59:17 PM quit requested at 10 seconds into game
11/4/2017 12:59:17 PM quit requested at 10 seconds into game
11/4/2017 12:59:18 PM quit requested at 10 seconds into game
11/4/2017 12:59:18 PM quit requested at 10 seconds into game
11/4/2017 12:59:18 PM quit requested at 11 seconds into game
11/4/2017 12:59:18 PM quit requested at 11 seconds into game
11/4/2017 12:59:18 PM quit requested at 11 seconds into game
11/4/2017 12:59:19 PM quit requested at 11 seconds into game
11/4/2017 12:59:19 PM quit requested at 11 seconds into game
11/4/2017 12:59:23 PM quit requested at 16 seconds into game
11/4/2017 12:59:24 PM quit requested at 16 seconds into game
11/4/2017 12:59:24 PM quit requested at 17 seconds into game
11/4/2017 12:59:24 PM quit requested at 17 seconds into game

As you can see, it's sporadic. Once you get into a game you can't quit from then you're just stuck though.

keith.lamothe

Nov 6, 2017 11:38 am

administrator   ~0046578

For 0.602:

* Added warning messages if a long-range-planning thread takes longer than 10 seconds, since some parts of the game cannot proceed until the long-range-planning phase concludes. For example, the "quit game" process needs to wait until the current planning is done to avoid the planning thread crashing into a bunch of null exceptions as the gamestate is dismantled.

It's possible this isn't the cause, but I can't think of another. At least this way if one of the faction threads gets unusually introspective we'll know about it.

BadgerBadger

Nov 7, 2017 9:33 am

manager   ~0046591

This problem still happens

Issue History

Date Modified Username Field Change
Nov 2, 2017 7:58 pm BadgerBadger New Issue
Nov 2, 2017 8:00 pm BadgerBadger Note Added: 0046567
Nov 2, 2017 8:01 pm BadgerBadger Note Added: 0046568
Nov 2, 2017 8:01 pm Chris_McElligottPark Note Added: 0046569
Nov 2, 2017 8:01 pm Chris_McElligottPark Assigned To => keith.lamothe
Nov 2, 2017 8:01 pm Chris_McElligottPark Status new => feedback
Nov 2, 2017 8:07 pm BadgerBadger Note Added: 0046571
Nov 2, 2017 8:07 pm BadgerBadger Status feedback => assigned
Nov 4, 2017 1:01 pm BadgerBadger Note Added: 0046573
Nov 6, 2017 11:38 am keith.lamothe Status assigned => resolved
Nov 6, 2017 11:38 am keith.lamothe Resolution open => fixed
Nov 6, 2017 11:38 am keith.lamothe Fixed in Version => 0.602
Nov 6, 2017 11:38 am keith.lamothe Note Added: 0046578
Nov 7, 2017 9:33 am BadgerBadger Note Added: 0046591