Craft Combat Mechanics - Revision history

Alpha Centauri Bear: /* Alternative closing speed observations */

2020-10-18T21:24:23Z

Alternative closing speed observations

← Older revision		Revision as of 21:24, 18 October 2020
Line 156:		Line 156:


	==== Alternative closing speed observations ====		=== Alternative closing speed observations ===

	Tested in OpenXcom UFO and TFTD.		Tested in OpenXcom UFO and TFTD.
Line 172:		Line 172:
	I have also independently computed estimated interceptor damage based on this closing time and enemy weapon power and fire rate. Results closely match to experimental observation when I use my approaching speed and they are noticeably off when I try to use Spike's numbers. So I have to conclude my speed is correct.		I have also independently computed estimated interceptor damage based on this closing time and enemy weapon power and fire rate. Results closely match to experimental observation when I use my approaching speed and they are noticeably off when I try to use Spike's numbers. So I have to conclude my speed is correct.

	===== Note from Meridian =====		==== Note from Meridian ====

	As meridian pointed out here, original XCom assumes UFOpaedia "second" to be equal two game ticks. Whereas OpenXcom assumes it to be equal one game tick. Hence the difference in calculated results.		As meridian pointed out here, original XCom assumes UFOpaedia "second" to be equal two game ticks. Whereas OpenXcom assumes it to be equal one game tick. Hence the difference in calculated results.

Alpha Centauri Bear: /* Alternative closing speed observations */

2020-10-18T21:23:57Z

Alternative closing speed observations

← Older revision		Revision as of 21:23, 18 October 2020
Line 158:		Line 158:
	==== Alternative closing speed observations ====		==== Alternative closing speed observations ====

	Tested ~~both~~ UFO and TFTD.		Tested in OpenXcom UFO and TFTD.

	Equipped interceptor with Stingray missiles and Cannon to set an exact visible and audible approaching range range. It is audible because when interceptor approaches to Cannon fire range it starts firing noticeably loud.		Equipped interceptor with Stingray missiles and Cannon to set an exact visible and audible approaching range range. It is audible because when interceptor approaches to Cannon fire range it starts firing noticeably loud.
Line 171:		Line 171:

	I have also independently computed estimated interceptor damage based on this closing time and enemy weapon power and fire rate. Results closely match to experimental observation when I use my approaching speed and they are noticeably off when I try to use Spike's numbers. So I have to conclude my speed is correct.		I have also independently computed estimated interceptor damage based on this closing time and enemy weapon power and fire rate. Results closely match to experimental observation when I use my approaching speed and they are noticeably off when I try to use Spike's numbers. So I have to conclude my speed is correct.

			===== Note from Meridian =====

			As meridian pointed out here, original XCom assumes UFOpaedia "second" to be equal two game ticks. Whereas OpenXcom assumes it to be equal one game tick. Hence the difference in calculated results.
			https://openxcom.org/forum/index.php/topic,8661.msg133010.html#msg133010

Alpha Centauri Bear: /* Closing Range */

2020-10-18T17:40:40Z

Closing Range

← Older revision		Revision as of 17:40, 18 October 2020
Line 156:		Line 156:


			==== Alternative closing speed observations ====

			Tested both UFO and TFTD.

			Equipped interceptor with Stingray missiles and Cannon to set an exact visible and audible approaching range range. It is audible because when interceptor approaches to Cannon fire range it starts firing noticeably loud.
			Set missile: range = 60, damage = 0, reload time = 10 (for all modes to not mess up with my observations), number of shots = enough to not run out of missiles with that frequent shooting.
			Set cannon: range = 10

			This way I can clearly count number of missile shots when interceptor closes distance from 60 to 10 km = 50 km.

			I did about 5 observations an in all of them I can count 20 missile shots. Sometimes maybe last shot was done a split second after cannon start firing. So probably 19.8 - 20 shots. That gives us 50 km / (20 shots * 10 s) = 0.25 km /s.

			I have tried different reload times just to make sure I don't miscount number of shots and to see how big error I get. In all cases the 50 km closing time was around 200 s, give or take half a shot. I have also tested this in TFTD and got same results. This is about twice as slow comparing to previous author.

			I have also independently computed estimated interceptor damage based on this closing time and enemy weapon power and fire rate. Results closely match to experimental observation when I use my approaching speed and they are noticeably off when I try to use Spike's numbers. So I have to conclude my speed is correct.


			{{REVISIONUSER}}

	=== Control of Range ===		=== Control of Range ===

