[RESOLVED] Crashes in CMO v1.09 Beta-Build 1774 (Steam)
Posted: Sun Nov 23, 2025 12:24 am
Altitude/Speed (F2) control window issues and crashes in CMO v1.09 Beta-Build 1774 (Steam) !
While testing the Steam version of Command Modern Operations v1.09 Beta-Build 1774, I encountered reproducible issues with the altitude/speed control window (F2), sidebar controls, and unit images. Updated details below.
🛠Problems observed
1. F2 window behavior depends on pause state
• Observed: The F2 altitude/speed window appears only when the game is paused, and in pause it remains open and usable.
• Issue: When the game is running (not paused), pressing F2 causes the window to appear briefly (around 2 seconds) and then auto-close, preventing changes to speed or altitude.
• Expected: The F2 window should remain open until confirmation, regardless of pause state.
• Additional note: This behavior in real-time mode started after downloading unit images from the server and adding them to the database.
2. Changing altitude while game is running
• Observed: Selecting an aircraft or ground unit and pressing F2 during live play shows the window for ~2 seconds before it disappears automatically.
• Impact: Makes real-time adjustments impossible without pausing the game.
3. Crash when changing altitude/speed via the right sidebar
• Observed: Attempting to change an aircraft’s altitude or speed using the right-hand sidebar controls results in a crash to desktop.
• Impact: Critical; prevents basic unit management through the UI.
System Information
• OS: Windows 11
• Platform: Steam
• Game Version: 1.09 Beta-Build 1774
• Mods: None
Notes
• The F2 window is stable only under pause; this appears to be a regression in live (unpaused) UI behavior.
• The sidebar crash is consistent and critical.
• The change in F2 behavior seems linked to the addition of unit images (.webp) downloaded from the server into the database.
Conclusion
Please investigate the F2 window handling when the game is running and the crash triggered by sidebar altitude/speed adjustments. The correlation with downloaded unit images may help identify the root cause.
Additionally, as in the previous beta builds, unit images are still missing in the right-hand unit status panel.
When collapsing the "unit status" section on the right sidebar, the game also crashes to desktop.
Additional crash log details (Build 1774):
During testing I also encountered the following error message in the exception handler:
"Error in Exception Handler! OnThreadException
Error in Exception Handler! theEx != null
Error in Exception Handler! e.Exception.GetType().Name: COMException
Error in Exception Handler! theEx.Message: The component initialization has failed. (Exception from HRESULT: 0x88982F8B)
Error in Exception Handler! theEx.StackTrace:
Error in Exception Handler! This is probably a Error in Exception Handler!. Please save a screenshot of this and submit it, along with the autosave files, for investigation."
• This COMException (HRESULT: 0x88982F8B) appears to be related to DirectX/Direct2D component initialization.
• It occurs when interacting with the F2 altitude/speed window and the right-hand sidebar unit image panel.
• As noted earlier, unit images are missing in the sidebar, and collapsing the image section also causes the game to crash to desktop.
I have saved the autosave files and can provide them along with screenshots if required.
Thank you.
While testing the Steam version of Command Modern Operations v1.09 Beta-Build 1774, I encountered reproducible issues with the altitude/speed control window (F2), sidebar controls, and unit images. Updated details below.
🛠Problems observed
1. F2 window behavior depends on pause state
• Observed: The F2 altitude/speed window appears only when the game is paused, and in pause it remains open and usable.
• Issue: When the game is running (not paused), pressing F2 causes the window to appear briefly (around 2 seconds) and then auto-close, preventing changes to speed or altitude.
• Expected: The F2 window should remain open until confirmation, regardless of pause state.
• Additional note: This behavior in real-time mode started after downloading unit images from the server and adding them to the database.
2. Changing altitude while game is running
• Observed: Selecting an aircraft or ground unit and pressing F2 during live play shows the window for ~2 seconds before it disappears automatically.
• Impact: Makes real-time adjustments impossible without pausing the game.
3. Crash when changing altitude/speed via the right sidebar
• Observed: Attempting to change an aircraft’s altitude or speed using the right-hand sidebar controls results in a crash to desktop.
• Impact: Critical; prevents basic unit management through the UI.
System Information
• OS: Windows 11
• Platform: Steam
• Game Version: 1.09 Beta-Build 1774
• Mods: None
Notes
• The F2 window is stable only under pause; this appears to be a regression in live (unpaused) UI behavior.
• The sidebar crash is consistent and critical.
• The change in F2 behavior seems linked to the addition of unit images (.webp) downloaded from the server into the database.
Conclusion
Please investigate the F2 window handling when the game is running and the crash triggered by sidebar altitude/speed adjustments. The correlation with downloaded unit images may help identify the root cause.
Additionally, as in the previous beta builds, unit images are still missing in the right-hand unit status panel.
When collapsing the "unit status" section on the right sidebar, the game also crashes to desktop.
Additional crash log details (Build 1774):
During testing I also encountered the following error message in the exception handler:
"Error in Exception Handler! OnThreadException
Error in Exception Handler! theEx != null
Error in Exception Handler! e.Exception.GetType().Name: COMException
Error in Exception Handler! theEx.Message: The component initialization has failed. (Exception from HRESULT: 0x88982F8B)
Error in Exception Handler! theEx.StackTrace:
Error in Exception Handler! This is probably a Error in Exception Handler!. Please save a screenshot of this and submit it, along with the autosave files, for investigation."
• This COMException (HRESULT: 0x88982F8B) appears to be related to DirectX/Direct2D component initialization.
• It occurs when interacting with the F2 altitude/speed window and the right-hand sidebar unit image panel.
• As noted earlier, unit images are missing in the sidebar, and collapsing the image section also causes the game to crash to desktop.
I have saved the autosave files and can provide them along with screenshots if required.
Thank you.