Pilotwings 64 (the pw64 decompilation, n64decomp/pw64)

In the US version of Pilotwings 64, the gyrocopter's update routine func_8030399C clears a vector (unk31C) and has five routines add terms to it: func_80307A9C, func_80307E2C, func_80308478, func_80307BAC, and func_80307EA8. A routine chosen by state can add to it after them (func_80304B98, for states 1 and 4, does), and func_80309090 copies the result to unk1AC. In state 1 (unkC0), the routine adds unk1AC times the frame time to the craft's velocity (unk190), with no mass dividing it; in state 0 it first combines unk1AC with cross terms of the velocity and the turn rates (unk1B8). func_80307E2C adds (0, 0, −9.8), z being the world's vertical, turned into the craft's frame through the inverse of its matrix (by the atlas's reading, gravity). func_80307A9C adds, on each of the craft's axes, a curve of the square of unk364's component on that axis, signed like the component: 0 at 0, 4.2 at 2661.2188, and 7.56 at 6944.389 and above, linear between (by the atlas's reading, air resistance). Those squares are speeds of about 51.59 and 83.33 (computed). func_80308478 sets unk364 to the vector env_802E1754 returns for the craft's position, in the craft's frame, less the craft's velocity, and adds 0.21 of that vector as a term of its own; by the atlas's reading the vector is the air's velocity and unk364 the airspeed. Below a speed (unk1A8) of 51.587303 the vector is scaled by the square of the speed over 51.587303, and outside state 0 it's taken as zero. The other two routines are in pw64/gyrocopter-lift. pw64/gyrocopter-forces

About: Pilotwings 64 Flight model

Value: 9.8 units per second squared (gravity)

The decompilers name none of these functions or fields. z being the world's vertical rests on the HUD reading the matrix's z translation as height above sea level. unk1A8 is the length of the world velocity, a ground speed, so the curve's knots (on unk364) match a speed readout only in still air; the readout figures are left out for that reason. State 0 is, from func_80305DC0, the state with no ground contact, but the atlas hasn't stated that rule.

Cited by: Flight model, Pilotwings 64

In the US version of Pilotwings 64, two of the terms the gyrocopter's func_8030399C sums give it lift, by the atlas's reading. The one the atlas calls the rotor term (func_80307BAC) is 0.3 times the square of the airspeed's component on the z axis of the matrix unk25C, signed like that component and capped at 200 when positive, times the square of the airspeed's y component over 25, held between 0.05 and 1; it's added along the z axis of the matrix unk21C. The one it calls the engine term (func_80307EA8), while usingFuel is set, is 35 × power (unkB4) × a factor of height (spD8, the atlas's altitude factor), split 0.24 onto y and 0.76 onto z, the z part also times a curve of the negated y airspeed: 0 at 0, 0.15 at 10, 0.4 at 20, 1.2 at 50, and 1.5 at 100 and above. It too goes through unk21C, and its y component is cut to 0.9 when unk1F0 is nonzero, unk190.y is positive, and unk7C is 0. That factor is 1 up to a height of 700 and falls by 0.01 per unit above it, held at 0 from 800 up; that hold is under #if !defined(VERSION_JP), so a Japanese build lets the factor go negative. Neither term applies while unkC1 is set or in state 2 (unkC0). pw64/gyrocopter-lift

About: Pilotwings 64 Flight model

Value: 700 height where engine thrust begins to fade

Neither term is named by the decompilers; "rotor" and "engine" are the atlas's reading (the engine term runs only while fuel is in use, and the rotor term grows with air flowing along the rotor matrix's z axis). That the 0.24 part pushes the craft forward and the 0.76 part up, with lift rising with forward airspeed, is a reading of the axes, not stated in the code. The README lists only the US build as supported, so the Japanese behavior is read from the conditional, not a build.

Cited by: Flight model, Pilotwings 64

