Flying - Revision history

Icecream17: typo + practical advice (double check this)

2026-06-11T18:31:04Z

typo + practical advice (double check this)

← Older revision		Revision as of 18:31, 11 June 2026
Line 12:		Line 12:
	\|related=		\|related=
	}}		}}
	Flying is an action that can ~~occurs~~ when Mario triple jumps or does a cannon shot while wearing the [[wing cap]].		Flying is an action that can occur when Mario triple jumps or does a cannon shot while wearing the [[wing cap]].

			Fast downward movements followed by slow upward movements is generally better than flying in a straight line.
	== Entering flying ==		== Entering flying ==
	* [[Shot From Cannon\|Cannon shot]]: when y vel < 0 (and Mario does not cancel) ('''Action argument: 0''')		* [[Shot From Cannon\|Cannon shot]]: when y vel < 0 (and Mario does not cancel) ('''Action argument: 0''')

Icecream17: /* update_flying */ typo

2025-08-19T16:42:45Z

update_flying: typo

← Older revision		Revision as of 16:42, 19 August 2025
Line 215:		Line 215:
	#* In further contrast, holding less of the same direction changes the angle by 32 (yaw) or 64 (pitch)		#* In further contrast, holding less of the same direction changes the angle by 32 (yaw) or 64 (pitch)
	#* In even furthest contrast, holding more of the same direction changes the angle by 16 (yaw) or 32 (pitch)		#* In even furthest contrast, holding more of the same direction changes the angle by 16 (yaw) or 32 (pitch)
	#* So it might be faster to say, modify pitch:as such: -56 to -4 to 60 instead of -56 to 8 to 40. Notice the slightly under zero instead of slightly over zero.		#* So it might be faster to say, modify pitch as such: -56 to -4 to 60 instead of -56 to 8 to 40. Notice the slightly under zero instead of slightly over zero.

	After that, update_flying_yaw does:		After that, update_flying_yaw does:

Icecream17: /* update_flying */ explain best flying

2024-08-02T16:37:44Z

update_flying: explain best flying

← Older revision		Revision as of 16:37, 2 August 2024
Line 63:		Line 63:
	# Pitch affects forward velocity.		# Pitch affects forward velocity.
	# Forward velocity becomes at least 0		# Forward velocity becomes at least 0
	# Forward velocity affects pitch (see ~~above~~ table)		# Forward velocity affects pitch (see below table)
	# Pitch velocity affects pitch.		# Pitch velocity affects pitch.
	# Pitch is clamped to be inside [-0x2AAA, 0x2AAA]		# Pitch is clamped to be inside [-0x2AAA, 0x2AAA]
	# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.		# x,y,z velocity is more or less directly exactly trigonometrically correspondent to forward velocity, pitch, and yaw.
	# xz sliding velocity updated to correspond		# xz sliding velocity updated to correspond
	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">
Line 108:		Line 108:
	</syntaxhighlight>		</syntaxhighlight>
	'''Key takeaways''':		'''Key takeaways''':
			* Pitch velocity ''additively'' affects forward velocity, but ''sin'' effects pitch. '''The most energy efficient flying is to fly a lot down, and then a little up''', as, for example, sin(-0.5) + sin(0.25) + sin(0.25) ≈ 0.0153823799048 (positive), while the totally additive effect is still 0 (actually -0.3 because of a flat -0.1 per trame)
	* Pitching to move up happens faster with higher forward velocity.		* Pitching to move up happens faster with higher forward velocity.
	** The difference between 4 and 5 speed, and 16 and 17 speed is especially large.		** The difference between 4 and 5 speed, and 16 and 17 speed is especially large.

Icecream17: cleanup

2024-07-06T20:05:12Z

cleanup

← Older revision		Revision as of 20:05, 6 July 2024
Line 56:		Line 56:
	Notice that there is no code handling air steps for ledge grabbing or hanging on a ceiling, so such transitions are impossible.		Notice that there is no code handling air steps for ledge grabbing or hanging on a ceiling, so such transitions are impossible.
	===update_flying===		===update_flying===
	Casually, tilt the joystick left to move left, right to move right, up to move down, down to move up.		Casually, tilt the joystick left to move left, right to move right, up to move down, down to move up. '''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.

	~~I am too lazy to describe~~ the ~~exact details of~~ <code>update_flying</code>, ~~so here~~ is ~~the code~~		Beyond this, the pseudocode is provided but probably isn't as useful as the <code>update_flying</code> code itself:
			# Joystick inputs affect (pitch,yaw) velocity.
			# Yaw velocity affects yaw, roll, and forward velocity.
			# Pitch affects forward velocity.
			# Forward velocity becomes at least 0
			# Forward velocity affects pitch (see above table)
			# Pitch velocity affects pitch.
			# Pitch is clamped to be inside [-0x2AAA, 0x2AAA]
			# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.
			# xz sliding velocity updated to correspond
	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">
	void update_flying(struct MarioState *m) {		void update_flying(struct MarioState *m) {
Line 106:		Line 115:
	* Pitch has a minimum and maximum and cannot overflow with standard speeds.		* Pitch has a minimum and maximum and cannot overflow with standard speeds.
	* '''More below the tables'''		* '''More below the tables'''
	* '''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.
	{\| class="wikitable"		{\| class="wikitable"
	\|+forwardVel's affect on pitch		\|+forwardVel's affect on pitch
Line 151:		Line 159:
	\|6		\|6
	\|}		\|}
	*'''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.
	~~Although I posted the code instead of the detailed psuedocode, here's some less detailed psuedocode anyways:~~

	~~Although I was too lazy, I typed a less detailed pseudocode anyways:~~
	~~# Joystick inputs affect (pitch,yaw) velocity.~~
	~~# Yaw velocity affects yaw, roll, and forward velocity.~~
	~~# Pitch affects forward velocity.~~
	~~# Forward velocity becomes at least 0~~
	~~# Forward velocity affects pitch (see above table)~~
	~~# Pitch velocity affects pitch.~~
	~~# Pitch is clamped to be inside [-0x2AAA, 0x2AAA]~~
	~~# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.~~
	~~# xz sliding velocity updated to correspond~~
	<hr>		<hr>
	Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.		Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.
Line 224:		Line 219:
	#Add yaw velocity to yaw		#Add yaw velocity to yaw
	# Set roll to yaw times negative twenty (-20)		# Set roll to yaw times negative twenty (-20)
	'''Note that turning left = positive yaw''' (up = positive pitch).<ref>https://youtu.be/TQt8MCsniQI</ref>		'''Note that turning left = positive yaw''' (up = positive pitch).<ref>https://youtu.be/TQt8MCsniQI</ref><syntaxhighlight lang="c">

	*
	<syntaxhighlight lang="c">
	/**		/**
	* Return the value 'current' after it tries to approach target, going up at		* Return the value 'current' after it tries to approach target, going up at

Icecream17: fix misinformation

2023-12-19T23:25:05Z

fix misinformation

← Older revision		Revision as of 23:25, 19 December 2023
Line 98:		Line 98:
	}		}
	</syntaxhighlight>		</syntaxhighlight>
	Key takeaways:		'''Key takeaways''':
	* Pitching to move up happens faster with ~~lower~~ forward velocity. ~~Try to be just under~~ 4 or 16 forward velocity (~~since those are~~ the ~~cutoffs~~).		* Pitching to move up happens faster with higher forward velocity.
			** The difference between 4 and 5 speed, and 16 and 17 speed is especially large.
			* At the same time, forward velocity is based on pitch. (But it is also based on:)
			** There is a base 0.1 forwardVel speed loss
			** There is anywhere from 0 to 0.5 further speed loss - more speed is lost the higher the yaw velocity is (ie '''the more Mario turns''').
			* Pitch has a minimum and maximum and cannot overflow with standard speeds.
			* '''More below the tables'''
			* '''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.
	{\| class="wikitable"		{\| class="wikitable"
	\|+forwardVel's affect in pitch		\|+forwardVel's affect on pitch
	\|'''<=4'''		\|'''<=4'''
	\|5		\|5
Line 123:		Line 130:
	\|33		\|33
	\|-		\|-
	\| -~~400~~		\| -1024
	\| -270		\| -270
	\| -260		\| -260
Line 144:		Line 151:
	\|6		\|6
	\|}		\|}
	* However, the pitch is capped to within +- 0x2AAA (in decimal: 10922)		*'''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.
	* '''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.		Although I posted the code instead of the detailed psuedocode, here's some less detailed psuedocode anyways:
	* In summary:
			Although I was too lazy, I typed a less detailed pseudocode anyways:
	# Joystick inputs affect (pitch,yaw) velocity.		# Joystick inputs affect (pitch,yaw) velocity.
	# Yaw velocity affects yaw, roll, and forward velocity.		# Yaw velocity affects yaw, roll, and forward velocity.
	# Pitch affects forward velocity.		# Pitch affects forward velocity.
	# Forward velocity affects pitch.		# Forward velocity becomes at least 0
			# Forward velocity affects pitch (see above table)
	# Pitch velocity affects pitch.		# Pitch velocity affects pitch.
			# Pitch is clamped to be inside [-0x2AAA, 0x2AAA]
	# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.		# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.
			# xz sliding velocity updated to correspond
	<hr>		<hr>
	Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.		Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.
