![]() ![]() How to avoid: Use one of the above approaches to avoid this problem before saving the zoo. Symptom: A saved game is loaded in MM or CC and the game crashes immediately or soon after.Ĭause: This is the same problem as above. I do not know what length of time one would need to wait before removing the fence, but this approach would make it easier to wait longer and the fence could also make it easier to relocate that location if you decide to go and do other zoo building while waiting. That way any guests that are on their way to the object will eventually get to the fence and stop. Wait a length of time without the game being paused before deleting that decorative fence. I do not know what that length of time to wait should be.Īnother approach is, before replacing an object with another object, put a decorative fence around the object, at least 1 tile away from the object. Once the guests get there, they will see that there is nothing there and will then go elsewhere. It has to be enough time for all guests that are on their way to that location to get there. One approach is, after deleting an object that guests might go to look at, wait a length of time without the game being paused before putting another object at that location. How to avoid: There are 2 approaches that can be used to avoid this problem. For example, if the tar pit is replaced with the ring toss game while adults are on their way to look at the tar pit, those adults will go and look at the ring toss game without going in and will have the guest thought for the ring toss game, even though the ring toss game is only for children. Interestingly, if the object is replaced with an object that does have a ".dll" ID, the guest will still go to look at it, but will have the guest thought for the new object instead. But when the guest gets there, MM/CC do not check if the object was changed and the game crashes. If a guest starts walking to such an object and that object is then replaced with an object that does not have a ".dll" ID, which most user made scenery, rocks, and foliage do not, the guest continues to go to the object. When MM/CC sees such an object, MM/CC will eventually have a guest go look at it. Those objects have to have IDs that are in ".dll" files. Most of the objects that come with Zoo Tycoon and some user made objects can be looked at. In MM, Blue Fang added the ability for guests to go look at objects. Symptom: An object is changed to a different object, usually a user made object, in a zoo in MM or CC and the game soon crashes.Ĭause: It is a mistake in the MM/CC program. But the list will include some crashes that can occur from user made objects if they involve things that are often missed in testing. This list does not cover most of the crashes that can occur from user made objects that were not configured correctly, since those should be found during testing. It also gives some ways to avoid the crashes. This lists some things that can cause Zoo Tycoon 1 to crash (ie, the program ends unexpectedly). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |