![]() I mean is nice, when you have some wild theory about code what you didnt even saw. You very often have absolutelly no idea what are you talking about, nor what are you doing. this exactly is why you coders need QA and ppl who do analysis. I had this happen to me when I was learning C++ and it's really difficult to find such issue, because random stuff unrelated to each other in code start happening then. They could overlook something when moving to C++, as memory management in C++ is very tricky and if they use pointers, it can get even trickier - when you have a lot of object, and you dynamically create some tables, if there's enough objects, they can override who knows what in other part of the memory. The code is probably a huge mess, if the game is being developed for 20 years. Oh, and if you didn't know, Dwarf Fortress is written both in C and C++. Unless, they made some asynchronous function for saving, but I wouldn't think anyone would code saving this way.ĮDIT. With slower CPU it would just take more time. Crashing during saving has nothing to do with CPU or GPU. You can make saving system that writes to a file sequentially, so the file can get as big as you want and you don't need a lot of system memory during saving. If a game is coded well, then saving just takes more time, it can't crash. It shouldn't matter what kind of PC you have, unless the game does it's saving by making the data structure in RAM first and you run out of memory, but it shouldn't be an issue on a modern PC.Ĭrashes during saving just shouldn't happen. There's many reasons why this can happen and it's for sure a coding issue, if it's happening during saving. If it just crashes, there's probably no checks in code for some extreme values that cause some overflow, or it runs out of indexes in some static table. If all exception would be handled properly, the game wouldn't crash, but instead inform about a specific error, why the game can't be saved. There's something wrong in the code related to saving the game. I have education related to game development, mostly programming computer graphics, but I made some games from scratch. That's why the best approach to making software is test driven development. Game just shouldn't crash while saving anyway. If the answer to both of these questions is no, then there's something wrong with the game. Second question: did you use default settings when creating the game world, or did you crank something up to extreme values? Originally posted by Kondiq:What's wrong with people on these forums?įirst of all, OP: Do you have any mods installed? When you know all of this, then what are you trying? You even know that it is not by other files on your PCĪnd you know that what you quoted dont say "buy a better PC", right? you are able read? You know that it is actually by broken save and thats why it always crash, when you are trying save it over that broken save.Īnd you know that your claim about coding were absurd inane mumbling, right?Īnd you know it it is not crashing because 200 citizens and 200 livestock/pets btw: you know that you are wrong and you do this only for trolling, right? if u cant add anything useful to the thread then keep quiet. Your answer to my question was "buy a better PC and stop complaining". now theres some serious dummass logic LMAO In games and in life.Įquating losing with the game crashing. Why do you want to win so badly anyway? Did you even have a good time playing the game? You know, I've found, that losing is quite fun. I'm not arguing against any of that logic. Try Banished with more than a few hundred villagers. Try modded Rimworld at high wealth, the raids will tank your fps and you will crash a lot. That's how literally every colony builder works once you push its limits. ![]() Thats hard programmed into the game where the same bug appears. That doesnt look even close to a CPU issue. Well i just replayed the gameworld from a much earlier save and i get the exact same savecrash if i try to save after a certain ingame date. I have a decent gaming PC with no fps issues at all in this game or any other and ur telling me its cos my 1 year old CPU isnt good enough. Or at the very least to suck it up and accept thats just the way it is. and ur also telling me thats by design LMAO So ur telling me its as intended that once u develop a large base that the game fails. ![]() Try to learn how the game works before calling something a bug. Originally posted by AlP:The game is tracking blood and dust from a forgotten beast your dwarves killed 10 years ago, which is now spattered over all your 200 dwarves, and their 5000 belongings and the fortress. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |