Sensor slave order possibly incorrect with mavericks loaded
-
I have noticed this problem for a while and today I tried to see if it was reported or being worked on. I didn’t find anything, but then I probably don’t know where to look.
Anyway, currently there is one key thing I have to keep in mind when using mavericks: After the last maverick is fired, the targeting pod becomes useless in A/G mastermode. Why? Because SOI slave order goes like this: mav and tgp slaved to FCR > FCR lock target, SOI goes to mavrick and tgp slaves to maverick > TMS back with mav as soi slaves mav and tgp back to FCR.
After the last mav is fired, the weapon page shows WPN OFF, and the tgp is still slaved to the now non-existent maverick. And of course since the maverick doesn’t exist, we can’t command it to return slave control to the FCR, and thus, the targeting pod cannot be controlled.
Now with that said, let me also say that I like having the tgp slaved to mavericks, as it lets me have a much closer look at what the mav is actually locking on to. However, recently I have been experimenting with loadouts of both mavs and LGBs for interdiction at high alt, and this bug makes it so I have to use LGBs first. It would be much better if I could use my mavs on the way to the target and then switch the LGBs as I’m flying over, instead of flying over first, then extending away, turning around and, well you get the idea.
Thoughts?
-
Hi, you will have to wait for some better SPI management in the future. In real, TGP never slave to the Maverick but it’s the opposite way (well besides VIS mode maybe…), just currently Maverick & TGP aren’t working so nice along.
-
@Mar:
I have noticed this problem for a while and today I tried to see if it was reported or being worked on. I didn’t find anything, but then I probably don’t know where to look.
Anyway, currently there is one key thing I have to keep in mind when using mavericks: After the last maverick is fired, the targeting pod becomes useless in A/G mastermode. Why? Because SOI slave order goes like this: mav and tgp slaved to FCR > FCR lock target, SOI goes to mavrick and tgp slaves to maverick > TMS back with mav as soi slaves mav and tgp back to FCR.
After the last mav is fired, the weapon page shows WPN OFF, and the tgp is still slaved to the now non-existent maverick. And of course since the maverick doesn’t exist, we can’t command it to return slave control to the FCR, and thus, the targeting pod cannot be controlled.
Now with that said, let me also say that I like having the tgp slaved to mavericks, as it lets me have a much closer look at what the mav is actually locking on to. However, recently I have been experimenting with loadouts of both mavs and LGBs for interdiction at high alt, and this bug makes it so I have to use LGBs first. It would be much better if I could use my mavs on the way to the target and then switch the LGBs as I’m flying over, instead of flying over first, then extending away, turning around and, well you get the idea.
Thoughts?
You can get the TGP to work again. Go to guns and back to the mavs (0 AGM-65s). Can’t remember if you have to go out of A-G mastermode and back… I’ll check and report back, but I know exactly what you’re talking about because it happened in a flight this weekend and I just cycled it going to guns and back and it worked fine again.
-
Yeah, now I know I’m stupid. Simply switch to the LGBs. Why didn’t I try that before?