markturner1960 Posted December 22, 2024 Posted December 22, 2024 Been working on using this with TOO JDAMS and found some strange behaviour. One was ( And I am not sure exactly what preceded it) that after designating a target, pressing the undesignate button did not seem to work, I still had the HUD indicator arrow pointing towards the target and did not seem unable to re designate another? What might cause that? Also, when in snowplow doing the initial ground stabilise, the target pointr seemed to be not where the velocity vector was pointing exactly....its in the general area, but offset down and to the right....again, any ideas what is happening and why? I dont have a track so appreciate this is a bit vague, but maybe someone can help? Is there a good definitive up to date guide? Chucks? System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Phantom711 Posted December 22, 2024 Posted December 22, 2024 (edited) vor einer Stunde schrieb markturner1960: I still had the HUD indicator arrow pointing towards the target I havn‘t tried to replicate this, so my answer is probably just as vague as your question. One thing to remember is, that undesignate does not delete the target from the JDAM. So if the JDAM with the previously designated TOO is selected, this is still the target that you are currently going after until you designate a new one. vor einer Stunde schrieb markturner1960: did not seem unable to re designate another The double negative throws me off here a little . So, were you or were you not able to designate another tgt? Sometimes I‘m not 100% sure either, what is going on, but usually either a TDC depress or cycling through the tracking modes solves the issue. vor einer Stunde schrieb markturner1960: the target pointr seemed to be not where the velocity vector was pointing exactly....its in the general area, but offset down and to the right Are you sure you were in the correct mode? There are two modes which you can cycle by a double tab on the NWS button. In one mode the TGP is on the velocity vector and on the other the TGP is pointing straight ahead and a few degrees (15?) down. Edited December 22, 2024 by Phantom711 1 vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.
markturner1960 Posted December 22, 2024 Author Posted December 22, 2024 (edited) I think the answers to all are in there mate, much appreciated! ( I was not able to designate BTW, apologies for my grammer!) Edited December 22, 2024 by markturner1960 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Muchocracker Posted December 22, 2024 Posted December 22, 2024 1 hour ago, markturner1960 said: Been working on using this with TOO JDAMS and found some strange behaviour. One was ( And I am not sure exactly what preceded it) that after designating a target, pressing the undesignate button did not seem to work, I still had the HUD indicator arrow pointing towards the target and did not seem unable to re designate another? What might cause that? Also, when in snowplow doing the initial ground stabilise, the target pointr seemed to be not where the velocity vector was pointing exactly....its in the general area, but offset down and to the right....again, any ideas what is happening and why? I dont have a track so appreciate this is a bit vague, but maybe someone can help? Is there a good definitive up to date guide? Chucks? When you make the handoff to the selected JDAM that information stays on your HUD as it's the steering release cues for that bomb. When you undesignate you're removing the aircraft's designation. They are 2 separate things but they're going to share some symbologies. to remove all of it you have to switch to a JDAM with no handoff information, deselect jdam's, or hit the erase jdam option to wipe the info. To update the handoff information on the bomb you have to do another handoff. Which is by TDC depress, or by creating a new designation. 1
rob10 Posted December 22, 2024 Posted December 22, 2024 5 hours ago, Muchocracker said: .... or hit the erase jdam option to wipe the info. Has this changed over time or does that not completely wipe the JDAM and make it a dud (i.e. it wipes all the programming and what not) and completely unusable? I know that was the case when the F-18 came out, but that might have changed since.
Muchocracker Posted December 22, 2024 Posted December 22, 2024 6 hours ago, rob10 said: Has this changed over time or does that not completely wipe the JDAM and make it a dud (i.e. it wipes all the programming and what not) and completely unusable? I know that was the case when the F-18 came out, but that might have changed since. 6 years ago bro
markturner1960 Posted December 28, 2024 Author Posted December 28, 2024 (edited) Thanks all, this information is very useful. If it's useful to anyone, I have made a basic kneeboard concerning JDAM useage, can someone check I have the information correct? HORNET JDAM.pdf Edited December 28, 2024 by markturner1960 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
rob10 Posted December 28, 2024 Posted December 28, 2024 I'd make a note that your co-ordinates have to be DD MM SS.SS (rather than DD MM.MMMM). And freaking autocorrect changed your HSI to HIS at the bottom of page 1. And technically the Hornet does not use SPI or SOI (those are Viper things). You designate a target via the sensor that is PRIORITY (i.e. has the * on it) not SOI -- that's a nitpicky detail, but it can be confusing if you're switching between Hornet and Viper. Also might be worth mentioning you need to TDC depress to designate the target and send it to the JDAM (unless your WPDSG is right over the target). And make sure you UNBOX the stations unless you want to assign any designated target to all of the selected stations. Not sure if deselecting the JDAMs removes targets from it (you'll have to realign it) . You might want to check that. 1
Muchocracker Posted December 29, 2024 Posted December 29, 2024 23 hours ago, rob10 said: I'd make a note that your co-ordinates have to be DD MM SS.SS (rather than DD MM.MMMM). only if you're using Pre-Planned with the manual lat-long input. It doesn't care about the jet's current selected format in TOO 2
Recommended Posts