FIXED - Beta v4.58 - Crash To Desktop Bug

[CrispyMouse]

This bug has been submitted via the reporting tool.

I'm in combat to get the hammer back. If I click the "Com" button I crash to desktop. I've done this three times now, just to make sure it is reproducible.

Have fun.

Here is the Problem Details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Horizon.exe
Application Version: 0.0.4.58
Application Timestamp: 529ff9b3
Fault Module Name: MSVCR100.dll
Fault Module Version: 10.0.40219.325
Fault Module Timestamp: 4df2be1e
Exception Code: c0000005
Exception Offset: 00010a62
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[CrispyMouse]

Engaged a different sector. Press the "Com" button on the colonizer in that sector and crashed to desktop.

[CrispyMouse]

Went to a different save game ... different setup, no missions ... (slot04)
When I pressed "Com" the window came up and I could switch to a different ship just fine.

Went back to the problem game and tested with ship that was in my communication range...still crashed to desktop.

Differences between the games that I'm aware of:
Problem game...missions, some ships outside of the communication range
Working game...no missions, all ships inside the communication range.

[Zaimat]

Thanks, will check this out. Was this a new game started (in 4.57 or 4.58) or older ?

[CrispyMouse]

The problem game was started in 4.58
The working game was started in 4.57 or older.
In the working game I moved a ship out of communication range and tried the coms and it still worked.

Another difference between the games is I'm transient in the non-working but I'm not transient in the working.

[Zaimat]

This bug has been fixed and will be in the next update in test branch (v4.59). Thanks to everyone for reporting it.