Diagnostics - 2020'09'10 @0012'35''.html

Every attempt to print the list leads, in the diagnostic file, to

* below exception statements

* below error stack at message level

This definitly appeared AFTER the latest patch, with or without mods.

Reproduced in 1.5.34 S5 GOLD-Public

Error: {"error message":"InvalidCastException: Cannot cast from source type to destination type.","callstack":" at UnityEngineLogCallback in Error while parsing stackframe: ImprovementsManagementModalWindow.deleteTemporaryImprovements ():line 0\n at UnityEngineLogCallback in Error while parsing stackframe: ImprovementsManagementModalWindow.OnBeginShow (Boolean instant):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: Amplitude.Unity.Gui.GuiPanel.Show (Boolean instant):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: Amplitude.Unity.Gui.GuiWindow.InternalShow (Boolean instant):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: Amplitude.Unity.Gui.GuiWindowsStack.ShowWindow (Amplitude.Unity.Gui.GuiWindow guiWindow, Boolean instant):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: Amplitude.Unity.Gui.GuiWindowsStackModal.ShowWindow (Amplitude.Unity.Gui.GuiWindow guiWindow, Boolean instant):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: Amplitude.Unity.Gui.GuiManager.ShowWindow (Amplitude.Unity.Gui.GuiWindow guiWindow, Boolean instant):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: ColonyInfoSidePanel.OnImprovementsCb ():line 0\n at UnityEngineLogCallback in Error while parsing stackframe: UnityEngine.GameObject:SendMessage(String, Object, SendMessageOptions):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: AgeControlButton:HandleMouseUpOrDown(AgeMouseEventData):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: AgeControlButton:MouseUp(AgeMouseEventData):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: UnityEngine.Component:SendMessage(String, Object):line 0\n at UnityEngineLogCallback in Error while parsing stackframe: AgeManager:UpdateInteractivity():line 0\n at UnityEngineLogCallback in Error while parsing stackframe: AgeManager:LateUpdate():line 0\n","turn":68,"gameID":"2721126b-4e71-4d1c-8b6c-44e7bad5f9c7","eventID":"5.19.01","eventName":"Error","steamID":"76561197971020338","gamecode":"392110","sessionID":"b0952d5aac464501847c54b1c123c292","eventTimestampClient":"2020-09-10T00:30:25.401"}

Hello.
I've this same problem...
https://steamcommunity.com/sharedfiles/filedetails/?id=2228177996

Same problem, with every race, in every game.

It is really annoying, when you want to put a ' Trade Company Subsidary ' somethere else.

Hope you guys fix it soon!

The Content Penumbra is deaktivated (because the Hacking is annoying), if it helps.

Diagnostic (can't upload it, I think its to big (35mb))

027.sav

CaptainCobbs wrote:

Please attach a diagnostics file from when this happened, they are located in Documents/Endless Space 2/Temporary files

I don't know if that's how it's done, but I want to bring attention to the fact that I've found out how to reproduce this bug.  Leveling a system up leads to this bug. Sorry if replying like this is wrong or something.

I've tested it and it happens with the first system that you level up to 2. I tried leveling 2 different systems in one turn, but only one of them got bugged. So maybe the reason is the tutorial message ot something. But I turned off tutorials and it happened to me anyway, so I guess I'm wrong.

I really-really hope that this bug gets fixed, so here's a savefile - ending the turn causes Mira to break. But if you delay building leveling up in Mira, than the other system with the level-up in queue breaks - Bundus. 

Oh, wait, they both stopped working. One of them can't show any of it's improvements, and the other just stopped showing newly built ones - the ones that are built after the level up

8 Leveling to 2 breaks improvements menu.sav

Strange, i had this issue before i got umbral choir expansion.After that bug disappeared. Having expansion removes bug or is this just a coincidence and latest path fixed it?