Tutorial - Beam Weapons - Revision history

EatThePath: correction about beam damage math

2020-11-27T03:12:09Z

correction about beam damage math

← Older revision		Revision as of 03:12, 27 November 2020
Line 35:		Line 35:
	$Subsystem Factor: 1.0</pre>		$Subsystem Factor: 1.0</pre>

	When creating beam weapons, it is very important to notice that the defined damage is continuous. To get damage caused per second, you must multiply this value by 5.5. Also to get full damage potential of the beam, you have to first multiply the damage with the 5.5 and then with the beam life value. Other values are used as with other weapons to determine damage multipliers against hulls, shields and subsystems.		When creating beam weapons, it is very important to notice that the defined damage is continuous. To get damage caused per second, you must multiply this value by 5.88. Also to get full damage potential of the beam, you have to first multiply the damage with the 5.88 and then with the beam life value. Other values are used as with other weapons to determine damage multipliers against hulls, shields and subsystems.

			5.88 is an appropriation, but a close enough one for any reasonable needs. If you're curious, the exact factor is 100/17, amounting to one 'pulse' of damage every 170 milliseconds. You may see find or receive information saying 5.5 instead, which was once a more useful number due to engine flaws that have since been fixed.

	<pre>$Lifetime: 60.0		<pre>$Lifetime: 60.0

TopAce: Reverted edits by JayBradley (Talk) to last revision by Asterpth

2011-12-01T08:07:07Z

Reverted edits by JayBradley (Talk) to last revision by Asterpth

← Older revision	Revision as of 08:07, 1 December 2011
(No difference)

Asterpth: /* Setting Basic Values */

2011-02-11T20:28:26Z

Setting Basic Values

← Older revision		Revision as of 20:28, 11 February 2011
Line 16:		Line 16:
	@Laser Tail Radius: 0.60</pre>		@Laser Tail Radius: 0.60</pre>

	~~Only~~ '''$Name:''' is ~~used~~. ~~The others are not used with~~ beam ~~weapons~~.		'''$Name:''' is obviously the name of the weapon, this is the name you will be giving FRED for weapons.

			'''@Laser Color''' affects the color that the beam lights up surrounding objects when it fires.

	<pre>$Mass: 100.0		<pre>$Mass: 100.0

Asterpth at 04:26, 11 February 2011

2011-02-11T04:26:46Z

← Older revision		Revision as of 04:26, 11 February 2011
Line 1:		Line 1:
	~~{{grammar}}~~

	This is a short tutorial detailing the exact functions of various parameters for Beam weapons in [[Weapons.tbl]]. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].		This is a short tutorial detailing the exact functions of various parameters for Beam weapons in [[Weapons.tbl]]. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].

Asterpth at 04:26, 11 February 2011

2011-02-11T04:26:32Z

← Older revision		Revision as of 04:26, 11 February 2011
Line 1:		Line 1:
	{{grammar}}		{{grammar}}

	This is a short tutorial ~~about~~ the ~~making~~ of ~~beam~~ weapons. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].		This is a short tutorial detailing the exact functions of various parameters for Beam weapons in [[Weapons.tbl]]. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].

	'''Please post any comments or questions concerning the beam weapons tutorial in the [[Talk:Tutorial_-_Beam_Weapon\|Discussion Page]]'''.		'''Please post any comments or questions concerning the beam weapons tutorial in the [[Talk:Tutorial_-_Beam_Weapon\|Discussion Page]]'''.
Line 117:		Line 117:

	===Type 3 Beams===		===Type 3 Beams===
	Type 3 beams are also known as anti-fighter beams and unlike other beam types, they have different ~~behaviours~~ depending on the type of its target. Against small targets, or more precisely against targets defined with certain [[Objecttypes.tbl#$Beams_Easily_Hit:\|Objecttypes.tbl]] options, they fire a number of short beam pulses (defined with [[Weapons.tbl#$BeamInfo:\|+Shots:]] that have their total combined lifetime equal to the defined lifetime of the beam. Against larger targets, they behave exactly like Type 0 beams. In both cases the beam uses '''+Miss Factor:''' values for its accuracy. Type 3 beams do not function as fighter beams.		Type 3 beams are also known as anti-fighter beams and unlike other beam types, they have different behaviors depending on the type of its target. Against small targets, or more precisely against targets defined with certain [[Objecttypes.tbl#$Beams_Easily_Hit:\|Objecttypes.tbl]] options, they fire a number of short beam pulses (defined with [[Weapons.tbl#$BeamInfo:\|+Shots:]] that have their total combined lifetime equal to the defined lifetime of the beam. Against larger targets, they behave exactly like Type 0 beams. In both cases the beam uses '''+Miss Factor:''' values for its accuracy. Type 3 beams do not function as fighter beams.

	[[AAAf]] and [[SAAA]] are such beams.		[[AAAf]] and [[SAAA]] are such beams.
Line 145:		Line 145:
	==Adjusting Beam Textures==		==Adjusting Beam Textures==

	Beam textures are - by default - used in game by stretching the single bitmap over the whole length of the beam. It is worthwhile to notice that if beam hits anything, its drawing length is limited to the distance from the firing point to the impact point. This may cause very erratic beam texture ~~behaviour~~ if the used bitmap was not uniform. Animations (both .ani and .eff) can be used instead normal bitmaps for beams textures.		Beam textures are - by default - used in game by stretching the single bitmap over the whole length of the beam. It is worthwhile to notice that if beam hits anything, its drawing length is limited to the distance from the firing point to the impact point. This may cause very erratic beam texture behavior if the used bitmap was not uniform. Animations (both .ani and .eff) can be used instead normal bitmaps for beams textures.

	===Adjusting Tile Length===		===Adjusting Tile Length===

Aquila7: Grammatical correction

2010-07-24T16:12:17Z

Grammatical correction

← Older revision		Revision as of 16:12, 24 July 2010
Line 1:		Line 1:
	{{grammar}}		{{grammar}}

	This is a short tutorial about making of beam weapons. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].		This is a short tutorial about the making of beam weapons. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].

	'''Please post any comments or questions concerning the beam weapons tutorial in the [[Talk:Tutorial_-_Beam_Weapon\|Discussion Page]]'''.		'''Please post any comments or questions concerning the beam weapons tutorial in the [[Talk:Tutorial_-_Beam_Weapon\|Discussion Page]]'''.
Line 34:		Line 34:
	$Subsystem Factor: 1.0</pre>		$Subsystem Factor: 1.0</pre>

	When creating beam weapons, it is very important to notice that the defined damage is continuous. To get damage caused per second, you must multiply this value by 5.5. Also to get full damage potential of the beam, you have to first multiply the damage with the 5.5 and then with the beam life value. Other values are used as with other weapons to determine damage multipliers against ~~hull~~, ~~shield~~ and subsystems.		When creating beam weapons, it is very important to notice that the defined damage is continuous. To get damage caused per second, you must multiply this value by 5.5. Also to get full damage potential of the beam, you have to first multiply the damage with the 5.5 and then with the beam life value. Other values are used as with other weapons to determine damage multipliers against hulls, shields and subsystems.

	<pre>$Lifetime: 60.0		<pre>$Lifetime: 60.0

TopAce at 13:02, 26 July 2009

2009-07-26T13:02:16Z

← Older revision		Revision as of 13:02, 26 July 2009
Line 93:		Line 93:
	==Different Beam Types==		==Different Beam Types==

	Beam types in [[~~FSSCP Introduction\|~~FreeSpace Open]] are clearly different from each other. Understanding their differences and unique features is useful for all tablers.		Beam types in [[FreeSpace Open]] are clearly different from each other. Understanding their differences and unique features is useful for all tablers.

SypheDMar at 23:26, 1 February 2009

2009-02-01T23:26:49Z

← Older revision		Revision as of 23:26, 1 February 2009
Line 1:		Line 1:
	{{grammar}}		{{grammar}}

	This is a short tutorial ~~into~~ making of beam weapons. Some knowledge on table editing is useful ~~and~~ as is basic understanding of [[Weapons.tbl]].		This is a short tutorial about making of beam weapons. Some knowledge on table editing is useful as well as having a basic understanding of [[Weapons.tbl]].

	'''Please post any comments or questions concerning the beam weapons tutorial to the [[Talk:Tutorial_-_Beam_Weapon\|~~talk page~~]]'''		'''Please post any comments or questions concerning the beam weapons tutorial in the [[Talk:Tutorial_-_Beam_Weapon\|Discussion Page]]'''.
	<br><br>		<br><br>
	==Making a Basic Beam Weapon==		==Making a Basic Beam Weapon==
Line 17:		Line 17:
	@Laser Tail Radius: 0.60</pre>		@Laser Tail Radius: 0.60</pre>

	Only ~~actually meaningful of these arguments is the~~ '''$Name:'''. ~~Others~~ are not used with beam weapons.		Only '''$Name:''' is used. The others are not used with beam weapons.

	<pre>$Mass: 100.0		<pre>$Mass: 100.0
Line 25:		Line 25:
	'''$Mass:''' value is used with beams to define the force with which it pulls (negative value) or pushes (positive value) the target. Setting to zero prevents 'beam whacking'.		'''$Mass:''' value is used with beams to define the force with which it pulls (negative value) or pushes (positive value) the target. Setting to zero prevents 'beam whacking'.

	'''$Velocity:''' value is ~~not as important with beam weapons as it is with other weapons as it is only~~ used for determining targeting range and also, for certain beam types, its accuracy.		'''$Velocity:''' value is used for determining targeting range and also, for certain beam types, its accuracy.

	'''$Fire Wait:''' value set the delay between individual beam firings~~. This is~~ in seconds.		'''$Fire Wait:''' value set the delay between individual beam firings in seconds.

	<pre>$Damage: 5		<pre>$Damage: 5
