Files
GrowlerFury/Notes/README.md
T

76 lines
3.3 KiB
Markdown
Raw Normal View History

# Notes:
<img src="intuiting-pi.jpg" alt="Intuiting PI" width="400">
var target_position = jet.to_local(jet.target.global_position)
-- Gets us the position of a target jet relative to the jet itself.
-- This treats the jet as the center of the world when calculating.
var direction = jet.to_local(jet.target.global_position).normalized()
-- I'm uncertain; but, the above might give direction similar to the below strategy but in local space.
var direction = (jet.target.global_position - jet.global_position).normalized()
### Steps to consider when rotating a jet by CPU mode:
-- PI is 180 degrees and 2PI is 360 degrees.
-- Remember pirodicity and how 0 degrees could technically mean +-360 degrees (full circle).
-- If rotation.z is equal to 0 or +-360 it means we're level.
-- Rotating along -z (Forward direction of Godot nodes) means left is -x and right is +x
-- Rotating left (-x) is towards <=360 degrees and +x is towards >=0 degrees rightward.
-- We're upside down If +-270 (or increments of that I.E +- 540, etc).
Can we normalize rotation and from that treat slices of the circle as specific command zones?
I.E if target a jet in front and and to the right by 45 degrees we yaw instead of roll?
2026-11-01 17:33:28 -06:00
Imagining the current situation is us observing our CPU controlled jet from
the 3rd person view from behind. The jet is level to the horizon of our world.
The target jet position is behind and slightly to the right corner of the screen.
____________________________________________
| |
| |
| | |
| -- jet -- |
| | |
| |
| |
| X |
____________________________________________
2026-11-01 17:33:28 -06:00
-- SOHCAHTOA
-- sin = Opposite/Hypotenuse
-- cos = Adjacent/Hypotenuse
-- tan = Opposite/Adjacent
Maybe aha moment, if I create a right angled triangles per plane then we can figure out radians from the aquired angles.
=O ^
We already have a hypotenuse value based on the 'distance'.
We have the target position and our position.
Thus, if certain target values are above or below we use one or the other to gague the 90 degree angle point
let x1 = 5;
let y1 = 5;
let rotation = 8; // in degrees
let magnitude = 7; // our distance
// got bellow from AI during 500 lines challenge; not sure what this is doing just yet
let radians = (rotation + 180) % 360;
const x2 = x1 + magnitude * Math.cos(radians);
const y2 = y1 + magnitude * Math.sin(radians);
We must roll the jet to +90 degrees left or -90 right and then pitch up
in order to turn towards target. OR yaw left or right to turn.
What conditions should we use to determin which to use? Distance from and to?
If shorter distance roll and pitch? If larger then yaw?
We are setting commands on the jet.control_frame. Over time, conditions change; so,
how do we confirm what set of actions to do/maintain? A queue and check over time?
Can we able to get the 'delta' in cpu_controller utside of '_process'/'_physics_process'?
If queue do we push "rotate towards using xyz pattern" as a command/state to check until met?