Added debug code

In 1.9 RC 1a, under Wine, I've been having non-immediate, but extremely frequent crashes whenever the "new"/extra segments armour UI is in use, especially when doing things (modifying armour, etc.) that cause it to highlight/redraw. I suspect it's due to some difference between Wine's and Windows' implementations of the drawing functions used. I have had it happen with the Armstrong-class transport playership, with Playership Drones, and with Brokers Expanded, but the debug.log presentation hasn't always been the same from what I remember. I haven't managed to make it manifest without mods/in a registered game yet, I'll try a Corporate Command-only run, but the Manticore's armour UI appears to not use the big circular diagram and does appear stable from my limited testing. Would debug logs and saves from any of the modded crashes be useful, or can you recommend a way to bring up the circular armour display in a registered game? Also, my apologies if I should have started a new issue, I think it's related to this one and don't want to open duplicate issues, but I might be mistaken.

With nothing but the Armstrong-class transport mod (and the base D&O content), the issue can be reproduced by starting a game with the Armstrong, then going into the S menu and examining your armour configuration (S->S->A). However, sometimes this crashes immediately, and sometimes you need to click a few armour segments first; sometimes the game crashes with the error display drawing on screen, and other times it simply hangs, printing the error data only to debug.log.
Sometimes it crashes in the 'painting armour display' state, sometimes 'painting SRS', etc.
Sample crash 1: Crash was delayed (clicked a few armour segments first), and printed its message to the screen.

2021-11-09 01:08:31 --------------------------------------------------------------------------------
2021-11-09 01:08:31 Start logging session
2021-11-09 01:08:32 Direct3D
2021-11-09 01:08:32 Screen: 1920 x 1080
2021-11-09 01:08:32 Scale: 1.00
2021-11-09 01:08:32 Background blt: Enabled
2021-11-09 01:08:32 Use Direct X: Enabled
2021-11-09 01:08:32 Use GPU compositing: Enabled
2021-11-09 01:08:32 LogPixelsY: 96
2021-11-09 01:08:33 DeviceType: 0x1
2021-11-09 01:08:33 Caps: 0x00000000
2021-11-09 01:08:33 Caps2: 0x60020000
2021-11-09 01:08:33 Caps3: 0x00000320
2021-11-09 01:08:33 DevCaps: 0x0019aff0
2021-11-09 01:08:33 DevCaps2: 0x00000051
2021-11-09 01:08:33 [DX] Buffer Format: 22
2021-11-09 01:08:33 Transcendence 1.9 RC 1a
2021-11-09 01:08:33 Graphics quality maximum: 73 ms; 6 cores.
2021-11-09 01:08:38 Loading user collection.
2021-11-09 01:08:39 Loading news.
2021-11-09 01:08:39 All resources downloaded.
2021-11-09 01:09:05 Initializing adventure: Transcendence.tdb
2021-11-09 01:09:09 Created new game
2021-11-09 01:09:10 Starting new game.
2021-11-09 01:09:40 Started game version: 1.9 RC 1a (1.9.301.0)
2021-11-09 01:09:40 Extension: Armstrong Transport Player Ship [1.0]
2021-11-09 01:09:41 Using API version: 44
2021-11-09 01:09:53 Crash in CGDraw::ArcQuadrilateral
2021-11-09 01:09:53 Crash in CArmorHUDRingSegments::DrawItemBox
2021-11-09 01:09:53 Crash in CArmorHUDRingSegments::DrawArmorName
2021-11-09 01:09:53 Crash in CArmorHUDRingSegments::Realize
2021-11-09 01:09:53 Crash in CArmorHUDRingSegments::OnPaint
2021-11-09 01:09:53 Crash in CHeadsUpDisplay::Paint
2021-11-09 01:09:53 CException: Win32 exception.
2021-11-09 01:09:53 Crash in CGameSession::OnAnimate
2021-11-09 01:09:53 Unable to continue due to program error.

program state: OnAnimate
program state: painting armor display
save file: Matz05-7993.sav
system: SE
system type: 00100001
system name: Eridani
total objs: 958
destroyed: 0
deleted: 0
bad: 0
stars: 1
game state: docked

Please contact [email protected] with a copy of Debug.log and your save file. We are sorry for the inconvenience.

Sample crash 2: Crash was delayed (had to click a few armour segments), but did NOT get to print error statement on screen.

2021-11-09 01:13:32 --------------------------------------------------------------------------------
2021-11-09 01:13:32 Start logging session
2021-11-09 01:13:33 Direct3D
2021-11-09 01:13:33 Screen: 1920 x 1080
2021-11-09 01:13:33 Scale: 1.00
2021-11-09 01:13:34 Background blt: Enabled
2021-11-09 01:13:34 Use Direct X: Enabled
2021-11-09 01:13:34 Use GPU compositing: Enabled
2021-11-09 01:13:34 LogPixelsY: 96
2021-11-09 01:13:34 DeviceType: 0x1
2021-11-09 01:13:34 Caps: 0x00000000
2021-11-09 01:13:34 Caps2: 0x60020000
2021-11-09 01:13:34 Caps3: 0x00000320
2021-11-09 01:13:34 DevCaps: 0x0019aff0
2021-11-09 01:13:34 DevCaps2: 0x00000051
2021-11-09 01:13:34 [DX] Buffer Format: 22
2021-11-09 01:13:34 Graphics quality maximum: 49 ms; 6 cores.
2021-11-09 01:13:34 Transcendence 1.9 RC 1a
2021-11-09 01:13:39 Loading user collection.
2021-11-09 01:13:40 Loading news.
2021-11-09 01:13:41 All resources downloaded.
2021-11-09 01:13:44 Initializing adventure: Transcendence.tdb
2021-11-09 01:13:48 Created new game
2021-11-09 01:13:48 Starting new game.
2021-11-09 01:14:04 Started game version: 1.9 RC 1a (1.9.301.0)
2021-11-09 01:14:04 Extension: Armstrong Transport Player Ship [1.0]
2021-11-09 01:14:04 Using API version: 44
2021-11-09 01:14:14 Crash in CDockScreen::ShowPane
2021-11-09 01:14:14 Crash in MainWndProc. Message = 0x201.

Third attempt: Crash was extremely delayed (I was clicking different armour segments for maybe ten seconds before it crashed), no message printed on the screen.
Aside from timestamps and the number of ms in the Graphics quality maximum line, debug.log output was identical to Sample Crash 2, full log not given to save space.

Further duplicates of the first two crashes occurred in repeated tests, until I got a crash immediately upon startup (without having opened the S menu at all)
Sample crash 3 (immediate crash, rather than in armour screen. This crash managed to print its message to the screen.):

2021-11-09 01:29:15 --------------------------------------------------------------------------------
2021-11-09 01:29:15 Start logging session
2021-11-09 01:29:16 Direct3D
2021-11-09 01:29:16 Screen: 1920 x 1080
2021-11-09 01:29:16 Scale: 1.00
2021-11-09 01:29:16 Background blt: Enabled
2021-11-09 01:29:16 Use Direct X: Enabled
2021-11-09 01:29:16 Use GPU compositing: Enabled
2021-11-09 01:29:16 LogPixelsY: 96
2021-11-09 01:29:16 DeviceType: 0x1
2021-11-09 01:29:16 Caps: 0x00000000
2021-11-09 01:29:16 Caps2: 0x60020000
2021-11-09 01:29:16 Caps3: 0x00000320
2021-11-09 01:29:16 DevCaps: 0x0019aff0
2021-11-09 01:29:16 DevCaps2: 0x00000051
2021-11-09 01:29:16 [DX] Buffer Format: 22
2021-11-09 01:29:17 Graphics quality maximum: 41 ms; 6 cores.
2021-11-09 01:29:17 Transcendence 1.9 RC 1a
2021-11-09 01:29:21 Loading user collection.
2021-11-09 01:29:22 Loading news.
2021-11-09 01:29:23 All resources downloaded.
2021-11-09 01:29:27 Initializing adventure: Transcendence.tdb
2021-11-09 01:29:32 Created new game
2021-11-09 01:29:32 Starting new game.
2021-11-09 01:29:47 Started game version: 1.9 RC 1a (1.9.301.0)
2021-11-09 01:29:47 Extension: Armstrong Transport Player Ship [1.0]
2021-11-09 01:29:47 Using API version: 44
2021-11-09 01:29:49 Crash in CGDraw::ArcQuadrilateral
2021-11-09 01:29:49 Crash in CArmorHUDRingSegments::DrawItemBox
2021-11-09 01:29:49 Crash in CArmorHUDRingSegments::DrawArmorName
2021-11-09 01:29:49 Crash in CArmorHUDRingSegments::Realize
2021-11-09 01:29:49 Crash in CArmorHUDRingSegments::OnPaint
2021-11-09 01:29:49 Crash in CHeadsUpDisplay::Paint
2021-11-09 01:29:49 CException: Win32 exception.
2021-11-09 01:29:49 Crash in CGameSession::OnAnimate
2021-11-09 01:29:49 Unable to continue due to program error.

program state: OnAnimate
program state: painting armor display
save file: Matz05-2830.sav
system: SE
system type: 00100001
system name: Eridani
total objs: 980
destroyed: 0
deleted: 2
bad: 0
stars: 1
game state: in game

Please contact [email protected] with a copy of Debug.log and your save file. We are sorry for the inconvenience.

I went through my collection of playerships with non-standard segment counts to determine which exhibited problems.
Manticore-class Heavy Gunship: uses (customised version of?) 'old' UI with 6 segments, stable.
TZ-61-class Transport: Uses 'old' UI with 6 segments, stable.
Kingfisher-class Fighter: uses 'old' UI with 3 segments, stable.
Hammerhead II-class Gunship: uses 'old' UI with 3 segments, appears to use an older version of the dock services UI without visual diagrams, stable.
Albatross-class Barge: Uses 'old' UI with 6 segments, stable.
Armstrong-class Transport: Uses 'new' ring UI with 6 segments, CRASHES.
Played a debug game, upgraded my equipment to level 10, and played until I found an EI200 for sale in Rigel. Traded the cheated in ship for the EI200, used the proceeds to outfit it and fought in the arena for testing. This uses the 'new' ring UI with 6 segments. Appeared stable (fiddling with armour didn't crash) until my shields dropped in a melee and I took armour damage, then CRASHED! (did not display errors on screen) This is a notable problem, as the Debug Part 1 was the only mod I used, indicating that this could happen in regular gameplay with the EI200.

Relevant portion of debug.log after EI200 crash:
2021-11-09 02:07:32 Initializing adventure: Transcendence.tdb
2021-11-09 02:07:34 Created new game
2021-11-09 02:07:34 Starting new game.
2021-11-09 02:07:48 Loading image ResourcesScreenSnow.jpg for 61448.
2021-11-09 02:07:48 Started game version: 1.9 RC 1a (1.9.301.0)
2021-11-09 02:07:48 Extension: Debug Part I [1.0.2]
2021-11-09 02:07:48 Using API version: 45
2021-11-09 02:07:50 Loading image ResourcesArmorHUDShip_Sapphire.jpg for .
2021-11-09 02:07:50 Loading image ResourcesArmorHUD.bmp for .
2021-11-09 02:07:50 Loading image ResourcesShieldsHUDDefault.jpg for .
2021-11-09 02:07:50 Loading image ResourcesReactorDisplay.jpg for .
2021-11-09 02:07:50 Loading image ResourcesWeaponsHUD.bmp for 61447.
2021-11-09 02:10:26 Loading image ResourcesArmorHUDShip_Sapphire.jpg for .
2021-11-09 02:10:26 Loading image ResourcesArmorHUD.bmp for .
2021-11-09 02:10:26 Loading image ResourcesShieldsHUDDefault.jpg for .
2021-11-09 02:10:26 Loading image ResourcesReactorDisplay.jpg for .
2021-11-09 02:10:27 Loading image ResourcesSapphire.jpg for .
2021-11-09 02:10:48 Loading image ResourcesHumanSpace.jpg for .
2021-11-09 02:11:16 Loading image ResourcesArmorHUDShip_Sapphire.jpg for .
2021-11-09 02:11:16 Loading image ResourcesArmorHUD.bmp for .
2021-11-09 02:11:16 Loading image ResourcesShieldsHUDDefault.jpg for .
2021-11-09 02:11:16 Loading image ResourcesReactorDisplay.jpg for .
2021-11-09 02:12:27 Loading image ResourcesArmorHUDShip_Sapphire.jpg for .
2021-11-09 02:12:27 Loading image ResourcesArmorHUD.bmp for .
2021-11-09 02:12:27 Loading image ResourcesShieldsHUDDefault.jpg for .
2021-11-09 02:12:27 Loading image ResourcesReactorDisplay.jpg for .
2021-11-09 02:12:28 Loading image ResourcesSapphire.jpg for .
2021-11-09 02:12:56 Loading image ResourcesArmorHUDShip_Sapphire.jpg for .
2021-11-09 02:12:56 Loading image ResourcesArmorHUD.bmp for .
2021-11-09 02:12:56 Loading image ResourcesShieldsHUDDefault.jpg for .
2021-11-09 02:12:56 Loading image ResourcesReactorDisplay.jpg for .
2021-11-09 02:18:37 Crash in CSystem::Update
2021-11-09 02:18:37 Crash in CUniverse::UpdateTick
2021-11-09 02:18:37 CException: Win32 exception.
2021-11-09 02:18:37 Crash in CGameSession::OnAnimate
2021-11-09 02:18:37 Unable to continue due to program error.

program state: OnAnimate
program state: updating universe
game state: in game

Please contact [email protected] with a copy of Debug.log and your save file. We are sorry for the inconvenience.

On reflection, I probably should have created a new topic as I'm unsure if this is related to the original bug (maybe the fix only worked on Windows?) or if it's a separate issue. I just felt bad cluttering up your tracker with what might be a duplicate. Again, I apologize if my ineptness here made things more difficult than they needed to be.