Line 165:		Line 176:
	\|negative pitch velocity		\|negative pitch velocity
	\|add 64 vel, cap at 32		\|add 64 vel, cap at 32
	\| approach (at most 40 up or 20 down)		\| approach (at most 64 up or 32 down)
	\|approach 0 (by at most 40)		\|approach 0 (by at most 64)
	\|-		\|-
	\|positive pitch velocity		\|positive pitch velocity
	\| approach (at most 20 down ~~or 40 up~~)		\| approach (at most 32 up or 64 down)
	\|subtract 64 vel, cap at -32		\|subtract 64 vel, cap at -32
	\|approach 0 (by at most 40)		\|approach 0 (by at most 64)
	\|-		\|-
	\|zero pitch velocity		\|zero pitch velocity
	\| approach (at most 20 down ~~or 40 up~~)		\| approach (at most 32 up or 64 down)
	\| approach (at most 40 up or 20 down)		\| approach (at most 64 up or 32 down)
	\| approach 0 (by at most 40)		\| approach 0 (by at most 64)
	\|}		\|}
	{\| class="wikitable"		{\| class="wikitable"
Line 187:		Line 198:
	\|negative yaw velocity		\|negative yaw velocity
	\| add 64 vel, cap at 16		\| add 64 vel, cap at 16
	\|approach (at most 20 up or 10 down)		\|approach (at most 32 up or 16 down)
	\|approach 0 (by at most 40)		\|approach 0 (by at most 64)
	\|-		\|-
	\|positive yaw velocity		\|positive yaw velocity
	\| approach (at most 10 up or 20 down)		\| approach (at most 16 up or 32 down)
	\| subtract 64 vel, cap at -16		\| subtract 64 vel, cap at -16
	\|approach 0 (by at most 40)		\|approach 0 (by at most 64)
	\|-		\|-
	\|zero yaw velocity		\|zero yaw velocity
	\|approach (at most 10 up or 20 down)		\|approach (at most 16 up or 32 down)
	\|approach (at most 20 up or 10 down)		\|approach (at most 32 up or 16 down)
	\|approach 0 (by at most 40)		\|approach 0 (by at most 64)
	\|}		\|}
			'''Key takeaways''':

			# Many joystick positions are equivalent.
			# One cannot change velocity by more than 64 (ignoring the effects of speed)
			# Holding joystick x=0 or y=0 will approach the corresponding 0 by at most 64.
			#* In contrast, holding the opposite direction changes the angle by 32 (yaw) or 64 (pitch), unconditionally
			#* In further contrast, holding less of the same direction changes the angle by 32 (yaw) or 64 (pitch)
			#* In even furthest contrast, holding more of the same direction changes the angle by 16 (yaw) or 32 (pitch)
			#* So it might be faster to say, modify pitch:as such: -56 to -4 to 60 instead of -56 to 8 to 40. Notice the slightly under zero instead of slightly over zero.

	After that, update_flying_yaw does:		After that, update_flying_yaw does:
	#Add yaw velocity to yaw		#Add yaw velocity to yaw
	# Set roll to yaw times negative twenty (-20)		# Set roll to yaw times negative twenty (-20)
	'''Note that turning left = positive yaw''' (up = positive pitch).<ref>https://youtu.be/TQt8MCsniQI</ref>		'''Note that turning left = positive yaw''' (up = positive pitch).<ref>https://youtu.be/TQt8MCsniQI</ref>
	~~As can be seen, many joystick positions will be equivalent, and the pitch velocity or yaw velocity change by at most 40.~~
	*		*
	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">

Icecream17: make it screenshottable

2023-12-19T18:20:58Z

make it screenshottable