In the US version of Pilotwings 64, the gyrocopter's fuel is a number from 0 to 1, starting at the value the task's first start pad holds, or 0 if the task has no start pad (db_getstart). While usingFuel is set, func_80307EA8 takes off each update the frame time times a rate read from a curve of the power (unkB4, the throttle that A raises and B lowers, which the HUD shows as power; in the throttle's case 0 A sets usingFuel, and in cases 1 and 2 A sets it only with fuel above 0): 0.001 at 0, 0.002 at 0.5, and 0.005 at full, linear between. The frame time (D_8034F854) is the time since the last frame held between 0.01 and 0.1, so the rate is per second, and a full tank lasts 200 s at full power and 1,000 s at none (computed). At 0 it clears usingFuel. In a Class B task, each update that func_802E08F4 returns nonzero for the craft's position sets the fuel to 1, and SFX_UI_FUEL_ADDED plays on the first. func_80307EA8 does none of this, refill or drain, while unkC1 is set or in state 2 (unkC0). Separately, the HUD update in code_7CF30.c warns below 0.15 (TEXT_FUEL_WAR) and at 0 (TEXT_FUEL_OUT). pw64/gyrocopter-fuel

About: Pilotwings 64 Fuel gauge

Value: 0.005 tank per second at full power

The 200 s and 1,000 s are 1 divided by the end rates. What func_802E08F4 tests (by its use, a refuelling area) isn't named. The start pad's value is task data from the ROM, so whether a test starts full isn't read.

Cited by: Fuel gauge, Pilotwings 64

In the US version of Pilotwings 64, a thermal is a vertical cylinder from the task's data (TaskTHER): a base position, a radius (scale), and a height. therm_80346C08 sums a vector from each thermal whose cylinder holds the point (by the atlas's reading, its air velocity): its horizontal distance d from the axis at most the radius r, and its height z above the base between 0 and the thermal's height. In therm_80346E04 the vector's vertical part (the atlas's updraft) is the thermal's unk24 × √((r − d)/r), full on the axis and 0 at the edge. Beyond 1 unit from the axis its horizontal part is at right angles to the axis direction, of length unk20 × (1 − 2|r/2 − d|/r) × d, longest halfway out (the atlas's swirl). Both fade in from 0 at the base to full at height unk18, and from unk1C fade out to 0 at the top. env_802E1754 adds the sum to the vector wind_8034D550 gives for the point (by the atlas's reading, the wind), along with, unless the task's unk8 is set, a further wind and a push from beyond 2050 units outside the map's bounds. The hang glider (hangGlider_802F391C) multiplies the total by its pilot's unk2F8: 1.2 for Lark and Kiwi, 1.0 for Goose and Ibis, and 0.8 for Hawk and Robin. pw64/thermal

About: Pilotwings 64 Thermal

{
 "lark": 1.2,
 "goose": 1,
 "hawk": 0.8,
 "kiwi": 1.2,
 "ibis": 1,
 "robin": 0.8
}

"Updraft" and "swirl" are the atlas's reading of the vertical and tangential parts; the decompilers name neither field. Each thermal's strengths and heights are task data from the ROM. The swirl's peak at d = r/2 is computed. How the hang glider's lift uses the air (the rest of hang_glider2.c) isn't read.

Cited by: Pilotwings 64, Thermal

In the US version of Pilotwings 64, the thermals switch off in one test: the hang glider's test with index 0 in the Pilot class (cls 3, CLASS_PILOT). There, from 240 on the clock D_8034F850 (by the decompilers' comment, the current time; the test's setup, gameUpdateStateTestSetup, sets it to 0, and each time func_80313D74 runs it adds the time since the last frame held between 0.01 and 0.1, so it counts seconds of game time), therm_8034695C narrows the drawn cylinders to nothing over the next 10, and at 250 (THERM_DISABLE_TIME) removes the thermals and shows TEXT_THERM_OFF. The narrowing scales only the model's matrix: the updraft reads the task's radius until the thermals are gone. pw64/thermal-cutoff

About: Pilotwings 64 Thermal

Value: 250 seconds

func_80313D74 is called from game.c and a dozen other state updates; the atlas hasn't shown it runs exactly once per frame, so the clock is stated as the sum of its calls. Which test index 0 is in the game's numbering (most likely the class's first) isn't checked against the game. Whether the clock runs while paused isn't read. The radius test in therm_80346C08 and therm_80346E04 read sTaskTHER's scale, not the drawn matrix.

Cited by: Pilotwings 64

The North American instruction booklet for Pilotwings 64 gives the game's copyright to Nintendo and Paradigm Simulation, Inc. (1996); it names no developer as such. pw64/copyright

Cited by: Pilotwings 64

In a recording of the PAL version, Pilotwings 64's ending credits list a "Nintendo Staff" group, directed by Makoto Wada, then a separate "Paradigm Staff" group under project manager Dave Gatchel, and end on "Presented by Nintendo"; the credits never name Nintendo EAD. pw64/credits

A recording of the game is a secondary source here, so the claim is T1; the credits screen itself would be primary. The Nintendo Life article's profile box lists "Nintendo EAD", the only place the scout found that name.

Cited by: Pilotwings 64