Rongor

As long as it isn't documented we have no idea whether it works. We only know that pressing the button has some effect, for example the status window box being displayed around the TAS and the disengage button making the box go away. There even seems to be some effect on the flight but everything else is pure assumption. the only thing not waiting for stuff to be implemented is the FTR and the disengage. Since we can not even select an attitude hold mode, which per the manual is a precondition, it seems a far stretch to claim "it works" and I would prefer people to stop putting their assumptions out as if they were facts. Then this thread might be a lot shorter

No aircraft is operated with any kind of standard frequency valid for that aircraft. You use a frequency to communicate with somebody. You will have to know which frequency he is monitoring. Be it a tower of an airfield, your wingmen, ground forces, air traffic control, who knows. There is no standard. Can you be a bit more specific what you are looking for?

Yeah I understood you right away, I only mentioned the keybind to avoid misunderstandings. I didn't know it had a clickspot. couldn't even find it so far

Maybe you should have stopped way earlier. This thread is overloaded with false assumptions and misconceptions inducing ever more confusion.

If you fly that way, then you have to learn how to fly a helo from zero. Simply apply right pedal gradually until your nose points somewhat in the direction of travel. Don't accept the roll attitude either. Also this is has nothing to with force trim. It's just bad flying.

No it's not, you are mixing up five different things. 1. This thread is addressing Force trim in it's title. This is the mechanic of easing your controls to some kind of centered/force-balanced state 2. Depending on the wind situation, you generall may want to steer in a way to either achieve an intended ground track (nose off of desired track to achieve a speed vector which combined with the wind vector lets you arrive at a destination on a straight line) or to keep a specific heading (nose pointing towards a target, launch rockets in longitudinal direction) 3. The trim ball has nothing to do with force trim. The force trim release's only purpose is to set your current steering inputs as the new 'center' to ease your control inputs. 4. whenever the trim ball is out of the center (disregard slow speeds close to hover, the ball isn't made for that and can be ignored in these occasions) you are moving through the air mass in a way that applies more vane effect on the one side of the helo than on the other. So you use pedal, this has nothing to do with point #2 5. yes, the wind vane effect of *forward speed* does support counter torque. No it doesn't seem to be what is described. Flying with 20° yaw and 10° roll constantly has nothing to do with aerodynamic trim nor with necessary countertorque. Flying with 20° offset is ridiculously beyond necessary values.

The faster you go, the more wind vane effect will support you countering the main rotor torque. So you'll need more rudder, the slower you go. You will barely find a trim position not needing rudder inputs after a few seconds, so (while I do trim the rudder too) I can understand people simply not trimming it as they will have to give rudder input aynway and maybe you don't want to trimm all the time. If the necessary pedal work doesn't strain your feet and right hand and arm too much, you can fly this helo very well without using the trim at all. No, a constant yaw at about 20 degrees to the left just to go in a straight line is certainly not connected to a helo's aerodynamics and not needed to counter torque. 20° yaw offset may be necessary to achieve a desired ground track during a storm. In any other case the dude at the controls should take flying lessons.

It's related by the title you gave this thread

While I can agree to the unquoted rest of your argument in this very post you made, these quoted words above hopefully will never be a guideline for the simulation depth of this great and unique study sim.

can you click the HDU turning up or away (keybind I) ?

To be fair and while the manual is showing a western longitude on page 195 as an example, the manual is expecting the reader to know that the earth is a sphere and therefore has 360° and not only 199.9° of longitudes encircling it. So it doesn't really matter if the manual presents an example of east or west longitude. If you don't want to cutoff the North American Pacific coast and the land mass west of Texas and all Asian lands east of Bangkok, so probably the majority of world's population with most of mainland China, Japan, Australia, Singapore and most of Indonesia, you need more than 99.9° of longitude east and west... Hence you need 3 digits of longitude and only 2 for latitude (as the poles are at 90°)...

Did it several times. Don't forget the longitude having to feature 3 digit degree in the front. This is what you would have to enter as coordinates for Beslan airport: N431251E0443534

a trackfile, seriously... baroset.trk

Ok, so far I have a trackfile showing aux tanks on the outer stations. Selecting them doesn't fill the little circles at their respective MPD buttons. Inner stations were occupied with weapons. Or are external tanks on outer stations simply unavailable if there aren't any at the inner stations as well? auxfuelouter.trk

yeah well, the problem with this bug is that you currently can't use this function if your airfield is higher than 1428 ft MSL...

If the CPG selects TADS as sight and PHS as acq src, why doesn't he see that PHS' cued LOS cross in the TADS? Also no cued LOS dot is appearing in the FOR box, unless he also slaves to PHS, which is kind of pointless, as you might want to know the PHS' LOS even without slaving

Activating the IAFS tank on on the MPD Fuel format so far works when done right from the startup. If you add other external fuel tanks than things *can* get mixed up. I had cases when only any external fuel tank refused to accept its activation on the fuel page, sometimes even the IAFS rejected the button press in such configurations. I guess you need a trackfile on it. This may take a while. Yet wanted to report in advance to invite others experimenting with it and add to this report.

Thanks!

I see, so it's like a virtual scope frame? Would it automatically disappear the moment no emissions are detected (or ASE is put back to standby)?

HMD - is set by default FCR - not (yet) implemented TADS - not available for PLT as per the manual link - no idea what this does, doesn't show any obvious effect

This rectangular green outline is appearing out of nowhere during my startup configuration checks. I don't know what it's telling me and I can't make it go away...

Currently the T1, T3 and T4 settings for HI and LO altitude alerts and the BARO alt setting reject any input beyond 1428 ft, which incidently is the maximum displayed value for the AN/APN-209 radar altimeter. As this makes sense in regard of setting altitude alerts, it is probably not meant to also affect the BARO alt setting, so maybe you have to review the constraints for this setting and disconnect it from the radar altimeter display limit. It's easily reproducable. So do you still need a track file on this?

No, simply visit https://www.digitalcombatsimulator.com/en/personal/licensing/trial/ and enjoy the

Yes it is.

How much will it help to install a Tucano mod when you would prefer to fly jets in air 2 air combat? How helpful is the idea of avoiding FC3 because it may cause problems to memorize all the keybinds, when in fact you have 2 button boxes and a HOTAS and have actually no issue to find all the switches blindly with your fingers while wearing a VR headset? In my unrequested opinion the topic question isn't the best approach at all into what DCS is or can be. Most of the well thought answers so far were necessarily based on assumptions and personal taste. On the way to gather your first impressions of DCS, you may want to ask yourself: 1) start with a genuine DCS module made by Eagle Dynamics or a certified 3rd party studio or with some unofficial user mods of unknown representation value? Which choice qualifies better to demonstrate what kind of fidelity to expect in this simulator? 2) what era are you interested in? WW2, first jets, cold war classics or the rather modern stuff? Each might give you totally different results during your first steps in DCS. 3) Air to ground? Air to air? Helos? Everybody has a different itch. Which is yours to scratch? 4) How well are you prepared for aviation in general? Is this your first contact? Do you have some experience, even expectations? What is your hardware performance offering? How far are you invested in peripheral controls? ED is offering a very customer friendly trial system. I'd strongly suggest to make intense use of it. If you do, you will find answers to all the questions above and even to the one in thread topic. Besides, even if VR flying might be an obvious goal, consider to get into this without VR first. If you are proficient in a module, then put on the VR set.