Please don't let Iceman touch the throttle.

[RPY Variable]

When you go to the rear pit he ALWAYS does the wrong thing!.

Case a) If you are full afterburner trying to gain speed and jump to the rear pit, he shuts down afb... waits multiple seconds and then, maybe, he turns the afb again maybe not.

Case b) You are in mil power, low fuel, you jump to the rear pit he turns the afterburner... then you ask him to slow down, and he opens the air brake as if you just realize there is a speed-camera in front of you.

It's impossible to jump to the rear pit if he is going to mess sup all your speed tactic.

Solution

a) Just make him not touch the throttle unless he is asked to make some change, or AOA is more than X amount.
b) When you jump to rear pit, and afterburner is on, let it on, unless you ask him to slow down. And if you jump to the rear pit with the afterburner off, do not turn it on unless you ask him to speed up.


 

[draconus]

It's being requested from time to time and it seems incredibly hard to fix.

[RPY Variable]

14 hours ago, draconus said:

It's being requested from time to time and it seems incredibly hard to fix.

Just make a special option "turn off iceman AI"...

This AI dictatorship, which doesn't even let me touch a button from the front, or at least pointing the radar, is the main reason why it didn't even cross my mind to buy the F-4... And I love that plane, but I already suffer from this logic with the f14. I'm going crazy moving my head everywhere to point the radar with no luck and ending up having to use PAL because I'm already merged, o running away because I fail to point the radar via jester menu. And if I go to the rear pit, the things I mention above happens.

That purism doesn't make sense. I don't see the justification why I can go RIO seat and move the radar height, but Troy burns if I do it from the front. Pointing radar from the pilot seat saves me the pain of having to go backwards, and prevent iceman from changeling my entire flight parameter. What is so serious about pressing a button from the pilot seat vs. saying "jester, press that button". It doesn't make sense, and the worst thing is that it's more complicated.

[WarthogOsl]

I think they usually say it's tied into the Iceman autopilot functionality, but I'd happily have Iceman be disabled on every axis if it would prevent him from touching the throttle as well.  Just have the plane do whatever it does when the pilot GLOCs or is killed.  I accept the risk!

[draconus]

3 hours ago, RPY Variable said:

What is so serious about pressing a button from the pilot seat vs. saying "jester, press that button".

Simulation, physics, realism - we come to DCS for that, remember?

It takes time (training!) to learn to how to talk to Jester but you'll be way more successful if you learn the radar operation (and its limitations) in the first place. If Jester menu or changing seats no longer work for you then human RIO is your last bet. Otherwise 2-crew aircraft are maybe not for you.

[RPY Variable]

29 minutes ago, draconus said:

Simulation, physics, realism - we come to DCS for that, remember?

It takes time (training!) to learn to how to talk to Jester but you'll be way more successful if you learn the radar operation (and its limitations) in the first place. If Jester menu or changing seats no longer work for you then human RIO is your last bet. Otherwise 2-crew aircraft are maybe not for you.

1) It is not necessarily more realistic, for example, to move the radar axis from the front than via jester menu, it is the same, only more cumbersome.

2) That I make this proposal does not mean that it cannot or does not know how to be effective, or that I need to "learn the radar operation", or whether two crew aircraft are or are not for me. You don't know how many hours I have in F14 and suffering with Jester, or flying RIO. A little pedantic attitude for my taste.

This other proposal, which was very simple, and any rational being will totally agree, has not yet been modified. I'm not complaining that they didn't modify it, because they don't have to. The thing is that since they won't let me move the radar axis from the front, at least, consider correcting this. It is to improve Jester by only changing 4 values in the code.

And now that I see the post, you also showed up to teach classes, with an air of superiority that seems to characterize you. In that thread, in this thread, and in other two threads. You never fail.

[draconus]

35 minutes ago, RPY Variable said:

1) It is not necessarily more realistic, for example, to move the radar axis from the front than via jester menu, it is the same, only more cumbersome.

It is unrealistic for the pilot to reach rear seat controls, that's why it will never be implemented in realistic simulator. Pilot has only limited auto-acquire modes available for radar operation, mostly for WVR. Either your RIO does the radar job or you ask him to do it - not the same as you doing it.

If you don't care about realism you can use mods like this:

https://www.digitalcombatsimulator.com/en/files/3319633/

43 minutes ago, RPY Variable said:

You don't know how many hours I have in F14 and suffering with Jester, or flying RIO.

I just follow what you wrote:

6 hours ago, RPY Variable said:

...I already suffer from this logic with the f14. I'm going crazy moving my head everywhere to point the radar with no luck and ending up having to use PAL because I'm already merged, o running away because I fail to point the radar via jester menu.

37 minutes ago, RPY Variable said:

You never fail.

Thank you, appreciate. I always supported the change for radar elevation Jester menu btw.

[RustBelt]

You can run most of the back from the front with a DCSBios interface like DCSFlightpanels, or MATRIC or Helios.

realism is cute, but it IS a game. Play how you like.