Welcome Guest ( Log In / Register ) |
Quick Lists Top RatedTutorials Living World Map G… Ultimate beginner'… Arrow scaling bug… Raising Heroes max… Creating an asset.… Proper Fire Arrow… Simple Structure B… Making a simple Ma… Quick and easy sno… Making patrols nea… Mods The Dwarf Holds The Peloponnesian… RJ - RotWK The Elven Alliance… Helm's Deep Last H… The Elven Alliance Special Extended E… Kings of the West… RC Mod The Wars of Arda Downloads BFME1 1.06 Widescr… Enhanced W3D Impor… Fudge's Map Pack LotR/BfME HD Logos Osgiliath Shellmap Crystals Of Ancien… 2v1 Wold The forests of Dru… Converted BFME2 an… ROTWK animations f… |
|||||||||||||||||||||
Register and log in to move these advertisements down Known Game.dat errorsTutorial for BFME 2
This list was started a long time ago at the forums. It is a compilation of the sort of game.dat errors that happen in game and won't bother to give you a debug report. The ones we all love :P NOTE: This article is not here for you to ask how to fix a gamedat error: it's here so we can post solutions and discuss them. Currently known causes for game.dat crashes: - Using the same animation state twice in an object's code. Celeglin - Referencing a specialpower template that doesn't exist Celeglin - Giving a unit a non-existing armor (crash when your unit is being attacked). Morgoth946 - Missing asset.dat. Morgoth946 - Referring to inexisting weapons in any unit's weaponset ched - Referring to inexisting locomotors in any unit's locomotorset ched - Altered Skirmish profile (from playing a mod with new factions) (crash when opening the Skirmish menu) Solution: Simply delete it in the Application Data folder. ched - Setting MaxLevelMP in playertemplate.ini to 0 (crash when you first get magic points). Lord of Gifts - Using an inexisting AnimationState. Mullers_11 - Putting a non-existing object in the BannerCarrierPosition line of a horde module. Stealthsnake and zimoo - Putting a SpellBook button in a SpellStoreCommandset (crash upon opening the Spellstore). Stealthsnake and Makaveli - Missing shellmap (data\maps\shellmap1\shellmap1.map) (crash in the loading screen, at the moment the little spinning ring shows up). ched and 2playgames - Missing a PhysicsBehavior in a unit. NebulousQ - Referencing unknown particles in a FXList. Error occors on startup. Sulherokhh Update Jan 2008: - Setting GeometryMajorRadius = 0 Occurs with: All versions Description: The height and minor radius can be 0, just not that one, makes sense i guess, in a weird way... Submitted by: Halbarad - Conflicts with the HardCoded AI Occurs with: BFME 2 (and RotWK) Examples which cause this error: 1. Adding 'AIUpdateInterface' to an object with the new 'AIGateUpdate' 2. Adding 'AIUpdateInterface' to an object that is defined as a WallHubTemplate in 'skirmishAIdata.ini'. Further information: I introduced the behavior to have the object be able to both use lua functions and to be able to execute sequential scripts. But the game crashes when a script-function is being run on both kinds of objects (runtime crash). Submitted by: Sulherokhh Update November 2010: - Missing Behavior in Object Example: "I misnamed the DualWeaponBehavior into WeaponBehavior in one of my units" Occurrence of Error: At game start Submitted by: Tir I Herkaluin Note: As can be seen above, there have been reports of issues with various types of missing behaviors. I think it is reasonable to say that any type of behavior will result in a game.dat error when wrongly named - Missing Attribute Modifier Cause Trying to reference an Attribute Modifier that does not exist. Occurrence of error: "The game will crash at 97% when loading the faction in skirmish. A weird thing if the attribute is for a specific faction ie Rohan it will crash Good factions but Evil factions are ok." Submitted by: Radspakr - System.ini Cause Typo's, reference errors, etc Occurrence of error: At the Shellmap Submitted by: Radspakr - HordeContain module Cause: Horde without a HordeContain module Occurs with: BFME 1, but likely also BFME 2 Occurrence of error: The error came up just before entering a skirmish. The loading bar went all the way up and then the display faded out as it does. It went to the red screen, but just before fading into the map it crashed Submitted by: Gfire - Update limit Cause: The game can only manage a limited number of upgrades in ExperienceLevels.ini. - According to GothmogTheOrc this limit is 190 - According to Lauri this limit is 205 Occurrence of error: The game crashes when building the object that in the code lists an upgrade after the limit of ExperienceLevels.ini has been reached. If you have one to add to the list, please place a comment below. Thank you :) CommentsDisplay order: Newest first | Page: 1, 2 Imdrar - Thursday March 17, 2011 - 20:12 May I contribute another two errors to this list. Lauri (Team Chamber Member) - Sunday November 7, 2010 - 7:22 About the Upgrade limit. I recently ran into it, and have now tested it thoroughly, and can confirm that it is you can have a maximum of 205 upgrades. I don't know if this is he case with BFME2, but for BFME1 upgrade number 205 is the last one that works. Gfire - Sunday August 23, 2009 - 17:30 I found one. Radspakr Wolfbane (Team Chamber Member) - Monday July 27, 2009 - 10:14 Oh yeah another two for the list. Tir i Helkaluin - Friday March 7, 2008 - 22:27 I've discovered another error. Solinx (Team Chamber Member) - Thursday January 10, 2008 - 7:29 Updated with the two mentioned causes. Rewriting them all following that structure you mentioned is going to take more time than I have. Sulherokhh (Team Chamber Member) - Monday December 31, 2007 - 1:22 Hehe. :D ched (Team Chamber Member) - Monday October 1, 2007 - 16:26 be my guest :) Bart (Administrator) - Monday October 1, 2007 - 15:43 the list should be rewritten to a format like Sulherokhh (Team Chamber Member) - Monday October 1, 2007 - 1:33 That is what i assumed as well. So let me rephrase the concern: It's important to know if the specific crash accurs at the loadup of the menu, the loadup of the map or the use/creation of actual objects on the map at a later date. That would be pretty helpful as it narrows down which of the possibilities listed (or even a completely different one) is at the root of the crash. |
|||||||||||||||||||||
"One site to rule them all, one site to find them, © All Rights Reserved Eric Edwards ©2013. |