this post was submitted on 23 Nov 2025
106 points (100.0% liked)
Not The Onion
18671 readers
683 users here now
Welcome
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
Please also avoid duplicates.
Comments and post content must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They're just wasting so much resources and don't even know what they're doing. "Just keep putting more receivers, they can't jam them all... can they?"
that’s not even the most incompetent part imo
the fact that the missile tries to change direction too quickly and just breaks itself apart from the aerodynamic pressure is crazy… it’s literally hobby robotics 101 to put limits on acceleration etc
It's just the life of each software dev: don't need to account for this situation, because the target would never move by 10000kms within seconds. Plus, the buyer would never bring a failed unit back to ask for a refund, so why bother and spend more on development. Unless it's a liquid fuel rocket, you wouldn't be able to change Trust and speed once fired.
the theoretical reason for doing that is that if you have to split jamming power over broader frequency range, then for every n^2 times increase in bandwidth, here number of channels, range decreases n times. however gnss signals are so weak, it probably doesn't matter, and if you're adding extra power per channel, then it doesn't apply
now if missile detects that gnss is fucked with (signal too strong, wrong direction, physically impossible location), the correct thing to do would be to fallback to inertial navigation while accepting that accuracy decreases until gnss can be received again, if at all, and acted upon. theoretically speaking, it's a matter of software update, better hardware also can help with that, so idk why would they release this. maybe there's something that prevents this