Hitscan - Revision history

Sangman: Bit more explanation (probably a bit too much heh) on hitwall/hitsprite

2020-11-17T22:43:44Z

Bit more explanation (probably a bit too much heh) on hitwall/hitsprite

← Older revision		Revision as of 15:43, 17 November 2020
Line 4:		Line 4:

	All parameters are [[gamevar \| gamevars]]. The first three are the coordinates from which the hitscan occurs, followed by the scanning sector. The [[cos]], then the [[sin]] of an angle (typically the [[ang]] of the actor performing the scan) come next, followed by the z angle, which must be calculated before the hitscan. The six return gamevars hold the values of what the hitscan hits. The value of [[clipmask]] tells hitscan which sorts of things it can hit. A [[clipmask]] of 4294901808 is useful for most purposes.		All parameters are [[gamevar \| gamevars]]. The first three are the coordinates from which the hitscan occurs, followed by the scanning sector. The [[cos]], then the [[sin]] of an angle (typically the [[ang]] of the actor performing the scan) come next, followed by the z angle, which must be calculated before the hitscan. The six return gamevars hold the values of what the hitscan hits. The value of [[clipmask]] tells hitscan which sorts of things it can hit. A [[clipmask]] of 4294901808 is useful for most purposes.

			HITWALL and HITSPRITE's default value is -1. They will be filled up with the wall id or sprite id that is hit. In other words, if running hitscan against an actor and HITWALL's value is not -1, that means the target actor is not hit. If it is hit, HITSPRITE will be set to the id of the actor.

	Example of hitscan originating from the player:		Example of hitscan originating from the player:

Sangman: some text changes

2020-11-17T22:39:51Z

some text changes

← Older revision		Revision as of 15:39, 17 November 2020
Line 5:		Line 5:
	All parameters are [[gamevar \| gamevars]]. The first three are the coordinates from which the hitscan occurs, followed by the scanning sector. The [[cos]], then the [[sin]] of an angle (typically the [[ang]] of the actor performing the scan) come next, followed by the z angle, which must be calculated before the hitscan. The six return gamevars hold the values of what the hitscan hits. The value of [[clipmask]] tells hitscan which sorts of things it can hit. A [[clipmask]] of 4294901808 is useful for most purposes.		All parameters are [[gamevar \| gamevars]]. The first three are the coordinates from which the hitscan occurs, followed by the scanning sector. The [[cos]], then the [[sin]] of an angle (typically the [[ang]] of the actor performing the scan) come next, followed by the z angle, which must be calculated before the hitscan. The six return gamevars hold the values of what the hitscan hits. The value of [[clipmask]] tells hitscan which sorts of things it can hit. A [[clipmask]] of 4294901808 is useful for most purposes.

	Example of hitscan:		Example of hitscan originating from the player:
	<pre>		<pre>
	// This state will return the sector, wall, and sprite(id, x ,y, and z data)currently under the crosshair.		// This state will return the sector, wall, and sprite(id, x ,y, and z data)currently under the crosshair.
Line 25:		Line 25:
	</pre>		</pre>

	If the hitscan ~~is between two actors~~, the code is a bit different:		If the hitscan does not originate from the player but from another actor, the code is a bit different:
	* Ensure the hitscan cstat bit is set on the target actor		* Ensure the hitscan cstat bit is set on the target actor
	* The angle needs to be calculated		* The angle needs to be calculated

Sangman: unordered list fix

2020-11-17T22:39:03Z

unordered list fix

← Older revision		Revision as of 15:39, 17 November 2020
Line 26:		Line 26:

	If the hitscan is between two actors, the code is a bit different:		If the hitscan is between two actors, the code is a bit different:
	- Ensure the hitscan cstat bit is set on the target actor		* Ensure the hitscan cstat bit is set on the target actor
	- The angle needs to be calculated		* The angle needs to be calculated
	- The zdist calculation is different		* The zdist calculation is different
	- If appropriate, the "my_z" coordinate needs to be shifted up to the "eye level" of the actor. You should be able to get away with using a constant value around 4096-8192 for most cases, but it depends on the exact height of the actor.		* If appropriate, the "my_z" coordinate needs to be shifted up to the "eye level" of the actor. You should be able to get away with using a constant value around 4096-8192 for most cases, but it depends on the exact height of the actor.
	<pre>		<pre>
	state checkhitscan		state checkhitscan

