You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is interesting to note that the combination of the world position vector and rotation quaternion would populate a translation+rotation matrix quite nicely...
The text was updated successfully, but these errors were encountered:
Ch7 - Capturing and processing flight telemetry
Summary of changes
Added UI menu sounds
Get planets spinning again with mesh.rotate (resolves Planets do not rotate as they orbit #66)
Modify base launch force and launcher rotation speeds for gameplay purposes
Adds a customized sun particle set along with textures and JSON definition (Star should have occasional flares and activity #71 )
CargoUnit now keeps track of its in-flight telemetry
added feature: encounter zones (see this PG ) (Generating the route #70)
Added encounter zone manager to provide game logic with info on which zone the unit is currently passing through (resolves Generating the route #70)
EncounterZones signal encounters via an Observable
gameData definitions for encounters within their respective zones (see Flight path encounter tables #65, Generating the route #70)
GUI displays encounters with their respective images along with sound feedback
Pause now correctly halts progress of the cargo unit while in flight (resolves Pause does not halt cargo unit physics #60)
getting route data
Route data is obtained by sampling the CargoUnit's position at intervals while the
isInFlight
flag is set. Data captured in each sample includes:It is interesting to note that the combination of the world position vector and rotation quaternion would populate a translation+rotation matrix quite nicely...
The text was updated successfully, but these errors were encountered: