Q3ark

Problem: In BVR situation Jester AI not performing autonomous actions. This only seems to affect the early A model Tomcat, I have not observed this on the other two variants. Jester does not: Jester does not switch radar into TWS auto. Jester does not IFF or classify targets with the HAFU symbol. Jester does not call out range to target after being commanded to STT. Jester does: Jester does switch to TWS auto when commanded using the jester wheel. Jester does STT a target when commanded by the jester wheel. Attached track shows a BVR intercept starting at 200 nm on the Syria map. No mods installed. If it helps I uploaded a video to youtube I captured at the same time f14_a_early.trk

Same here, also the three status lights above the EKRAN display are effected too.

That old AWG-9 is great. Once you learn how to use it properly it’s like the eye of Sauron, nobody gets away

People around here are obsessed with the “D”

I thought we were talking about the F14 BU, that aircraft didn’t have an IRST and the lantirn only had controls in the back.

If there’s a RIO in the aircraft why would they go to the bother of giving the pilot full radar controls? It’s not the pilots job, I doubt you’ll be controlling the radar from the front seat.

This is something I’d like an answer to as well, what is the procedure for dealing with this scenario?

This happens for me as well, from cold and dark totally repeatable the nav system resets and the game stutters when I start to taxi from the stand. I’ll upload a track when I’m next on DCS

I’m a westerner and I can confirm that I regularly get confused.

This is the answer

Try adjusting the “resolution of cockpit displays” option in the settings menu, see if that makes a difference. That option needs a DCS restart to take effect though.

You can negate this by binding it to a switch on your HOTAS, it’ll stay out as long as you have the switch toggled on

Speedbrake in the fulcrum only stays extended for as long as you hold the speedbrake button, it retracts as soon as you release it.

You flew at that speed at 2000 feet? That’s you problem right there.

That’s great and all but what were your cruise settings? What altitudes did you fly at for each aircraft? What throttle settings? also if you don’t like the mig why are you here?

It’s a good incentive to not get shot down in multiplayer, makes me fly a little more realistically, reminds me not to take risks as a full start and INS calling awaits if I mess up.

Holy thread necro Batman seriously though why did they misspell night?

It’s been a while, I’m doing the F4 mig killers campaign at the moment, they’re a Mach 4 missile, though the top speed varies wildly. It’s dependent upon your launch parameters, a Phoenix launched down low in the thick atmosphere will be much slower and have a much shorter range than one launched up high.

Get yourself high and fast, the less atmosphere the phoenix has to go through means less drag, if you can get through the transonic region to Mach 1.2 (a lot of drag in the transonic area) before you launch that’ll help too.

When you’re on finals and you’re all nicely trimmed out use power to adjust your glide slope.

The old tgp needing a restart was a bug iirc

Is that the window with the drawing tools in it?

When in VR the input window where you can write appears at the front of your view where the jester wheel normally appears. It’s a bit inconvenient but it’s apparently a limitation of the DCS engine.

Don’t you think the design teams and engineers have been through all this? It’s fun to imagine what would I do in their shoes but these people know what they are doing. When is the last time you heard of a screen failing in an aircraft? This isn’t new technology any more.

Grease pencil works in VR, I was using it yesterday. The only issue is the input window appears at the front in the same place as the jester wheel but that’s a DCS limitation.