[Workaround In Place] Build 1128.1 Persistent Spinning Globe (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support



Message

rmwilsonjr -> [Workaround In Place] Build 1128.1 Persistent Spinning Globe (2/13/2020 1:21:06 AM)

Just loaded Build 1128.1, played one game, tried to reload it (using .scen, not .save) and Spinning Globe screen appeared along with a locked map belonging to the game I tried to reload. Have exited and restarted a number of times. Spinning Globe appears after loading, but no matter what scenario I select, it appears hidden behind the Spinning Globe screen (I thought they weren't even loading until I found them hidden behind the Spinning Globe). Moving the map to a new screen leaves the Spinning Globe still spinning on the home screen. Secondary screens will appear on top of it, but if you focus on it, it fills the screen covering all the secondary screens. I don't see any windows buttons in the upper right to minimize it, or close it. Before the latest build, it just automatically disappeared when the scenario loaded.



Dimitris -> RE: Build 1128.1 Persistent Spinning Globe (2/13/2020 6:48:25 AM)

Have you set the message log to be in detached mode, per chance?



rmwilsonjr -> RE: Build 1128.1 Persistent Spinning Globe (2/13/2020 4:59:34 PM)

Yes I always do.



michaelm75au -> RE: Build 1128.1 Persistent Spinning Globe (2/14/2020 4:49:06 AM)

The problem is that it is expecting a window position for the detached log.

(a) For now I would suggest adding the following line to the config\command.ini file under the [Secondary Window Settings] section
MessageLogWindow = 56|261|691|392

This will give the window a starting location.

(b) The other alternate is to edit command.ini and change the value under the [Game Preferences] section
MessageLogInWindow = False

This will start the game with attached, so when you detach it, the window position will be recorded in INI.

The reason why it is not handling a case of no 'window position -> use default' is being investigated.



Barleyman -> RE: Build 1128.1 Persistent Spinning Globe (2/15/2020 1:28:42 AM)

quote:

ORIGINAL: michaelm75au

The problem is that it is expecting a window position for the detached log.

(a) For now I would suggest adding the following line to the config\command.ini file under the [Secondary Window Settings] section
MessageLogWindow = 56|261|691|392

This will give the window a starting location.


Woo, I can play my game again [&o]



rmwilsonjr -> RE: Build 1128.1 Persistent Spinning Globe (2/15/2020 2:28:34 AM)

Michael, I wish I knew what you said, but the only code I know is Morse. My workaround was just to shrink it to the size of a postage stamp and park it off to a corner of my screen. The Devs, god love ‘em, seemed to have conquered the problem in the latest build.



MaB1708 -> RE: Build 1128.1 Persistent Spinning Globe (2/15/2020 5:28:55 PM)


quote:

ORIGINAL: michaelm75au

The problem is that it is expecting a window position for the detached log.

(a) For now I would suggest adding the following line to the config\command.ini file under the [Secondary Window Settings] section
MessageLogWindow = 56|261|691|392

This will give the window a starting location.

(b) The other alternate is to edit command.ini and change the value under the [Game Preferences] section
MessageLogInWindow = False

This will start the game with attached, so when you detach it, the window position will be recorded in INI.

The reason why it is not handling a case of no 'window position -> use default' is being investigated.


Thank you, Michael, (a) did it for me after some fiddling on my own yesterday evening!
Cheers,
Martin



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.109375