Rackham

You are right : my mod has to be updated (higher display readibility at high resolution). Thanks very much

Since the last DCS Openbeta update (52196), my displays are out at the beginning of the mission...

Look at this mod : https://www.digitalcombatsimulator.c...files/3301897/ Hope it will help. Using this mod, displays (HUD, DDIs and AMPCD) look sharp at normal zoom.HUD text has been sharpened and green color has been modified in order to be red on a bright background. On AMPCD, HSI text and lines are now red without outline: this way text and HIS symbology are easily readable with moving map on and also off.

75th, what are your needs ?

Look at this mod : https://www.digitalcombatsimulator.com/en/files/3301897/ Hope it will help. Using this mod, displays (HUD, DDIs and AMPCD) look sharp at normal zoom.HUD text has been sharpened and green color has been modified in order to be red on a bright background. On AMPCD, HSI text and lines are now red without outline: this way text and HIS symbology are easily readable with moving map on and also off.

Try this mod : https://www.digitalcombatsimulator.com/en/files/3301897/

A tip : I used this mod https://www.digitalcombatsimulator.com/en/files/3300978/ to help trimming during the learning curve. Once full flaps and gear come down together, below 250kts, you just have to trim till the white indicator reach the level -2.5 : this is the maximum trim you will need. Then you wait till speed reaches 150 knots, then follows the curse of the plane and use throttle to E bracket, with anticipation. The ballooning effect will be smaller if flap and gear are activated below 200 kts.

Look at this mod : displays look sharper at normal zoom (32” display, 3840x2160 resolution). https://www.digitalcombatsimulator.c...files/3301897/

Displays Readability Mod Look at this mod : displays look sharper at normal zoom (32” display, 3840x2160 resolution). https://www.digitalcombatsimulator.c...files/3301897/

Look at this mod : displays look sharper at normal zoom (32” display, 3840x2160 resolution). https://www.digitalcombatsimulator.com/en/files/3301897/

No problem to convert each and every command by keyboard or joystick in a vocal command, but addition must be done in VoiceAttack (Edit profile / New Command).

To manage your trim, you could use my mod : https://www.digitalcombatsimulator.com/en/files/3300978/ It adds a new scale on the pitch axis of the controls indicator and changes the trim index color to white, in order to appreciate the amount of trimming which is needed during landing...

I also felt in the water... the reason : throotle's Y saturation was not 100, so my afterburner never reached the maximum power...

It seems DCS manual is faulty. In NATOPS manual, before taxi procedures, III-10-13 : "Place the attitude selector switch to STBY, check that the velocity vector disappears and pitch ladder is referenced to waterline symbol ( W ). Verify INS ATT caution is displayed. Check that standby attitude reference indicator is erect and HUD pitch ladder appears. Verify Xs appear in CH 1/3 of the PROC row on the FCS page. Return the switch to AUTO".

Thanks for your post. It seems DCS manual is faulty. In NATOPS manual, before taxi procedures, III-10-13 : "Place the attitude selector switch to STBY, check that the velocity vector disappears and pitch ladder is referenced to waterline symbol ( W ). Verify INS ATT caution is displayed. Check that standby attitude reference indicator is erect and HUD pitch ladder appears. Verify Xs appear in CH 1/3 of the PROC row on the FCS page. Return the switch to AUTO".

Here is a post by Malek : "There is another issue why the autopilot might not engage. According to the manual, you should set the "Attitude Source Switch" below the UFC to standby during the start up, but with this switch in standby the autopilot will not engage. So I leave it on auto". I have to try...

66 here...and I am traveling all day tomorrow :(

Vocal recognition should be a must. A first step could be to redefine the comm menus (the authors of VAICOM 2, based on Voice Attack, should have good ideas on this matter). Comm could be limited to the radio functions; vocal command could be an option.

Thanks Sabre, in fact, based on a few tests and on my configuration only, it seems that Easy Comms does not run with AFT01 campaign mission (with or without vocal command). I had no problem with AFT01 practice or BFT missions.I will try to be qualified with Easy Comms off, as it seems running correctly.

Rectification : communication with tanker is possible in the practice mission but impossible on the campaign mission. I use DCS openbeta upgraded to 1.5.3, the latest missions and Easy comms with Voice Attack and VAICOM 2.0. The problem is this difference between the two versions of the same mission, played with the same configuration. Is communication with the tanker theoretically possible as soon as we fly or is there a trigger somewhere in the campaign mission ?

Tanker communications In VAICOM 2.0 I note that communication with tankers seems to be on VHF1, while DCS World is now on UHF (251 Mhz). Is this a problem ? (I'm looking for the reason why I can't communicate with tanker in Easy command and Auto command).

Tanker comm A full day trying to find an answer to this question: why am I unable to communicate with the tanker in the AFT01 training mission, but not in the campaign mission? Yet I respect all DTOT, with exactly the same navigation and radio settings... Some help would be highly appreciated.