Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
But Imperium has tons of other issues so I think MotBW is a better game especially with Jagulars's fixes.
I hope the devs could fix it someday, they can do it in Imperium, then they can also fix the error in MotBW if they like.
Also, try to reload a save, see how much memory is consumed, then reload it again. You'll probably see that on the second reload, more memory is used even though everything should be identical. Also, players seem to report less Access Violations when they reload less. It's possible that there's something wrong with the loading code, which would be unfortunate because it is engine code, and apparently even Snowbird does not have access to the engine's source code.
It's also possible that the errors are caused by generally faulty memory management. Every time you open an interface window, construct a building, enter a battle or shoot an arrow, new objects are created. And when you close that window, destroy the building, finish the battle or watch the arrow reach its target, those objects are deleted, and removed from memory. If, for whatever reason, that memory is not allocated or deallocated correctly, it will eventually cause Access Violation. To test this, I've been working on a workaround that would minimize the creation and destruction of objects by storing and reusing them whenever they're needed or not needed. This is, however, an enormous task, involving hundreds of game script files. We will see how it works out.
Yeah, there is also something wrong with the loading code.
I believe that the game cannot clean up loaded resource in time and properly either on reloading or normal playing is a very possible reason which causes the error. Eador is a 32-bit game and it cannot handle more than 2GB memory in theory, 1.6GB in fact.
Your mod and fixes are highly appreciated, the devs should pay your awesome work!
I have the first one which apparently had bugs to but has the new horizon mod which fixes a bunch and is at least playable with minimal issue. Was eye balling the two 3d games but after finding out that BOTH have game breaking bugs that happen to pretty much everyone i lost interest. I see that Jagulars is trying to fix this game but it still has the bug mentioned in this post which to me sounds game breaking even if you can just do something different and then pray it works. I like to concept and systems of this 4x game but i have zero confidence that the devs will pull anything together in the future and hearing they lack funding does not help.
Regardless of the remaining game breaking bugs, I'm not impressed by their talent at all. 90% of the new units in Imperium are lazily and poorly designed, from the portraits to the skills, and most of the changes they made only hurt the gameplay.
Glad to hear.
Eador Genesis is a masterpiece.
Check out his Steam Workshop: https://steamcommunity.com/profiles/76561198035603355
He has made some high-quality mods for other games.