diff --git a/Notes/README.md b/Notes/README.md new file mode 100644 index 0000000..07d62ac --- /dev/null +++ b/Notes/README.md @@ -0,0 +1,76 @@ +# Notes: + +Intuiting PI + +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 jet infront and and to the right by 45 degrees we yaw? + +Imagine 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 | +____________________________________________ + +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? + + +If in rotate towards + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Notes/intuiting-pi.jpg b/Notes/intuiting-pi.jpg new file mode 100644 index 0000000..6e2c8ce Binary files /dev/null and b/Notes/intuiting-pi.jpg differ diff --git a/Notes/intuiting-pi.jpg.import b/Notes/intuiting-pi.jpg.import new file mode 100644 index 0000000..c1fed36 --- /dev/null +++ b/Notes/intuiting-pi.jpg.import @@ -0,0 +1,40 @@ +[remap] + +importer="texture" +type="CompressedTexture2D" +uid="uid://bspcgiktdy8at" +path="res://.godot/imported/intuiting-pi.jpg-a72b97b3ff84526851df55b10614055f.ctex" +metadata={ +"vram_texture": false +} + +[deps] + +source_file="res://Notes/intuiting-pi.jpg" +dest_files=["res://.godot/imported/intuiting-pi.jpg-a72b97b3ff84526851df55b10614055f.ctex"] + +[params] + +compress/mode=0 +compress/high_quality=false +compress/lossy_quality=0.7 +compress/uastc_level=0 +compress/rdo_quality_loss=0.0 +compress/hdr_compression=1 +compress/normal_map=0 +compress/channel_pack=0 +mipmaps/generate=false +mipmaps/limit=-1 +roughness/mode=0 +roughness/src_normal="" +process/channel_remap/red=0 +process/channel_remap/green=1 +process/channel_remap/blue=2 +process/channel_remap/alpha=3 +process/fix_alpha_border=true +process/premult_alpha=false +process/normal_map_invert_y=false +process/hdr_as_srgb=false +process/hdr_clamp_exposure=false +process/size_limit=0 +detect_3d/compress_to=1