Radar Redundancy | RECOIL TECH

who even reads this? the intro says it all.
the final version:
steamcommunity.com/sharedfile...

[@ThisIsDumbAllTheNamesAreTaken]

the person who shared analog memory bits with me: www.youtube.com/@raisininc1887/featured

[@----870]

I remember building a fully autonomous ship with some tracking guns. Nowhere as advanced as this but it did work and managed to win against some people. I wish the Trailmakers devs would add radar or at least make the distance sensors have more range. I'm very hopeful for the future of your creation!

[@paulburmester6572]

Wow. How do you even know how all that logic works. I’m just so amazed! Keep it up!

[@rujakk9412]

I once thought that might work with the spinning sensors that go vertical and horizontal line so it almost does like 360 with slow trigger

[@suicidalbanananana]

Very cool! And impressive how far you are managing to take this idea. Keep it up! 👍

[@SSS333-AAA]

i check back on your channel and this is the fucking monstrosity spaghetti computing shit that i see. this is what we're here for brother. keep this shit up and you'll be making ballistics tracking integrated with a radar system in no time! (no time being 4 months)

[@ThisIsDumbAllTheNamesAreTaken]

just you wait :)

[@ramrod1290]

Genius

[@fredparker7363]

I am your 500th subscriber

[@ThisIsDumbAllTheNamesAreTaken]

neat

[@jhoelkrissianesisterr1977]

I hope you get famous someday

[@itsthorondil7608]

The analog memory bits will, unfortunately, 'stutter' a bit unless you find a way to 'filter' the output or input so they always stay at the same number. This is because, for example, from a steady-state of 0 and 0 on each gate, if you give one tick of input at say 0.5, the first OR gate it encounters will send it to the next OR gate, then set itself to 0 once again, then the other OR gate will do the same, causing the 0.5 (or whatever the value is) to flip flop between the two gates. This can be alleviated by halving your initial input value and sending it to BOTH gates, so they're always synchronized, alternatively you can filter the output through a 0.5 output OR gate, which then feeds into another 1.0 OR gate, and both those into one final OR gate, combining the two 0.5s into a 1.0 once again, effectively averaging the fluctuating output. For the first given example, it would output a steady 0.25, despite the input value being a 0.5, and again this is unnecessary if you initially halve the input values and send it to both OR gates in the memory bit.

[@ThisIsDumbAllTheNamesAreTaken]

thank you for a new solution to a problem i am aware of. the way i solve it, or at least get it small enough to a point where it is no longer a limiting factor, is simply making the input values 0.01. since half will be applied to one side and half will be applied to the other side, this pretty much solves the issues because the difference between the values becomes at most 0.01 at which point precision beyond that point becomes pointless.

[@ThisIsDumbAllTheNamesAreTaken]

the averaging is something new that i will keep in mind for the future. also sending a signal to both sides at once halves the potential amount of in-between values.

[@OdKoala184]

Could we see these creations in combat?

[@ThisIsDumbAllTheNamesAreTaken]

i still need to mount it on something that can move with an actual turret. next video.

[@knottem2587]

my drifts are sick 😎

[@nicholasrobert9676]

How does it realise that it's getting a locking though?

[@ThisIsDumbAllTheNamesAreTaken]

when two radar modals point in the same direction. it checks for this by connecting the rotation of one to a pink brick and connecting the other to a U shaped sensor thing. when they align that sends a signal confirming that direction to have targets.