Line 133:		Line 133:
	===Beam Targeting Ranges===		===Beam Targeting Ranges===

	Generally speaking, beams target ~~any legal - that is,~~ anything not protected by other weapon settings such as 'huge' ~~- target~~ within the set [[Weapons.tbl#.2BWeapon_Range:\|weapon range]]. However, this range can be defined by using [[Weapons.tbl#.2BWeapon Range:\|+Weapon Range:]] and [[Weapons.tbl#.2BWeapon Min Range:\|+Weapon Min Range:]] for setting the maximum and minimum targeting ranges, respectively. It should be also noted that beams do use the range calculated for other weapons as well (''lifetime x velocity'') despite the fact they actually do not need these values for anything else. If the ''lifetime x velocity'' is smaller than the set ''weapon range'' then beam uses the ''lifetime x velocity'' for determining its maximum range. The AI uses this range for determining when to fire the beam weapon.		Generally speaking, beams target anything not protected by other weapon settings such as 'huge' within the set [[Weapons.tbl#.2BWeapon_Range:\|weapon range]]. However, this range can be defined by using [[Weapons.tbl#.2BWeapon Range:\|+Weapon Range:]] and [[Weapons.tbl#.2BWeapon Min Range:\|+Weapon Min Range:]] for setting the maximum and minimum targeting ranges, respectively. It should be also noted that beams do use the range calculated for other weapons as well (''lifetime x velocity'') despite the fact they actually do not need these values for anything else. If the ''lifetime x velocity'' is smaller than the set ''weapon range'' then beam uses the ''lifetime x velocity'' for determining its maximum range. The AI uses this range for determining when to fire the beam weapon.

	===Actual Beam Range===		===Actual Beam Range===
Line 141:		Line 141:
	===Beam Accuracy===		===Beam Accuracy===

	Normally, beam accuracy is determined by '''+Miss Factor:''' values that uses set accuracy values for each difficulty level. Higher values increase the chance of beams missing their targets. However, direct-fire beams (Type 2 or Type 4 beams as fighter beams and Type 4 beams in multi-part turrets) use ~~normal targeting 'rules'. That is they use~~ the weapon velocity, target velocity and range for calculating lead for the target. As beams are ~~instantenous~~, this causes the beams to miss their targets or rather AI to fire its beam to a point exactly in front of the target.		Normally, beam accuracy is determined by '''+Miss Factor:''' values that uses set accuracy values for each difficulty level. Higher values increase the chance of beams missing their targets. However, direct-fire beams (Type 2 or Type 4 beams as fighter beams and Type 4 beams in multi-part turrets) use the weapon velocity, target velocity, and range for calculating lead for the target. As beams are instantaneous, this causes the beams to miss their targets or rather AI to fire its beam to a point exactly in front of the target.

	==Adjusting Beam Textures==		==Adjusting Beam Textures==

TopAce: Spelling and some other alterations. Still needs a native speaker, so it gets {{grammar}}

2009-01-09T21:20:06Z

Spelling and some other alterations. Still needs a native speaker, so it gets {{grammar}}

Show changes

Wanderer: fixed errors

2007-02-08T17:36:26Z

fixed errors

← Older revision		Revision as of 17:36, 8 February 2007
Line 151:		Line 151:
	===Adjusting Tile Length===		===Adjusting Tile Length===

	Instead of letting the game stretch the bitmap over the whole length of the beam the tiling of the beam texture can be adjusted with two different methods. To use these methods for adjusting beam texture tiling we have to use '''+Tile Factor:''' option under the beam section that is to be modified. Tile factor requires two arguments of which the ~~first~~ one (either 0 or 1) will determine the actual texture tiling method.		Instead of letting the game stretch the bitmap over the whole length of the beam the tiling of the beam texture can be adjusted with two different methods. To use these methods for adjusting beam texture tiling we have to use '''+Tile Factor:''' option under the beam section that is to be modified. Tile factor requires two arguments of which the second one (either 0 or 1) will determine the actual texture tiling method.
	<br><br>		<br><br>
	'''Tiling Method '0''''		'''Tiling Method '0''''

	Method '0' sets the beam texture to be tiled in similar way as the default method but with one difference. You can define how many times the texture tile is used in beam - default option is the same as '''+Tile Factor: 0~~, 1~~'''. However stretching is again possible issue.		Method '0' sets the beam texture to be tiled in similar way as the default method but with one difference. You can define how many times the texture tile is used in beam - default option is the same as '''+Tile Factor: 1, 0'''. However stretching is again possible issue.
	<br><br>		<br><br>
	'''Tiling Method '1''''		'''Tiling Method '1''''

	Using method '1' for setting the beam texture tiling allows us to use the ~~second~~ value to define the length of the beam tiles used in the beam texture. So when using this method the number of tiles shown on screen does depends on the length of the beam and stretching issues shouldn't as visible at all.		Using method '1' for setting the beam texture tiling allows us to use the first value to define the length of the beam tiles used in the beam texture. So when using this method the number of tiles shown on screen does depends on the length of the beam and stretching issues shouldn't as visible at all.
	<br><br>		<br><br>
	===Setting Beam Translation Values===		===Setting Beam Translation Values===