3 ms·
Sorry but- after the JSF debacle- is this not already a dead duck? Honestly- on a battlefield, everything in addition you want has to be unobtrusive, totally in
by Pica_soO 8y ago
Sorry but- after the JSF debacle- is this not already a dead duck? Honestly- on a battlefield, everything in addition you want has to be unobtrusive, totally intuitive and non-view obstructing. The last thing you want after a IDE has blown up, to see MS Clippy hoping through the wreckage, producing friendly fire.
Just take the integrated battlefield promised with the JSF, generating more Noise then usage. Im sure, you could add something similar in theory to a FPS, basically estimating the position of a retreating shooter.
But why bother and risk - when some well placed mortars will do that?
Just because it looked good in scifi movies, doesent mean its good in reality.
Only parties that could benefit from this, are specialists- meaning, drone-flights, commanding officers and upgraded personal- (medics in need for direct instructions by a doctor) - even those could usually be easier given without the AR.
And thats from someone who is a huge AR fan. Maybe im overlooking some benefits- i would really appreciate some usecases - if i missed them.
- ericd 8y agoMaybe non-obstructive collaborative battlefield annotations would be helpful?