Floyd1212

This appears to be a known bug, mentioned in the Bugs and Problems forum:
https://forum.dcs.world/topic/332503-external-fuel-tanks-and-hot-vs-cold-starts/#comment-5280033
 

Page 240 of the new manual describes the procedure.
Before you can type in a point using the KU you need to press L1 for "POINT>?".

Page 74 of the (new) manual does a good job of explaining this.

 
8. SYM Rocker Switch. Controls the brightness level of displayed symbology on the TDU or within the CPG’s HDU. When the CPG’s selected sight is HMD, the symbology within the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the symbology brightness on the TDU will be adjusted. The symbology brightness may be incrementally adjusted using short presses, or continually adjusted using continuous presses.

9. BRT Rocker Switch. Controls the overall brightness level of the TDU or CPG’s HDU. When the CPG’s selected sight is HMD, the overall brightness level of the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the overall brightness level of the TDU will be adjusted. The brightness level may be incrementally adjusted using short presses, or continually adjusted using continuous presses.

10. CON Rocker Switch. Controls the contrast level of the TDU or CPG’s HDU. When the CPG’s selected sight is HMD, the contrast level of the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the contrast level of the TDU will be adjusted. The contrast level may be incrementally adjusted using short presses, or continually adjusted using continuous presses.

11. Asterisk Button. Resets the overall brightness and contrast levels to their default settings. When the CPG’s selected sight is HMD, the overall brightness and contrast of the CPG’s HDUwill be reset. When the CPG’s selected sight is TADS or FCR, the overall brightness and contrast of the TDU will be reset.

Here is a thread with a SME discussing the tail rotor thrust after the changes made in OB ver 2.7.18.30348.
 

This is where the “cursor select” function on your analog stick comes into play.
When you have the circles lined up and centered, just press select on your analog stick and you are done. You don’t have to take your eyes off the boresight reticle. 

When you drop a unit in the ME you can check/uncheck the option to "Hide on MFD" for the group.
If it is unchecked, the group will show up in the pre-planned "threats" category in the TSD.  It's been a while since I have played with it, so I can't recall if only some unit types show up, but I know it works for SAM units.
You can search for "threats" and find the pertinent threads.
In the future, when/if ED implements the Data Cartridge feature you might be able to plan out a mission and then preload points into the TSD at mission start. 🙏
Edit: Found these threads:
https://forum.dcs.world/topic/319135-placing-targets-in-the-editor/
https://forum.dcs.world/topic/301194-option-for-automatically-importing-mission-editor-targetthreat-control-measure-points/
That second thread is older, and I think some of the issues have been improved upon, but still not perfect

ED has indicated they are looking into it.

We have seen a few cases of trim just straight-up not working. In the two cases I can recall, the solution was to reinstall DCS.
For example:
 

There was a patch a while back that changed the "neutral" position of the tail rotor blade pitch.  (I'm sure you can find some discussions about it if you search a bit.)  This change means there is now less pedal input needed for a given amount of thrust at the tail than there was. 
In addition, the SAS is providing some assistance if you pull gently into a hover.  Even if you have your feet off the pedals, you can see the green mark giving it a little left pedal for you when needed.

You can also apply curves to the LMC axis to get whatever sensitivity you are looking for.  I will say that having a quality thumbstick, like on a game controller, makes it much easier.
Also, you are using IAT to "lock on" to targets now, right?  It wasn't available when this thread was started last year.

Like NeedzWD40 said, are you using [George Hat] Short Left to cycle him through his weapons, or are you WASing the weapon for yourself in the back seat?
Telling George what weapon system to use is different than the system you are using from the back.

I looked it up in the Quick Start Manual. On page 304:
I only recall seeing the warning a couple times, but now I know what to do if I see it again.

I'm not seeing this behavior.  Maybe a control bind conflict?  Maybe a hardware issue?

You need to make sure the "Hidden on MFD" is unchecked for the group in the ME, then they will show up in the threat database at the mission start.
Some units, like SAMS and AA will show up as TGTs, where other units, like armor will show up as Control Measures.
To see the CMs on the TSD, make sure you go to TSD > SHOW > COORD SHOW  and enable ENEMY UNITS.

nullA screenshot of what you are seeing on the IHADSS and your TSD page when this happens would be helpful. 
Like mentioned above, you want to make sure the Acquisition Source is set to TADS in order to see where the CPG is currently pointing the laser.

If the TADS is looking 90 degrees off to the right, you won't see the dashed reticle unless you look off to the right for it.  The little dots around the LOS reticle will tell you where to look for it in relation to your current head position.

While tracking the target, move the TADS cross-hairs to a different position on the unit and press IAT Fwd again.
It's the same procedure like you are adding a track to a new vehicle, but if you are already tracking that vehicle, it updates the position.

Page 112 of said manual describes the FMC channels, and the UTIL page is where you can enable/disable each if you like.
 

I posted some instructions in another thread here:
https://forum.dcs.world/topic/298935-cpg-vr-view-is-off-center-to-the-l-side/?do=findComment&comment=5029995
I'm not sure how it works in VR; this may only work for flat-screen.

There are some explanations in this related thread, but the short answer is you won't get the same dashed reticle indicating where the TADS is looking from the front seat, like you do from the back seat.
 
 

Try setting a dead zone of 4 on that axis.
this was an early bug with the cursor getting stuck on the edge of the screens. The dead zone seems to help. 

No, you will need to hold the pedals in this position after unlocking the tail wheel.  At this position, the pitch of the blades on the tail rotor are "flat" and not inducing any lateral forces on the tail.  Once you increase collective on the main rotor for lift-off, you will also add some left pedal which will bring it back closer to center.
If you have springs on your pedals you can "trim" the controls in this position and then release your pedals back to center, and this becomes the new center point for your controls.  Most would recommend removing the spring from the pedals and using the "spring-less pedals" trimmer setting so they aren't affected by trimming, then you can leave them in this position for as long as you need to.

Not sure what you are seeing on your end, but when I replay your track, everything seems to work fine.


Are you not seeing the display light up?  Maybe a messed up .lua file in the displays folder?
Are you able to launch chaff/flares, even though the display is dead?

It is much better again, and seems to hold a hover nicely once settled down.  👍
I don't know what to expect out of the system when intentionally maneuvering the aircraft with ALT hold enabled.  I was in a hover at tree-top level and tried to creep forward slowly with ALT Hold enabled and it allowed me to climb a bit before kicking in, then when I slowed back down to 0 it allowed me to descend a bit as well.

The answer to your first question can be found in this thread:
The short answer is neither of those features has been implemented yet.

You will want to program your main throttle on your HOTAS to the "Collective" axis in game.  This is what controls the pitch of the blades, and therefore how much lift they are producing.
The left and right throttle levers you see to your left in the cockpit are set to "Fly" during the startup sequence, and are not adjusted after that.  I think a lot of players will adjust these manually with the mouse, and not have them bound to an axis on their HOTAS.
Also, you use RALT+HOME and RSHIFT+HOME to get them from "Off" to "Idle", though you can bind those to switches on your HOTAS of you desire.