jojo

Works for me, I only tried in solo. But other people confirmed that it works on MP servers, even with pilot + WSO and integrity check.

If you need ILS, line up far enough and figure out with yout ADI needles. After landing, just park anywhere you like.

That's a DCS World issue, not specific to M-2000C.

You can make a desktop shortcut to launch DCS in non VR mode, like so: "F:\DCS World OpenBeta\bin-mt\DCS.exe" --force_disable_VR

What is the speed of your tanker ? The reference speed to refuel F-4E is 315 KIAS. If you’re too slow, you will enter a flight domain where throttle inputs (to stay in position) will create pitch variations and then it’s very difficult to fly. At 315 KIAS it’s stable and easy. Here are some values you can set in the mission editor for the tanker to get close enough to 315 KIAS. 18000ft: 400kt TAS 20000ft: 412kt TAS 22000ft: 425kt TAS 24000ft: 437kt TAS

Up ! At least a key bind to request boresight to current radar range, followed by context action to lock the target would be of great help.

Well, not everyone as the luxury to fly with a human WSO as proficient as you

That's weird. I re-launched the same mission after restarting DCS, and now it's working OK. I used the same release parameters in bombing table, I tried diving from 25 000ft and pop-up attacks, now both work whereas both failed on previous session. So far cased closed for me.

Yes I did. Dive-Toss was working fine for me before the patch, that video is the third failed attack run. I will retry with an air start...

I'm dumb, but not that much !

I don't understand, I have the lock, I have tone, but the bombs are released way too late ! Am I doing it wrong or is it broken ?

@Zabuzard Thats something I would like to be sure about. You say that the Phantom needs to be trimmed constantly. But in landing configuration, at slow speed with +/- throttle inputs (to control the glide path) causing pitch changes and the trim being so coarse, it seems better to trim roughly OK and then handle AoA around neutral position with manual pitch input on the stick rather than with the trim on many other jets. Would that be the correct technique to handle it ? So far, small inputs on the pitch trim to try to release stick pressure seems to do more bad than good.

Already figured that out, but thanks.

I’m complaining about the system because it’s a pain to use at landing AoA. So yes I did try at slow speed. If it’s an accurate simulation, so be it. But there were better trim systems in the same time era. I have a Virpil WarBRD base and it’s already expensive enough as it is…

OK then, worst flight control system ever. I hope the guys who designed that were sentenced to life prison

Then how does Ian Christies put bombs on target in his video ? I also did it but with more lateral deviation...but it's on me.

Here we discuss INS and offset. LOFT does work with Jester. He computes offset between current IP and the next with Bombing Table when you click "Tell Jester". Then, when squeezing bomb release button when overflying the IP you're guided toward the offset target.

@Zabuzard Testing the trim system on the ground. I have no idea if it's the intended behavior, but the trim inputs on the Phantom are wild !

Because you don’t have a ground speed gauge in the cockpit ? It’s already great to have a TAS gauge on such old aircraft.

OK, thanks guys 12-VIS is fine

@Zabuzard Up

The manual is little bit short here. 1- is it working already ? 2- if yes, how do we do that with Jester from front the pilot seat or jumping into the back seat ? Thanks

OK thanks. I understood that the guidance started when pressing bomb release, but I wanted to be sure that Jester was computing offset with the WRCS board “tell Jester”. Thanks for your patience

Same problem for me. MT Client. Virpil WarBRD base + Thrustmaster Hornet stick. The slower it gets, the more difficult it is to trim, at landing AoA I’m fighting the jet. I can’t let the stick go even half a second. I’m always one click too much or one click not enough with the Trim HAT. I can trim the Tomcat in landing configuration fine.

But there is also a roll guidance, isn’t it ? Jester has to enter N/E and E/W offset. My question are: - does he assume offset from current waypoint and next waypoint ? - when does he input offset into WRCS ?