 |
welcome, guest |
| Help Forum | |||||
 |
| ||||
 Issy  Moderator  |
Hello there! I've been trying to have some wolfling runs while I am at work. Usually I pick a theme (arctic breeds, desert breeds, aquatic breeds, etc.) and inject the relevant metarooms and agents. I only inject ones I know that so far have not caused errors (or at least, catastrophic ones that the autokill cannot deal with). However, it seems like the worlds tend to get corrupt somehow after an unspecified amount of time. I have never seen these errors before, in all my years of playing. The errors in question are:
Attempting to launch the worlds affected by these errors prompts the last two errors to pop up, in order, and the game to close. The first error happened only once, but I am unsure what caused it. Any ideas of what could be wrong? I do have a lot of third party works installed, so perhaps things are just clashing. But it is odd to me that the game works fine for a while. Could it be from my screensaver, perhaps? I know some applications despise running when the computer is not active. Any help is appreciated! For now, I will see if disabling my screen saver causes any change. ~Issy ![[ngeek]](/images/smilies/emot_geek.gif "[ngeek]") |
||||
 Sanely Insane RisenAngel Manager |
I've seen errors like this before running wolfling runs. I might be mistaken, but this looks like an error that won't do much more than simply make you restart Docking Station and make you lose some progress (which can be immensely frustrating if the autosave hasn't kicked in for a while; I recommend using an agent like the Advanced Autosaver to minimize the amount of progress lost). What I usually do when I get such an error is empty the world's Attic folder (Docking Station/My Worlds/<world name>  . That's where all unused genetics files go for creatures that died in the world (as opposed to the world's Genetics folder, which is where all the genetics files for the currently living creatures in the world go). If your world's been running for a while and you've got lots of high gen creatures, chances are there's at least a couple MB worth of old genetics files in there. I've found that emptying the Attic folder regularly helps cut down on the error appearing. However, it has been a while since I've run a wolfling run (or even touched C3 or DS). There's also a chance that this error is fatal and will pop up eventually even if you restart the world after the crash (if you're really unlucky it'll pop up again immediately). If it doesn't pop up again immediately you'll have some time to export all your creatures and then delete and remake the world, but there's nothing you can do to save the old world. There are some third-party breeds whose sprites can cause the latter kind of error (the Zwergbunt Grendels, for example). If it pops up you can try exporting any creature using third-party sprites and see if that prevents the error, maybe even finding which breed is the culprit. If nothing else works, unfortunately the only fix I can think of is simply to delete the world. Sometimes errors pop up for the weirdest reasons (I once had a norn somehow wind up out of bounds of a room which caused a fatal error in that world) or for no good reason at all. Usually the fatal errors are marked with "Caught C-Style structured exception" (or something along those lines). I don't see that here, which makes me think it's the former kind of error. That kind of error can also be predicted if you happen to notice a lot of agents getting autokilled beforehand, even things like favorite places and the HUD. Risen Angel's Creatures Blog |
||||
Issy Moderator |
I will look into getting that agent for sure. That makes sense about the attic, I'll take a look tomorrow and see if anything changes when I clear it out a bit. The error is indeed a fatal error-- it occurs after less than a fourth of the loading bar completes for loading the corrupted world. Both pop up and then the game closes. So, I cannot even enter the world anymore. I should have some creatures from the world exported though, I use that population control panel agent that automatically exports creatures after having a specified amount of offspring. Perhaps this agent could be the problem? I should test that. One of the breeds in the most recent world did have Yettin arms, (which do not look correct, so that could be one of the problems, if I am understanding you correctly) but the rest were mall/official breeds, fimbul norns, and a Gaius with cupid's halo left to meander around. If you cannot tell, this was the arctic wolfling run. ![[nsmile]](/images/smilies/emot_smile.gif "[nsmile]") I did notice that the Eggernator II creates a small metaroom that any creatures in it are transported to-- so that could cause some issues-- but I did not have that agent in the world since it prevents eggs from hatching on their own for some reason. I think I had it in the world that crashed with the emergency safe place error. However, I cannot be certain since it was a few days ago. Yeah, usually when the world crashes I see that C-style exception, but every time so far it has been everything but that. Hmm... Thank you for the help, I will pursue some of your suggestions! ~Issy |
||||
 Patient Pirate ylukyun Manager |
Do these errors still happen if you run a vanilla world (no third-party breeds or agents) for a comparable length of time? |
||||
Issy Moderator |
Unsure, I would have to test that. I will let a world run overnight with nothing extra in it! ~Issy |
||||
Issy Moderator |
I ran the game for two days in a world with only mall/official breeds. All the norns eventually died but the game never crashed. The only agent I injected into the world was the Autonamer. I'll try adding the Population Control Panel and Cupid's Lyre to put some emphasis on breeding to see if it's the Population Control Panel that is causing the crashing. It seems like exporting creatures can be a bit taxing on the game. I noticed there was also a computer memory issue-- I had several videos of gameplay an hour or so in length from a different game that were taking up a lot of disk space, so I deleted them. I did not even know I was "running low" until DS threw an error up complaining about disk space. It has stopped yelling at me now, thankfully. After fixing the memory issue, I still cannot open the "corrupt" worlds, it just throws up the memory mapped file error. I believe they are lost for good. I tried to also access the "My Worlds" folder to empty the attic as suggested, but curiously, there are only four worlds listed there. I now have around ten, with the four listed being the first ones I created. Only one of the attics for these worlds actually has .gen files in it. Not sure what is going on there. Actually, come to think of it, part of the problem could be that originally I only had Docking Station, but then acquired Exodus. I believe I may have copied my files over from the standalone version, including worlds. Those four worlds I mentioned are not playable in Exodus DS, despite me copying them over. I'm not sure what is up, I'm just throwing a bunch of ideas out there. I might just have to wipe and reinstall Exodus again, without copying the worlds and such. EDIT: So far so good with the new world. I'm thinking I might have just had too much going on at once and the game could not handle it. ~Issy |
||||
| downloads cobs adoptions creaturelink metarooms breeds gallery art wallpaper screenshots graphics promos sprites |
dev hack shack script reservations dev resources active projects dev forum community links advice chat polls resources |
creatchi forum bookmarks general news help development strangeo survivor |
mycaves log in register lost pw |
0 online |
| creatures caves is your #1 resource for the creatures artificial life game series: creatures, creatures 2, creatures 3, docking station, and the upcoming creatures family. contact help privacy policy terms & conditions rules donate wiki |
||||