Known Bugs - Revision history

75338: /* Interceptions: Last Shot Always Misses */ fixed

2024-04-23T22:14:34Z

Interceptions: Last Shot Always Misses: fixed

← Older revision		Revision as of 22:14, 23 April 2024
Line 76:		Line 76:

	=== Interceptions: Last Shot Always Misses ===		=== Interceptions: Last Shot Always Misses ===
			NOTE: This has been fixed in OpenXCom.

	When using Cautious attack when [[UFO Interception\|intercepting a UFO]], your craft will stay at the maximum range of your longest-range weapon. When using Standard attack, your craft will stay at the maximum range of your shortest-range weapon. (Usually players use two weapons of the same type, so Cautious and Standard attack will behave the same in this regard.)		When using Cautious attack when [[UFO Interception\|intercepting a UFO]], your craft will stay at the maximum range of your longest-range weapon. When using Standard attack, your craft will stay at the maximum range of your shortest-range weapon. (Usually players use two weapons of the same type, so Cautious and Standard attack will behave the same in this regard.)

PocketUFOPlayer? at 15:26, 29 January 2020

2020-01-29T15:26:55Z

← Older revision		Revision as of 15:26, 29 January 2020
Line 191:		Line 191:
	Due to a bug in the way this tileset was created, when you shoot the ground, it doesn't burn up - it turns into a tree stump.		Due to a bug in the way this tileset was created, when you shoot the ground, it doesn't burn up - it turns into a tree stump.

	Because the stump is on object, as opposed to actual ground, any objects that were in the tile already (for example, UFO hulls or the landing gear of your craft) get replaced by these stumps, making it seem as if they were destroyed.		Because the stump is an object, as opposed to actual ground, any objects that were in the tile already (for example, UFO hulls or the landing gear of your craft) get replaced by these stumps, making it seem as if they were destroyed.

	Tree stumps don't take much damage, so they often get burnt up immediately if an explosive goes off, leaving nothing but burnt ground behind. It is easier to view the effects of this bug by shooting the ground instead.		Tree stumps don't take much damage, so they often get burnt up immediately if an explosive goes off, leaving nothing but burnt ground behind. It is easier to view the effects of this bug by shooting the ground instead.

NKF: /* Hangar Split in Half */ Added example

2018-08-06T06:39:45Z

Hangar Split in Half: Added example

← Older revision		Revision as of 06:39, 6 August 2018
Line 40:		Line 40:
	===Hangar Split in Half===		===Hangar Split in Half===
	In the DOS version of UFO, it's possible to place the top-left section of a hangar in the rightmost column or bottommost row of the base map, hanging it off the edge of the map. In the case of a hangar placed in the rightmost column, the "right" half of the hangar will appear on the leftmost column, shifted one row down. This is due to the game storing the base map as a 1-dimensional string of values. The hangar will still function normally, but unless both halves of the hangar are connected to the rest of the base it could make a Base Defence mission unwinnable.		In the DOS version of UFO, it's possible to place the top-left section of a hangar in the rightmost column or bottommost row of the base map, hanging it off the edge of the map. In the case of a hangar placed in the rightmost column, the "right" half of the hangar will appear on the leftmost column, shifted one row down. This is due to the game storing the base map as a 1-dimensional string of values. The hangar will still function normally, but unless both halves of the hangar are connected to the rest of the base it could make a Base Defence mission unwinnable.

			{{UBK\|=
			\|dirt\|dirt\|hangar1\|hangar2\|dirt\|dirt\|=
			\|dirt\|dirt\|hangar3\|hangar4\|dirt\|dirt\|=
			\|dirt\|dirt\|lift\|stores\|dirt\|dirt\|=
			\|dirt\|dirt\|quarters\|large_radar\|workshop\|hangar1\|=
			\|hangar2\|dirt\|quarters\|lab\|dirt\|hangar3\|=
			\|hangar4\|dirt\|dirt\|dirt\|dirt\|dirt\|=}}

	In the case of a hangar hanging off the bottommost row, the "hanging" segments will overflow into other parts of memory. There is an exploit related to this.		In the case of a hangar hanging off the bottommost row, the "hanging" segments will overflow into other parts of memory. There is an exploit related to this.

Magic9mushroom: /* Hanger Split in Half */ lots of spelling errors in the previous version, and a bit of confusion

2018-07-04T01:51:56Z

Hanger Split in Half: lots of spelling errors in the previous version, and a bit of confusion

← Older revision		Revision as of 01:51, 4 July 2018
Line 38:		Line 38:
	This bug allows you to "upgrade in place", for example building a new Hyper-Wave Decoder over the top of an existing Large Radar, and retaining the detection capability of the Large Radar until the Hyper-Wave Decoder completes building. (Unless something else completes building first).		This bug allows you to "upgrade in place", for example building a new Hyper-Wave Decoder over the top of an existing Large Radar, and retaining the detection capability of the Large Radar until the Hyper-Wave Decoder completes building. (Unless something else completes building first).

	===~~Hanger~~ Split in Half===		===Hangar Split in Half===
	~~This happens if~~ the ~~hanger is placed on~~ the ~~6th~~ row in the base ~~construction screen~~. ~~It wont break battlescape combat but may make certain battles unwinnable if an alien is trapped~~ in ~~an isolated chunk~~. This is ~~caused by~~ the game ~~calculating~~ the base ~~sheet~~ as a 1 ~~demensional~~ string of ~~entries~~. ~~See [http://www~~.~~strategycore~~.~~co.uk/forums/topic/11491-hangar-split-in-half/~~ this ~~thread] for more info~~. ~~Does not effect the CE version~~ or TFTD.		In the DOS version of UFO, it's possible to place the top-left section of a hangar in the rightmost column or bottommost row of the base map, hanging it off the edge of the map. In the case of a hangar placed in the rightmost column, the "right" half of the hangar will appear on the leftmost column, shifted one row down. This is due to the game storing the base map as a 1-dimensional string of values. The hangar will still function normally, but unless both halves of the hangar are connected to the rest of the base it could make a Base Defence mission unwinnable.

			In the case of a hangar hanging off the bottommost row, the "hanging" segments will overflow into other parts of memory. There is an exploit related to this.

			This bug doesn't affect Collector's Edition or TFTD, as you will receive a "cannot build here" warning if you attempt to place a hangar in an invalid position.

	===Fixes for Base Construction Bugs===		===Fixes for Base Construction Bugs===

3371-Alpha: /* Base Construction Bugs */

2018-07-03T17:22:15Z

Base Construction Bugs

← Older revision		Revision as of 17:22, 3 July 2018
Line 37:		Line 37:

	This bug allows you to "upgrade in place", for example building a new Hyper-Wave Decoder over the top of an existing Large Radar, and retaining the detection capability of the Large Radar until the Hyper-Wave Decoder completes building. (Unless something else completes building first).		This bug allows you to "upgrade in place", for example building a new Hyper-Wave Decoder over the top of an existing Large Radar, and retaining the detection capability of the Large Radar until the Hyper-Wave Decoder completes building. (Unless something else completes building first).

			===Hanger Split in Half===
			This happens if the hanger is placed on the 6th row in the base construction screen. It wont break battlescape combat but may make certain battles unwinnable if an alien is trapped in an isolated chunk. This is caused by the game calculating the base sheet as a 1 demensional string of entries. See [http://www.strategycore.co.uk/forums/topic/11491-hangar-split-in-half/ this thread] for more info. Does not effect the CE version or TFTD.

	===Fixes for Base Construction Bugs===		===Fixes for Base Construction Bugs===

3371-Alpha: /* Other Bugs */

2018-03-21T02:05:08Z

Other Bugs

← Older revision		Revision as of 02:05, 21 March 2018
Line 495:		Line 495:
	Noticed this in EU CE version, but probably it happens in every other, probably in TFTD too. If, for any case, you have graphs data for months you did not play yet, you will see numbers like 10240, 163780 etc. next to the vertical axis, and graphs will be totally garbled.		Noticed this in EU CE version, but probably it happens in every other, probably in TFTD too. If, for any case, you have graphs data for months you did not play yet, you will see numbers like 10240, 163780 etc. next to the vertical axis, and graphs will be totally garbled.
	This can be fixed by hex-editing [[ALIEN.DAT]], [[XCOM.DAT]] and [[UIGLOB.DAT]] -- just fill the 'future' with zeros.		This can be fixed by hex-editing [[ALIEN.DAT]], [[XCOM.DAT]] and [[UIGLOB.DAT]] -- just fill the 'future' with zeros.

			=== [[Game Files\|Resource File]] Bugs ===

			There are several issues with both UFO and TFTD's resource files. These are far too numerous to list unfortunately. The [http://www.strategycore.co.uk/files/combo-x-com-game-folder-patch/ Game Folder Combo Patch] for UFO and [http://www.strategycore.co.uk/files/tftd-uso-routes-fix/ USO Routes Fix] and [http://www.strategycore.co.uk/files/tftd-interception-screen-fix/ Interception Screen Fix] for TFTD resolve these issues. [[User:Sherlock\|Sherlock]] also has some additional fixes available.

	=== Saving and Loading Oddities ===		=== Saving and Loading Oddities ===

3371-Alpha: /* Saving and Loading Oddities */

2018-02-21T01:11:04Z

Saving and Loading Oddities

← Older revision		Revision as of 01:11, 21 February 2018
Line 500:		Line 500:
	It is possible to load an empty save game slot. Doing so will place the player at the beginning stages of the X-COM campaign however their base will be nowhere to be found on the globe. Sending an air craft out of the base will reveal it to be in the just off the coast of Africa. This is due to the game normally asking you to pick your first base location, however loading an empty save slot bypasses the routine causing the base to simply be placed on the globe's first "graph point" which happens to be off the coast of Africa. Actually attempting to play the bugged campaign will end in failure as, although things can be purchased, sold, researched, ect. like usual, your base does not exist as far an the game's engine is concerned. Any aircraft sent from the base cannot return to it, forcing the game into a stand still once you finish a battlescape mission. This bug does not affect [[TFTD]] as selecting an empty save simply dumps you back to the previous screen, regardless of whether that's the current game or the main menu.		It is possible to load an empty save game slot. Doing so will place the player at the beginning stages of the X-COM campaign however their base will be nowhere to be found on the globe. Sending an air craft out of the base will reveal it to be in the just off the coast of Africa. This is due to the game normally asking you to pick your first base location, however loading an empty save slot bypasses the routine causing the base to simply be placed on the globe's first "graph point" which happens to be off the coast of Africa. Actually attempting to play the bugged campaign will end in failure as, although things can be purchased, sold, researched, ect. like usual, your base does not exist as far an the game's engine is concerned. Any aircraft sent from the base cannot return to it, forcing the game into a stand still once you finish a battlescape mission. This bug does not affect [[TFTD]] as selecting an empty save simply dumps you back to the previous screen, regardless of whether that's the current game or the main menu.

	Similarly, if you create a new base then select it in the bases menu and then immediately reload to a previous save prior to building it and open the bases menu again you will be greeted with a base screen full of [[Access ~~lift~~\|Access ~~lifts~~]]. If you look at the base selection bar at the top you will notice the slot the the new base once occupied will be currently selected, though oddly empty. This is caused by the game not actively resetting the "selected base" variable unless the geoscape is restarted (either by quitting or entering a battlescape mission). Access Lifts fill the empty base due to the game not being designed to display a completely empty base grid and because they are the "default" base module type, being the first one that's always built upon creating a new base. Unlike the previous, this bug is a harmless visual anomaly. Simply selecting one of the filled base slots returns everything to normal.		Similarly, if you create a new base then select it in the bases menu and then immediately reload to a previous save prior to building it and open the bases menu again you will be greeted with a base screen full of [[Access Lift\|Access Lifts]]. If you look at the base selection bar at the top you will notice the slot the the new base once occupied will be currently selected, though oddly empty. This is caused by the game not actively resetting the "selected base" variable unless the geoscape is restarted (either by quitting or entering a battlescape mission). Access Lifts fill the empty base due to the game not being designed to display a completely empty base grid and because they are the "default" base module type, being the first one that's always built upon creating a new base. Unlike the previous, this bug is a harmless visual anomaly. Simply selecting one of the filled base slots returns everything to normal.

	==Utility bugs==		==Utility bugs==

3371-Alpha: /* Saving and Loading Oddities */

2018-02-21T01:10:01Z

Saving and Loading Oddities

← Older revision		Revision as of 01:10, 21 February 2018
Line 498:		Line 498:
	=== Saving and Loading Oddities ===		=== Saving and Loading Oddities ===

	It is possible to load an empty save game slot. Doing so will place the player at the beginning stages of the X-COM campaign however their base will be nowhere to be found on the globe. Sending an air craft out of the base will reveal it to be in the ~~middle~~ of ~~the Atlantic ocean~~. This is due to the game normally asking you to pick your first base location, however loading an empty save slot bypasses the routine causing the base to simply be placed on the globe's first "graph point" which happens to be in the ~~middle~~ of the ~~atlantic~~.		It is possible to load an empty save game slot. Doing so will place the player at the beginning stages of the X-COM campaign however their base will be nowhere to be found on the globe. Sending an air craft out of the base will reveal it to be in the just off the coast of Africa. This is due to the game normally asking you to pick your first base location, however loading an empty save slot bypasses the routine causing the base to simply be placed on the globe's first "graph point" which happens to be off the coast of Africa. Actually attempting to play the bugged campaign will end in failure as, although things can be purchased, sold, researched, ect. like usual, your base does not exist as far an the game's engine is concerned. Any aircraft sent from the base cannot return to it, forcing the game into a stand still once you finish a battlescape mission. This bug does not affect [[TFTD]] as selecting an empty save simply dumps you back to the previous screen, regardless of whether that's the current game or the main menu.

	Similarly, if you create a new base then select it in the bases menu and then immediately reload to a previous save prior to building it and open the bases menu again you will be greeted with a base screen full of [[Access lift\|Access lifts]]. If you look at the base selection bar at the top you will notice the slot the the new base once occupied will be currently selected, though oddly empty. This is caused by the game not actively resetting the "selected base" variable unless the geoscape is restarted (either by quitting or entering a battlescape mission). Access Lifts fill the empty base due to the game not being designed to display a completely empty base grid and because they are the "default" base module type, being the first one that's always built upon creating a new base.		Similarly, if you create a new base then select it in the bases menu and then immediately reload to a previous save prior to building it and open the bases menu again you will be greeted with a base screen full of [[Access lift\|Access lifts]]. If you look at the base selection bar at the top you will notice the slot the the new base once occupied will be currently selected, though oddly empty. This is caused by the game not actively resetting the "selected base" variable unless the geoscape is restarted (either by quitting or entering a battlescape mission). Access Lifts fill the empty base due to the game not being designed to display a completely empty base grid and because they are the "default" base module type, being the first one that's always built upon creating a new base. Unlike the previous, this bug is a harmless visual anomaly. Simply selecting one of the filled base slots returns everything to normal.

	==Utility bugs==		==Utility bugs==

3371-Alpha: /* Other Bugs */

2018-02-21T00:49:01Z

Other Bugs

← Older revision		Revision as of 00:49, 21 February 2018
Line 495:		Line 495:
	Noticed this in EU CE version, but probably it happens in every other, probably in TFTD too. If, for any case, you have graphs data for months you did not play yet, you will see numbers like 10240, 163780 etc. next to the vertical axis, and graphs will be totally garbled.		Noticed this in EU CE version, but probably it happens in every other, probably in TFTD too. If, for any case, you have graphs data for months you did not play yet, you will see numbers like 10240, 163780 etc. next to the vertical axis, and graphs will be totally garbled.
	This can be fixed by hex-editing [[ALIEN.DAT]], [[XCOM.DAT]] and [[UIGLOB.DAT]] -- just fill the 'future' with zeros.		This can be fixed by hex-editing [[ALIEN.DAT]], [[XCOM.DAT]] and [[UIGLOB.DAT]] -- just fill the 'future' with zeros.

			=== Saving and Loading Oddities ===

			It is possible to load an empty save game slot. Doing so will place the player at the beginning stages of the X-COM campaign however their base will be nowhere to be found on the globe. Sending an air craft out of the base will reveal it to be in the middle of the Atlantic ocean. This is due to the game normally asking you to pick your first base location, however loading an empty save slot bypasses the routine causing the base to simply be placed on the globe's first "graph point" which happens to be in the middle of the atlantic.

			Similarly, if you create a new base then select it in the bases menu and then immediately reload to a previous save prior to building it and open the bases menu again you will be greeted with a base screen full of [[Access lift\|Access lifts]]. If you look at the base selection bar at the top you will notice the slot the the new base once occupied will be currently selected, though oddly empty. This is caused by the game not actively resetting the "selected base" variable unless the geoscape is restarted (either by quitting or entering a battlescape mission). Access Lifts fill the empty base due to the game not being designed to display a completely empty base grid and because they are the "default" base module type, being the first one that's always built upon creating a new base.

	==Utility bugs==		==Utility bugs==

Binkyuk: /* Cash Rollover Bug */ Yes, unsigned arithmetic was possible in the early 90s...

2016-04-27T12:25:45Z

Cash Rollover Bug: Yes, unsigned arithmetic was possible in the early 90s...

← Older revision		Revision as of 12:25, 27 April 2016
Line 89:		Line 89:
	When your cash balance goes over $2,147,483,647, it will rollover and become $-2,147,483,647. Which means your game is done for, unless you use an editor. Fortunately, by the time you accumulate this much cash, you have usually completed all necessary research to win the game.		When your cash balance goes over $2,147,483,647, it will rollover and become $-2,147,483,647. Which means your game is done for, unless you use an editor. Fortunately, by the time you accumulate this much cash, you have usually completed all necessary research to win the game.

	''When the game was written, the largest unit that a programmer had available was ~~a DWORD~~. The programmers did not make this unsigned ~~(if that was possible back in the early '90s)~~ so the largest amount that could be stored is ~~7FFFFFFh~~, which is 2147483647.''~~[[User:Morgan525\|Tycho~~]~~] ([[User talk:Morgan525\|talk]])~~		''When the game was written, the largest unit that a programmer had available was 32-bits. The programmers did not make this unsigned so the largest amount that could be stored is 2 ^ 31 - 1, which is 2147483647. Incrementing this causes it to overflow to a negative number due to [https://en.wikipedia.org/wiki/Two's_complement Two's complement arithmetic]''

	== Battlescape Bugs ==		== Battlescape Bugs ==