Medinoc: /* Accuracy Mechanics */

2015-06-22T20:25:32Z

Accuracy Mechanics

← Older revision		Revision as of 20:25, 22 June 2015
Line 106:		Line 106:
	[1+(3/UFOsize)]/2 * Weapon Accuracy		[1+(3/UFOsize)]/2 * Weapon Accuracy

	In other words, for a typical Medium (size=3) target, the adjusted accuracy is equal to the base unadjusted weapon accuracy.		With the UFOsize value going down as UFOs get bigger. In other words, for a typical Medium (size=3) target, the adjusted accuracy is equal to the base unadjusted weapon accuracy.

	[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] to alter X-Com attack accuracy based on a seperate difficulty rating specified in the INI and target size.		[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] to alter X-Com attack accuracy based on a seperate difficulty rating specified in the INI and target size.

Hobbes: categorizing

2013-07-23T02:55:54Z

categorizing

← Older revision		Revision as of 02:55, 23 July 2013
Line 280:		Line 280:
	* found offsets for Craft Weapons - see [[Talk:GEOSCAPE.EXE#TFTD_Sub_weapon_stats]]		* found offsets for Craft Weapons - see [[Talk:GEOSCAPE.EXE#TFTD_Sub_weapon_stats]]
	** also need to locate USO stats / Sub stats		** also need to locate USO stats / Sub stats

			[[Category:Enemy Unknown/UFO Defense]]

Morgan525: /* General Notes */

2012-10-03T05:42:35Z

General Notes

← Older revision		Revision as of 05:42, 3 October 2012
Line 188:		Line 188:

	UFOs are capable of attempting to hold range, to close, and to break off, just like XCom aircraft. The behaviour is not well understood but appears in part to be influenced by the Attack mode of the XCom craft. Of course, initiating an attack often has an effect on this behaviour (e.g. the UFO attempts to break off).		UFOs are capable of attempting to hold range, to close, and to break off, just like XCom aircraft. The behaviour is not well understood but appears in part to be influenced by the Attack mode of the XCom craft. Of course, initiating an attack often has an effect on this behaviour (e.g. the UFO attempts to break off).
			:''UFOs are incapable of holding range or closing on their own initative. The player's choice of attack mode is the only factor that determines range. The only independent action a UFO can take is escape if the UFO is faster than the Xcraft and its escape timer has reached zero.'' [[User:Morgan525\|Tycho]]

	== UFO Rate of Fire Mechanics ==		== UFO Rate of Fire Mechanics ==

Morgan525: /* Control of Range */

2012-10-03T05:38:54Z

Control of Range

← Older revision		Revision as of 05:38, 3 October 2012
Line 169:		Line 169:
	Question: do UFOs attempt to hold an advantageous stand off range, as XCom craft do in Cautious and Standard attack modes?		Question: do UFOs attempt to hold an advantageous stand off range, as XCom craft do in Cautious and Standard attack modes?

	''No. The interception routine is strictly one-sided ~~in favor of~~ the ~~player~~.''[[User:Morgan525\|Tycho]] 06:46, 3 July 2012 (EDT)		''No. The interception routine is strictly one-sided. The player chooses the range and when to attack. The UFO only responds if the Xcrafts comes into its weapon's range.''[[User:Morgan525\|Tycho]] 06:46, 3 July 2012 (EDT)

	Question: Do UFOs use Attack modes in the same way that XCom craft do, and if so, what are the effects?		Question: Do UFOs use Attack modes in the same way that XCom craft do, and if so, what are the effects?

	''No. ~~The player controls when and how~~ to ~~attack. The UFO simply responds if~~ the ~~Xcraft reaches it~~'s ~~weapon range. The UFO will only disengage if its escape timer reaches zero and its maximum speed is greater than the Xcraft~~.'' [[User:Morgan525\|Tycho]] 06:46, 3 July 2012 (EDT)		''No. UFOs fire rate is based on an internal timer, which is reduced according to the game's difficulty level. '' [[User:Morgan525\|Tycho]] 06:46, 3 July 2012 (EDT)

	=== Standoff Is Independent of Range ===		=== Standoff Is Independent of Range ===

Morgan525: /* Accuracy Mechanics */

2012-10-03T05:34:40Z

Accuracy Mechanics

← Older revision		Revision as of 05:34, 3 October 2012
Line 108:		Line 108:
	In other words, for a typical Medium (size=3) target, the adjusted accuracy is equal to the base unadjusted weapon accuracy.		In other words, for a typical Medium (size=3) target, the adjusted accuracy is equal to the base unadjusted weapon accuracy.

	[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] to alter X-Com attack accuracy based on ~~game~~ difficulty ~~level~~ and target size.		[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] to alter X-Com attack accuracy based on a seperate difficulty rating specified in the INI and target size.
	~~:''Actually, Interception has an independent difficulty setting in the INI.[[User:Morgan525\|Tycho]]''~~

	== Range ==		== Range ==

Spike: /* Empirical Data */ copy of same typo

2012-09-26T21:01:55Z

Empirical Data: copy of same typo

← Older revision		Revision as of 21:01, 26 September 2012
Line 261:		Line 261:
	Gas 1 1 1		Gas 1 1 1
	Ajax 16 12 8		Ajax 16 12 8
	DUP 24 16 12		DUP 24 18 12
	Gauss 6 6 6		Gauss 6 6 6
	Sonic 6 6 6		Sonic 6 6 6

Morgan525: /* UFO Accuracy Mechanics */

2012-09-25T03:01:04Z

UFO Accuracy Mechanics

← Older revision		Revision as of 03:01, 25 September 2012
Line 225:		Line 225:
	:This could be translated to C as " if(GetRandom_0_n(100) <= 40) { return; } ", for the most part. What this does is skip all of the damage and destruction code if that GetRandom_0_n call rolls 0 through 40, for 41 values, out of 101 total possibilities. I am fairly certain that I recall UFOs missing frequently, as well. --[[User:Xusilak\|Xusilak]] 15:36, 11 April 2010 (EDT)		:This could be translated to C as " if(GetRandom_0_n(100) <= 40) { return; } ", for the most part. What this does is skip all of the damage and destruction code if that GetRandom_0_n call rolls 0 through 40, for 41 values, out of 101 total possibilities. I am fairly certain that I recall UFOs missing frequently, as well. --[[User:Xusilak\|Xusilak]] 15:36, 11 April 2010 (EDT)

	UFOs have a flat 60% accuracy which is not affected by game difficulty, UFO size, or Xcraft attack stance. [[User:Morgan525\|~~Morgan525~~]] 06:50, 3 July 2012 (EDT)		UFOs have a flat 60% accuracy which is not affected by game difficulty, UFO size, or Xcraft attack stance. [[User:Morgan525\|Tycho]] 06:50, 3 July 2012 (EDT)

	[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] for UFO accuracy to vary with the difficulty level and X-craft attack mode. The difficulty level is independent of game difficulty and selected by the user in the INI.		[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] for UFO accuracy to vary with the difficulty level and X-craft attack mode. The difficulty level is independent of game difficulty and selected by the user in the INI.

← Older revision		Revision as of 03:01, 25 September 2012
Line 225:		Line 225:
	:This could be translated to C as " if(GetRandom_0_n(100) <= 40) { return; } ", for the most part. What this does is skip all of the damage and destruction code if that GetRandom_0_n call rolls 0 through 40, for 41 values, out of 101 total possibilities. I am fairly certain that I recall UFOs missing frequently, as well. --[[User:Xusilak\|Xusilak]] 15:36, 11 April 2010 (EDT)		:This could be translated to C as " if(GetRandom_0_n(100) <= 40) { return; } ", for the most part. What this does is skip all of the damage and destruction code if that GetRandom_0_n call rolls 0 through 40, for 41 values, out of 101 total possibilities. I am fairly certain that I recall UFOs missing frequently, as well. --[[User:Xusilak\|Xusilak]] 15:36, 11 April 2010 (EDT)

	UFOs have a flat 60% accuracy which is not affected by game difficulty, UFO size, or Xcraft attack stance. [[User:Morgan525\|~~Morgan525~~]] 06:50, 3 July 2012 (EDT)		UFOs have a flat 60% accuracy which is not affected by game difficulty, UFO size, or Xcraft attack stance. [[User:Morgan525\|Tycho]] 06:50, 3 July 2012 (EDT)

	[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] for UFO accuracy to vary with the difficulty level and X-craft attack mode. The difficulty level is independent of game difficulty and selected by the user in the INI.		[[UFO Extender]] / [[TFTDextender]] provide an [[User:Morgan525#Functions_used_in_UFOextender.27s_new_interception_routines\|option]] for UFO accuracy to vary with the difficulty level and X-craft attack mode. The difficulty level is independent of game difficulty and selected by the user in the INI.