Pyrdacor/Ambermoon.net

[Bug report] Lizard fight crash

fluff79 opened this issue · 6 comments

Describe the bug
Entered the cellar at the beginning of the game and at the well , when the lizard jumps out, the game crashes before the battle starts.

here is the error log

The type initializer for 'System.Runtime.Serialization.Formatters.Binary.Converter' threw an exception.

at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.GetAssemblyId(WriteObjectInfo objectInfo)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, BinaryFormatterWriter serWriter)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph)
at Ambermoon.Data.Monster.Clone()
at Ambermoon.Data.MonsterGroup.Clone()
at Ambermoon.Game.<>c__DisplayClass557_0.b__0()
at Ambermoon.Game.Update(Double deltaTime)
at Ambermoon.GameWindow.Window_Update(Double delta)
at Silk.NET.Windowing.Internals.ViewImplementationBase.DoUpdate()
at Silk.NET.Windowing.WindowExtensions.<>c__DisplayClass2_0.b__0()
at Silk.NET.Windowing.Internals.ViewImplementationBase.Run(Action onFrame)
at Silk.NET.Windowing.WindowExtensions.Run(IView view)
at Ambermoon.GameWindow.Run(Configuration configuration)
at Ambermoon.Program.Main()

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Running on a windows PC, the advanced ambermoon 1.03. Downloaded it earlier this evening from github.

Additional context
Add any other context about the problem here.

Thank you!

Reloaded the crash save and tried again without the issue reoccuring.

Can you start any fights?

Still strange that this happened. I leave this open as a reminder to have a closer look at it.

This never happened again I guess. I will close this now. If it occurs again, someone will most likely create a new issue and I can investigate further then if needed.