11/13/2023 0 Comments Gzdoom save failed![]() Memory errors I_AllocLow: DOS alloc of %i failed, %i free Īn allocation of low DOS memory, RAM within the first 640 KB of address space required for communicating with real mode code, failed. This error should never occur.Īn enemy has attempted to move in an undefined direction. While sliding the player against a line, the traversal code has iterated over an intercept object which represents a moving object (enemy, torch, etc.) rather than a line. This includes gun-type switch lines, and so the easiest way to cause this error is to put too many consecutive gun switches on two-sided lines. The player has activated too many switch-type line actions at a time. This error can be easily triggered by modifying pickup items through DeHackEd. The player has touched a thing which is marked as a collectable item, but for which the game does not have a hard-coded sprite-based effect. This error most often occurs if maps are loaded in the wrong game, or occasionally with carelessly made DeHackEd patches. The map being loaded has an unknown type of thing specified at the given x-y coordinates. P_SpawnMapThing: Unknown type %i at (%i, %i) This error can occur in some versions of Doom in response to an intercept overflow. The game has tried to stop a platform action that it apparently never started in the first place. The player has stepped in a sector with an undefined special, or type, value. P_PlayerInSpecialSector: unknown special %i P_NewChaseDir: called with no target Īn enemy looking for a new direction to move in is not actually moving toward a valid target. This error can occur if the texture directory is reordered so that the last flat or texture in a sequence occurs before the first. P_InitPicAnims: bad cycle from %s to %s Īn error occurred while determining the number of frames in an animated flat or texture. This error should never occur.Īn inconsistency has occurred while building the sector line pointer tables. This error should never occur.Ī pickup item the player has collected has tried to give an invalid ammo type. P_CrossSubsector: ss %i with numss = %i Ī line of sight check has indexed into the subsector array out of bounds. This error can easily be triggered by allowing the player to activate too many lifts at once, or by starting too many perpetual lifts during the course of a level. Too many platform actions are active at one time. Simulation errors P_AddActivePlat: no more plats! 10.12 W_ReadLump: only read %i of %i on lump %i.10.5 Wad file %s doesn't have IWAD or PWAD id.6.3 P_UnarchiveSpecials: Unknown tclass %i in savegame. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |