Here's the report. This happened on both 1.8 and 1.9
Sovereignty Error Report - Version: EA1.9 Build: 48
Reporter ID: 76561198031847192
Loaded Mods: None
=========================================================
Sovereignty Crash in thread: Main
Error: E_OUTOFMEMORY: Ran out of memory (-2147024882)
Stack traces:
-------------
Active thread (Main):
Method: Void Throw[T](System.Object, System.Object)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\result.cpp
Line Number: 119
Method: SlimDX.Result Record[T](Int32, Boolean, System.Object, System.Object)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\result.cpp
Line Number: 150
Method: SlimDX.Direct3D9.Texture FromMemory(SlimDX.Direct3D9.Device, Byte[], Int32, Int32, Int32, SlimDX.Direct3D9.Usage, SlimDX.Direct3D9.Format, SlimDX.Direct3D9.Pool, SlimDX.Direct3D9.Filter, SlimDX.Direct3D9.Filter, Int32)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\direct3d9\texture.cpp
Line Number: 165
Method: SlimDX.Direct3D9.Texture FromStream(SlimDX.Direct3D9.Device, System.IO.Stream, Int32, Int32, Int32, Int32, SlimDX.Direct3D9.Usage, SlimDX.Direct3D9.Format, SlimDX.Direct3D9.Pool, SlimDX.Direct3D9.Filter, SlimDX.Direct3D9.Filter, Int32)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\direct3d9\texture.cpp
Line Number: 254
Method: SlimDX.Direct3D9.Texture FromStream(SlimDX.Direct3D9.Device, System.IO.Stream)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\direct3d9\texture.cpp
Line Number: 271
Method: Void CreateAnimationSprite(System.String, Int32, Int32, System.String, Single, Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\GameData\UnitSpriteInfo.cs
Line Number: 626
Method: Void SpriteInfo_OnAnimationFinished(Sovereignty.GameData.TimedSpriteInfo)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\GameData\WorkingData\WorkingUnit.cs
Line Number: 2333
Method: Void UpdateDamageSprites(Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\GameData\UnitSpriteInfo.cs
Line Number: 742
Method: Void UpdateDamageSprites(Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\GameData\WorkingData\WorkingUnit.cs
Line Number: 2929
Method: Void UpdateMovingUnits(Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\Game\Battle\BattleController.cs
Line Number: 4641
Method: Void Render(Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\UI\CombatMap.cs
Line Number: 738
Method: Void Render(Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\UI\GameMap.cs
Line Number: 2408
Method: Void RenderEngine_OnRender(Single)
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\UI\UIEngine.cs
Line Number: 427
Method: Void Invoke(Single)
File:
Line Number: 0
Method: Void RenderFrame()
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\Engine\RenderEngine.cs
Line Number: 334
Method: Void OnIdle(System.Object, System.EventArgs)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\windows\messagepump.h
Line Number: 47
Method: Boolean System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32)
File:
Line Number: 0
Method: Boolean System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
File:
Line Number: 0
Method: Void RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
File:
Line Number: 0
Method: Void RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
File:
Line Number: 0
Method: Void Run(System.Windows.Forms.Form)
File:
Line Number: 0
Method: Void Run(System.Windows.Forms.Form, SlimDX.Windows.MainLoop)
File: c:\users\promit\documents\projects\slimdx\main\trunk\source\windows\messagepump.cpp
Line Number: 55
Method: Void StartThread()
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\Engine\RenderEngine.cs
Line Number: 266
Method: Void MainFunc()
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\Program.cs
Line Number: 229
Method: Void ThreadFunc()
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\Engine\ThreadManager.cs
Line Number: 79
============================END THREAD TRACE============================
AI:
Method: Void MainThreadLoop()
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\AI\AIThreadController.cs
Line Number: 69
Method: Void ThreadFunc()
File: c:\Users\Jekky\Documents\Visual Studio 2010\Projects\Sovereignty\Sovereignty\Engine\ThreadManager.cs
Line Number: 79
Method: Void ThreadStart_Context(System.Object)
File:
Line Number: 0
Method: Void RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
File:
Line Number: 0
Method: Void Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
File:
Line Number: 0
Method: Void Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
File:
Line Number: 0
Method: Void ThreadStart()
File:
Line Number: 0
============================END THREAD TRACE============================
crashing
Moderators: Slitherine Core, Gothic Labs
Re: crashing
Well, as it says, you ran out of memory - how much memory does your PC have?
Assuming it has enough, then if it was a one-off, it may just be that the game was running for a long time (even a tiny memory leak can build up if left for enough hours) - if this is a consistent error, then we probably need to look in more detail (in which case information regarding how often, what you were doing, etc would be useful)
The upcoming 2.0 patch should resolve a lot of issues related to stability, and reduces memory footprint quite a bit, so if all else fails, it will probably help.
Assuming it has enough, then if it was a one-off, it may just be that the game was running for a long time (even a tiny memory leak can build up if left for enough hours) - if this is a consistent error, then we probably need to look in more detail (in which case information regarding how often, what you were doing, etc would be useful)
The upcoming 2.0 patch should resolve a lot of issues related to stability, and reduces memory footprint quite a bit, so if all else fails, it will probably help.
Re: crashing
Jekky wrote:Well, as it says, you ran out of memory - how much memory does your PC have?
Assuming it has enough, then if it was a one-off, it may just be that the game was running for a long time (even a tiny memory leak can build up if left for enough hours) - if this is a consistent error, then we probably need to look in more detail (in which case information regarding how often, what you were doing, etc would be useful)
The upcoming 2.0 patch should resolve a lot of issues related to stability, and reduces memory footprint quite a bit, so if all else fails, it will probably help.

And this is a consistent error. It usually happens at a certain point in a campaign, and every time I load that save (Or any other save around then) it'll happen fairly consistently when I go into a tactical battle. It happened around turn 70 for my wood elf campaign and around 160 in my cor vilad campaign.
I want to say it correlates to fighting rebels, but once the crashing starts it just never stops no matter who I'm fighting. I'll get maybe 2 more battles before another crash. Reinstall didn't fix, the game verifies fine.
Re: crashing
Well, i don't think we'll be putting out another patch before the 2.0 update, but as stated, it will be big on stability improvements, unfortunately it will also not be save-compatible with older saved games.
There is defiitely something going on there with battles though.. possibly with the attack/damage animations - so we will look into that area, make sure that it doesn't have any memory leaks for 2.0.
There is defiitely something going on there with battles though.. possibly with the attack/damage animations - so we will look into that area, make sure that it doesn't have any memory leaks for 2.0.
Re: crashing
Hey, EA for a reason right XD.Jekky wrote:Well, i don't think we'll be putting out another patch before the 2.0 update, but as stated, it will be big on stability improvements, unfortunately it will also not be save-compatible with older saved games.
There is defiitely something going on there with battles though.. possibly with the attack/damage animations - so we will look into that area, make sure that it doesn't have any memory leaks for 2.0.
The game's great when I'm not crashing though

-
- Private First Class - Wehrmacht Inf
- Posts: 8
- Joined: Tue Sep 16, 2014 8:31 pm
Re: crashing
Hi
I had the same problem with my Maledor Hardcore campaign.
When I seized goldenspire and killed the boravian emperor, all else wen rebels.
When I fought rebels with my army in tac mode. It crashed and everything crashed after in tac mode (no problem in automatic mode).
But I can't win in auto mode
, computer plays too bad.
We should avec ranks in auto mode (first line, second, ...)
I had the same problem with my Maledor Hardcore campaign.
When I seized goldenspire and killed the boravian emperor, all else wen rebels.
When I fought rebels with my army in tac mode. It crashed and everything crashed after in tac mode (no problem in automatic mode).
But I can't win in auto mode

We should avec ranks in auto mode (first line, second, ...)