Ukikipedia

Flying: Difference between revisions

Page Discussion

Flying (view source)

Revision as of 16:37, 2 August 2024

1,411 bytes added ,  2 August 2024
→‎update_flying: explain best flying
(make it screenshottable)
(→‎update_flying: explain best flying)
 
(2 intermediate revisions by the same user not shown)
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 below table)
# Pitch velocity affects pitch.
# Pitch is clamped to be inside [-0x2AAA, 0x2AAA]
# x,y,z velocity is more or less directly exactly trigonometrically 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 98: Line 107:
}
}
</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).
* 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.
** 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'''
{| class="wikitable"
{| class="wikitable"
|+forwardVel's affect in pitch
|+forwardVel's affect on pitch
|'''<=4'''
|'''<=4'''
|5
|5
Line 123: Line 139:
|33
|33
|-
|-
| -400
| -1024
| -270
| -270
| -260
| -260
Line 144: Line 160:
|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.
* In summary:
# Joystick inputs affect (pitch,yaw) velocity.
# Yaw velocity affects yaw, roll, and forward velocity.
# Pitch affects forward velocity.
# Forward velocity affects pitch.
# Pitch velocity affects pitch.
# 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.
Line 165: Line 172:
|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 194:
|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><syntaxhighlight lang="c">
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">
/**
/**
  * 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
251

edits

Retrieved from "https://ukikipedia.net/wiki/Special:MobileDiff/18804...19368"