(Medal link)
I swear man, everytime i use this targeting pod something weird happens! I just want to bomb SAM sites in nuclear thunder from far away, ive looked at all my keybinds trying to figure out whats wrong, some help please.
(Medal link)
I swear man, everytime i use this targeting pod something weird happens! I just want to bomb SAM sites in nuclear thunder from far away, ive looked at all my keybinds trying to figure out whats wrong, some help please.
It’s just how it works, targetting pod is…targetting pod, you target it by looking through it. You can’t separate targetting and looking, it’s a singular system.
damn :(
It’s a targeting pod, it set’s the target point, not sure what the issue is.
You can try using the new system that sets multiple points, might be what you are looking for:

Can’t say the same for the EF targeting gibberish.
Enlighten me?
PIRATE POI auto follow RADAR targeting overiding the POI, making it flick around evertime you tried to drop CAS munitions.
This bug was not fixed ever since… I lost count.
It’s another bug to add to the long list I have discovered including MITL being inverted on Xbox for no reason. I literally keep listing bugs until they are fixed in a notepad.
Isn’t that intended behaviour though? Some planes have radar tracking slaving to the pod, i think the F-15 does the same if i remember correctly.
It is sometimes but not always. There is a way to prevent it I think? Might be wrong.
I don’t have the EF so can’t test, it works fine with the JAS39E at least. Target pod goes to radar contact if you switch target but you can still de-couple it and lock it to something else and have radar and pod track independent targets.
That’s for seeker lock from munitions.
It also overides the TGP lock, besides the 3rd seeker lock.
That is not stated in that report though. I’m not saying it doesn’t happen (since i can’t test it myself), it’s just not what that report is saying.
Should ask @Morvran who wanted to do a report about that. I mainly reported the broken third-person-lock-on for SPICE-250/GBU-53.
Did I?
Which bug is this?
That was it I think :)