Hot_LZ

Yeah, can we disable the 'realistic head movements'? With TrackIR it totally sucks.

Saw your guide. First of all, I would just use X instead of Y, it's the standard. Also, most of what's in the guide maybe works in DCS (haven't checked it), but it's not realistic since it won't work that way in reality. Any 3rd, 4th, 5th etc aircraft would have to select Air-to-Air TACAN RECEIVE ONLY, like I said before. If you don't do that, the signal would interfere and render all distance measuring going on between the channels unreliable and useless. It's not true that the system just picks the 'strongest signal'. That just doesn't happen.

X is used primarily, for both air and ground. Y can also be used for air and ground. It doesn't matter at all. The standard is X, so just use X for air to air tacan. If you want a third aircraft to get range distance from the other two, be sure to have that third aircraft set on tacan RECEIVE ONLY.

He already answered your question in the opening post. It's basicly because TARS and Aries kinda suck, stability wise.

Teamspeak totally kills realism and immersion. For me, it's not an option at all. Especially not in the bigger missions I make where you really need to use different radio's and frequencies at the same time.

Hey guys, I'm designing a mission primarily for multiplayer A10C missions, and as usual, I run into a shitload of sketchy problems in DCS. I wonder if you guys could help me a little bit. One of the problems I'm having right now is controlling infantry. Sometimes I can, often I can NOT. I can click the infantry group, but I can't expand the bottom menu with the little arrow, and I can't make a path for them. But then again, sometimes I CAN make a path. What is up with that??? Also, I have some AI aircraft takeoff and fly circles. I want them to standby until I need them. But guess what, I can't order them around... But when I'm testing via the mission player, so single player, it works!!! Are these known bugs, or am I doing something wrong?