Callsign JoNay

Good catch, I've never noticed that.

My virtual squadron and me noticed a bug in the latest OB. AI JTACs are unresponsive on comms. I tested the same miz in the following conditions: MT+SP = JTAC responds to check-in. MT+MP = JTAC is unresponsive. ST+MP = JTAC is unresponsive. I haven't tested ST+SP yet, I assume that works since MT+SP works.

The liveries folder is already pretty bloated.

I get that, but it was also mentioned in the patch notes that the light direction was corrected, and that doesn't seem to be the case. Anyway, I'll drop it for now, and wait for future improvements. Thanks for the replies.

Agreed. The issue seems to be the direction the light is pointing more so than the strength of the light. @IronMikeDoes anyone from the HB team have a picture of the light working as intended?

It's not just me in particular, so far nobody had been able to show a picture of the improved light. I will try repositioning. Are you able to show us a screenshot of what it looks like on your end?

I don't think there is any bind or axis that it can be mapped to. I agree, it would be nice. I'm not a fan of the Jester LANTIRN implementation decisions. I have a spare TDC on my throttle quadrant doing nothing, which could be used for things like this.

Are you positive the implementation made it to the patch though, and wasn't accidentally left out on the cutting room floor similar to other recent Tomcat fixes? It might be worth confirming, IDK. I don't see one photon of light hitting this basket.

I wonder if it's a case of something getting lost between what HB worked on and what was actually submitted to ED for the patch, because I don't see any change to the probe light at all. It's been happening a lot lately. The fuel dump bug occurred, HB said they fixed it, but it got overlooked somehow on the next patch and we had to live with it for another cycle. Same thing with the busted wheel chocks too, IIRC.

Comment edited/removed: Replied to thr wrong thread.

+1 I'm not seeing any probe light improvements in MT.

A customizable picture in the cockpit is an awesome idea.

In DCS sometimes you have to wake the axis up with some movement before it responds. If you just put your IRL throttle to cutoff position and jump in the HB Tomcat, the throttle might not be in the correct spot initially. Sometimes I have to push the throttle to idle and back to cutoff before I begin starting things up to wake up the axes. I've never once modified my key file lua in DCS, and I can assure you the cutoff/detent works for me with no modifications necessary.

You have to wait for the horizontal authority warning light to go out.

I love that suggestion. Too bad HB considers Iceman feature complete.

They glove pylons were absent in some ACM training, too.

I just checked out my controls. The only thing you need to do is set right and left engine cutoff to the mechanical cutoff position (behind the detent) on your HOTAS throttle. Pushing the throttles back over the detent into the mil power range automatically pushes the DCS Tomcat's throttle levers into idle position. So you didn't have to adjust any keybinds, it's already built into the engine cutoff command as an "on else off" type command.

Update as of March 5th 2023! Recruiting has re-opened for the F-14B and A-10C II, along with F-16C, F-15E, AV-8B, and AH-64D. Of all the modules that we operate, only the F/A-18C and LotATC are closed enrollment.

Only server side tracks replay correctly. You wont be able to view from the cockpit, though.

Isn't there a known bug with the AOA indexer lights at night if the brightness knob is not above 6, or something? Did you try maxing the brightness knob to see what happens?

Jester holds your requested FOV zoom level when you are using head control and Vaicom? And when you are Qing to waypoints?

I don't know why you're looking at it that way. I tell Jester to use RWS vs TWS vs STT all the time. I manage his TID range, his az/el, I am the one who shoots the missiles, etc. You would have a point if I asked Jester to search for ground targets or something, but once I've taken direct head control it should be my LANTIRN not Jester's.

He never leaves the zoom where I ask him to leave it, even when I've taken direct head control. I think the Vaicom function is bugged.

You don't need to add anything, it's alreay there. I use my winwing throttles to move from cutoff to idle all the time. I can't look up the name of the keybind because I'm traveling away from my PC, but it's in there somewhere.