• Anno 1404 Game Guide
• Anno 1404 Gold Edition

Savegame for Anno 1404 – 600000 gold – 51 warship – The Church and the Mosque built – 20,000 people – 27 to fame – Players: d ‘Artois, Flores, Merchant. Anno 1404 Full PC Game Overview. Anno 1404 Download. The 'Anno 1404: Venice' expansion adds 300 new quests. (among other things) a serious save game.

Anno 1404 Game Guide

I've got the same issue with Venice. Crash to desktop during saving, corruption of the savegame. This is an issue that was meant to be solved in the anno patch 1.1 and is back in the 2.00.58 version of Venice (never experienced the savegame corruption in Anno DoD though).

Can't find any work around solution, to change the graphic settings, to change the compression in engine.ini none worked so far. I've contacted the tech support (in France)and they said I was the first to report this kind of bug. They offer no solutions whatsoever, just killing extra process, thing I do for myself (I'Ve got only 22 process running and 90% windows related) or update my video driver (also done).

I' don't know if Related Design (I guess they're in charge of the dev for Venice addon) is working on a patch but to feedback to the tech support can (I'm not saying it will. Alas) help to get a patch in the future regarding the savegame issue. Also do anyone have ever tried to max the priority of the process of the game (Addon.exe and AddonWeb.exe)? I will try that now, can't thing of something new to solve the issue.

Don't know if it will change a thing. I realize this is a deadish thread but I thought I would pop in for a moment to share my experience. For some reason my ANNO1404:Venice fixed. I did three things to my computer that could of caused it. (1) Upgraded the cooling system (2)Upgraded from a HD 4650 to a HD 5750 GPU (3) Uninstalled my HD 4200 Integraded card.

It isn't a cooling issue in my mind as stated here and other places. Fact is my CPU/Ambient(case) after playing for an hour when it let me get that far was always around 43C/46C with the crashes and even though I upgraded the cooling im running hotter now.around 49C/42C under the same conditions.

Also my card runs at around 52C which is a little high but not for that card under load. I have no way of comparing it because I had no temp moniter on my old 4650. Blah blah blah not temp.

If anything my temps are worse. Unless of course it was my RAM and the ambient is an indication that my RAM is cooler, but none of my cooling upgrades effect my RAM directly and if anything im putting more stress on them.

I'm not an expert, but I doubt ambient would make that much of a different on them considering. I upgraded from a 4650 to a 5750.

Anno 1404 Gold Edition

What that means? I again am not an expert. Could be the 3D engines just get overloaded when saving.That upgrade also meant an upgrade from DX9 to DX11. But im sure there are plenty of people without 11 running it fine or you would hear a lot more about this problem. 5750 is just tons better. I'd be offended if it didnt run on it. But I also know from reading elsewhere this problem affects everyone from low end integrated to high-end so.:shrugs: I uninstalled my integrated GPU drivers.

This could be huge depending on the rig. I previously had not done this with my 4650 because I didnt think about it and the card worked fine.

But my negligence I doubt is repeated by everyone. Seems to me a lot of experienced people are having this problem. I doubt its a rock uncovered.

But for those who have not done this id highly recommend it as a possible fix that doesn't involve upgrading. Oh also.the game works on my personal comp (the one above is my girls).

I have both the specs posted below. Girls- Motherboard: RS780 (Gateway-Stock) GPU: XFX 1GB HD5750 RAM: 8 GB DDR2 CPU: Phenom II x4 810 (2.6Ghz Stock) PSU: 550W Mine- Motherboard: ASUS M4A79 Deluxe GPU: XFX 1GB HD5770 RAM: 8GB DDR2 CPU: Phenom II x4 965 BE (3.4Ghz) PSU: 650W. I have given some thoughts to people why the 'savegame crash' appears in the German forum area. One of the things that is open to questioning is whether Anno1404 is compiled with the extended address flag enabled.

As some/seemingly most here run 64bit systems with 8G ram and no problems (as far as this peculiar problem is concerned) I am led to believe that Anno1404 does indeed allow for 4G ram addressing. In that case, you are reasonably safe.

Another unsolved problem is the question whether this bug could also be invoked due to graphic card memory overflows. I'm inclined to also think this could be the case as the person switching from a 4650 to a 5750 may have more memory on the card (and ATI's cards are known to lose less memory than NVidia's cards.) Now why do people (including me) see the 'savegame bug'? This is an old programming problem that lurks behind every program that 'does a lot of things'. As you might know, a 32bit system has only 2GBytes memory available (and without the extended flag set, every system has, as well).

When you play Anno1404, memory gets allocated whenever something is built or appears in the game to store the associated info. The system uses something called 'heap pointer' that points to the next free memory available. If you build a house, say 200 bytes get allocated and the heap pointer is moved upwards 200 bytes to protect the memory you just reserved.

When you tear down a house, its memory gets deallocated. However, the heap pointer cannot move downwards, as your house's memory is likely somewhere in midst of all your reserved memory space.

At some point, your memory will look like Swiss cheese: lots of occupied space and lots of memory holes. When you build too many houses, at some point your heap pointer reaches the end of the 2G space available and can no longer be moved forward.

The system will return a Null pointer (this is something that points to memory location 00000000 in your computer), telling the program there is no more space for whatever you are trying to do. Now the program has to react to the Null pointer message in a reasonable way. In an ideal world, the program does something called 'full resource tracking'. This basically means that it can collect all the memory holes into one big hole, shift the used memory down (the size of the big hole) and has free memory available again above the used memory. If Anno1404 would do this, it might have three times the code size and probably ran at half the speed, because this full resource tracking is a total mess to implement, since it has to check every single memory allocation.

Probably no game does this, they usually assume that getting a few bytes will work because '2G is so much memory'. This is an assumption that is almost always correct in real life. Now Anno1404 crashes, and the question is why? There are multiple occasions that a Null pointer can pop up (and reading or writing to or from memory location 0 is absolutely lethal), but mostly it happens during writing savegames that end up being only 0-70kbytes long. That problem has existed since the early beta testing phase. When you save a game, several data packets are created in memory which form the savegame, one of which is an encrypted memory stream of your compressed map info. These 30-70kByte savegames never contain the encrypted map, so it is very likely that the encryption returned a Null pointer since it could not create the memory space needed (10-20mBytes are needed for that.

And since you could not get the memory the first time, all subsequent attempts to try another save also fails with 100% certainty). There are other ways for Anno1404 to run out of memory, sometimes Anno1404 will crash during loading of a savegame. This means that not all memory was freed from the game you ran just before loading a new one. How will this help you? - I'm afraid not at all. There are a few things you can do to postpone the bug as long as possible. A) Use systems with 4G memory on 32 bit systems.

At least Anno1404 gets its full 2Gbytes as other stuff (the OS and other tasks still have around 1.2Gbytes to clog up). B) Use as much memory as possible on 64bit systems, as Anno1404 seems to have the extended addressing mode enabled (not sure about that, there are hints to that effect). C) Use the smallest map size possible for whatever you want to do. The huge map has 1440.1440 tiles, the large map only 1024.1024. Estimating that every tile needs about 200 bytes of memory, we are looking at a savings of 200mbytes alone by using the smaller map size d) Pray that RD removes all the crap from the code that wastes memory and finds a way to reduce memory use or introduces full resource tracking. (Don't count on d), option d is the least likely to come true).

E) graphics settings probably do not influence the problem, as most users have cards with = 512M ram. I have had this problem for a while (but no solution), but was a bit slow 'googling' for errors rly noobish of me. But anyway; this seems definitely as a memory issue (no clear evidence though) based on the nature of the error. The game gives two different errors when I have played 'huge' maps for a while; and this is VERY frustrating. The two errors are: One with the last savegame corrupt but no specific error message. I am able to load one of the other savegames.

The other error gives 'Load Failed' and NO savegames can be loaded; they all give the same error message. I am using a mix of QuickSave and manual Save and even then none are useable at all when 'Load Failure' occures.

UbiSoft provided the game and should be the one responsible to get a fix for this EDIT: I checked quite old Savegames and those less than approx 12 Mbyte seem to be OK. Those saved AFTER the last OK one are of 34K - 54K size.

Damnit, gave the game a chance and nothing helped, game was at 30 hrs + and suddenly when i saved i noticed that 18kb savefile so i kept saving hoping it would save properly but it seems that doesn't help either, all games after the initial 18kb games were the same until after 5th or so save game crashed, all my settings were on low so graphics settings are out.it's probably the size of the game that's the problem since mine were close to 18mb. Since it seems to take half a year + to figure out this problem I'm leaving this game until something gets fixed.if that ever happens such a shame. If this helps.