← Older revision		Revision as of 18:20, 19 December 2023
Line 99:		Line 99:
	</syntaxhighlight>		</syntaxhighlight>
	Key takeaways:		Key takeaways:
	* Pitching to move up happens faster with lower forward velocity. Try to be just under 4 or 16 forward velocity.		* Pitching to move up happens faster with lower forward velocity. Try to be just under 4 or 16 forward velocity (since those are the cutoffs).
	{\| class="wikitable"		{\| class="wikitable"
	\|+forwardVel's affect in pitch		\|+forwardVel's affect in pitch

Icecream17: /* Behavior */ clarify

2023-08-04T02:02:41Z

Behavior: clarify

← Older revision		Revision as of 02:02, 4 August 2023
Line 37:		Line 37:
	### Set action state to 1		### Set action state to 1
	# Call '''<code>update_flying</code>'''		# Call '''<code>update_flying</code>'''
	# switch [[Movement_steps#Perform_Air_Step]]: (Note: ~~perform air step is significant because it~~ '''adds vel[0,1,2] to pos[0,1,2]'''.)		# switch [[Movement_steps#Perform_Air_Step]]: (Note: if there are no floor/wall/ceiling/oob interactions this just '''adds vel[0,1,2] to pos[0,1,2]'''.)
	#* air step none:		#* air step none:
	#*# Update graphics (camera) angle to be behind Mario		#*# Update graphics (camera) angle to be behind Mario
Line 99:		Line 99:
	</syntaxhighlight>		</syntaxhighlight>
	Key takeaways:		Key takeaways:

	* Pitching to move up happens faster with lower forward velocity. Try to be just under 4 or 16 forward velocity.		* Pitching to move up happens faster with lower forward velocity. Try to be just under 4 or 16 forward velocity.

	{\| class="wikitable"		{\| class="wikitable"
	\|+forwardVel's affect in pitch		\|+forwardVel's affect in pitch
Line 146:		Line 144:
	\|6		\|6
	\|}		\|}

	* However, the pitch is capped to within +- 0x2AAA (in decimal: 10922)		* However, the pitch is capped to within +- 0x2AAA (in decimal: 10922)
	* '''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.		* '''TODO:''' I heard moving down then up can be faster then just the direct line. Explain big picture movements, what happens in a practical example.
	* In summary:		* In summary:

	# Joystick inputs affect (pitch,yaw) velocity.		# Joystick inputs affect (pitch,yaw) velocity.
	# Yaw velocity affects yaw, roll, and forward velocity.		# Yaw velocity affects yaw, roll, and forward velocity.
Line 157:		Line 153:
	# Pitch velocity affects pitch.		# Pitch velocity affects pitch.
	# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.		# x,y,z velocity is more or less directly exactly correspondent to forward velocity, pitch, and yaw.

	<hr>		<hr>

	Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.		Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.
	{\| class="wikitable"		{\| class="wikitable"

Icecream17: /* Behavior */ expand

2023-08-04T00:08:52Z

Behavior: expand

@@ Line 22: / Line 22: @@
 As with all airborne actions, a variety of "cancels" are checked prior to actually performing any airborne action. See [[Jump#Airborne cancels]].
-Then:
+Then:<ref>https://github.com/n64decomp/sm64/blob/66018e9f3caaa67399218971d61366cb3f7ba7d7/src/game/mario_actions_airborne.c#L1726</ref>
 # If Z is pressed
 ## If Mario's camera mode is CAMERA_MODE_BEHIND_MARIO, set_camera_mode to m->area->camera->defMode
@@ Line 37: / Line 37: @@
 ### Set action state to 1
 # Call '''<code>update_flying</code>'''
-# switch [[Movement_steps#Perform_Air_Step]]:
+# switch [[Movement_steps#Perform_Air_Step]]: (Note: perform air step is significant because it '''adds vel[0,1,2] to pos[0,1,2]'''.)
 #* air step none:
 #*# Update graphics (camera) angle to be behind Mario
@@ Line 56: / Line 56: @@
 Notice that there is no code handling air steps for ledge grabbing or hanging on a ceiling, so such transitions are impossible.
 ===update_flying===
 I am too lazy to describe the exact details of <code>update_flying</code>, so here is the code
 <syntaxhighlight lang="c">
@@ Line 96: / Line 98: @@
+}
 </syntaxhighlight>
 Here are some tables summarizing the <code>approach_s32</code>, <code>update_flying_pitch</code>, and <code>update_flying_yaw</code> functions.
 {| class="wikitable"

Icecream17: this code is so indirect

2023-08-03T20:51:35Z

this code is so indirect

Show changes

Icecream17 at 22:25, 1 August 2023

2023-08-01T22:25:58Z

← Older revision		Revision as of 22:25, 1 August 2023
Line 54:		Line 54:
	#*# stop holding, stop riding, [[Lava Boost]]		#*# stop holding, stop riding, [[Lava Boost]]
	# finally, play the flying sound (adjust sound for speed)		# finally, play the flying sound (adjust sound for speed)
			Notice that there is no code handling air steps for ledge grabbing or hanging on a ceiling, so such transitions are impossible.

	I am too lazy to describe the exact details of <code>update_flying</code>, so here is the code		I am too lazy to describe the exact details of <code>update_flying</code>, so here is the code
	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">