Sangman: Description of hitscan between two actors

2020-11-17T22:36:30Z

Description of hitscan between two actors

@@ Line 22: / Line 22: @@
 	hitscan MY_X MY_Y MY_Z MY_SECTOR MY_COS MY_SIN MY_ZDIST HITSECTOR HITWALL HITSPRITE HITX HITY HITZ 4294901808
 ends
 </pre>

TX: Reverted edits by Ularedmond (talk) to last revision by One

2011-09-23T13:03:46Z

Reverted edits by Ularedmond (talk) to last revision by One

← Older revision		Revision as of 06:03, 23 September 2011
Line 27:		Line 27:
	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
	[[Category:Gamevar manipulation]]		[[Category:Gamevar manipulation]]
	~~[http://essaywritingservices.org/index.php essay writing services]~~

Spammer at 11:08, 23 September 2011

2011-09-23T11:08:46Z

← Older revision		Revision as of 04:08, 23 September 2011
Line 27:		Line 27:
	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
	[[Category:Gamevar manipulation]]		[[Category:Gamevar manipulation]]
			[http://essaywritingservices.org/index.php essay writing services]

One at 19:40, 4 May 2009

2009-05-04T19:40:16Z

← Older revision		Revision as of 12:40, 4 May 2009
Line 1:		Line 1:
	hitscan <x1> <y1> <z1> <sect1> <cos of ang> <sin of ang> <zvel> <hit sector return var> <hit wall return var> <hit sprite return var> <hit x return var> <hit y return var> <hit z return var> <clip mask>		'''hitscan''' <x1> <y1> <z1> <sect1> <cos of ang> <sin of ang> <zvel> <hit sector return var> <hit wall return var> <hit sprite return var> <hit x return var> <hit y return var> <hit z return var> <clip mask>

	Hitscan returns the values of what would be hit if one travelled in a straight line from a set of coordinates in a specified direction.		Hitscan returns the values of what would be hit if one travelled in a straight line from a set of coordinates in a specified direction.

66.97.115.134 at 07:26, 7 January 2009

2009-01-07T07:26:25Z

← Older revision		Revision as of 00:26, 7 January 2009
Line 7:		Line 7:
	Example of hitscan:		Example of hitscan:
	<pre>		<pre>
	// This state will return the sector, wall, and sprite(id,x,y, and z data)currently under the crosshair.		// This state will return the sector, wall, and sprite(id, x ,y, and z data)currently under the crosshair.

	state checkhitscan		state checkhitscan

66.97.115.134 at 07:26, 7 January 2009

2009-01-07T07:26:07Z

← Older revision		Revision as of 00:26, 7 January 2009
Line 7:		Line 7:
	Example of hitscan:		Example of hitscan:
	<pre>		<pre>
			// This state will return the sector, wall, and sprite(id,x,y, and z data)currently under the crosshair.

	state checkhitscan		state checkhitscan
	getplayer[THISACTOR].posx MY_X		getplayer[THISACTOR].posx MY_X

66.97.115.134 at 06:38, 7 January 2009

2009-01-07T06:38:38Z

@@ Line 4: / Line 4: @@
 All parameters are [[gamevar | gamevars]].  The first three are the coordinates from which the hitscan occurs, followed by the scanning sector.  The [[cos]], then the [[sin]] of an angle (typically the [[ang]] of the actor performing the scan) come next, followed by the z angle, which must be calculated before the hitscan.  The six return gamevars hold the values of what the hitscan hits.  The value of [[clipmask]] tells hitscan which sorts of things it can hit.  A [[clipmask]] of 4294901808 is useful for most purposes.
 [[Category:EDuke32 specific commands]]
 [[Category:Gamevar manipulation]]