itn

FIX has been working for years. However, if GPS is enabled, it over time would ”override” your manual FIX. Some people have observed this, but haven’t always realized what exactly happens, and then have claimed ”FIX does not work” here in forums. In reality it’s often just that GPS overrode the FIX they did. In essence, at least some versions back doing FIXes in GPS environment was pretty useless. In non-GPS environment they’ve worked just fine.

The special options for automatic trigger safety and gear lever guards are absolutely useful and justified because we the players mostly work with simple HOTAS systems, not simpits nor a real plane. Those two options are and should be a player preference to work around physical control limitations that would never be an issue IRL, but are definitely an issue and a hindrance with basic HOTAS controls. I'm not sure I understand the change that was made to these options. Were the changes necessary for a MP sync issue in BE variant? If not, I'd really appreciate returning those two options to be strictly a player preference.

See the screenshot in darkman222's message above. The "FILE" text is a menu so just click on it to open. It's confusing everyone . You can just join a MP server, open DTC, edit it as you want. Then from FILE->Export the DTC file. Next time you connect to a server, open DTC and FILE-Import.

+1 for the tab to move to next cell, it's a basic UI functionality that should be there.

On hot ground starts it might be more debatable, but even then in my opinion it clearly should be autoloaded in avionics, as it should in air spawns. Some points to consider: A DTC would be loaded in the same process/checklist as e.g. avionics power and INS alignment. Those are all done on a DCS hot start, and so should the DTC. In general, a hot start in DCS is a way to skip the necessary cockpit simulation and to just expedite getting in to the air. Basically what I'm getting at is a "hot start on ground" is not about the pure engine startup. It's about the jet being ready to taxi. When you have a DTC this means the DTC is entered and loaded in the avionics. To me this clearly favors autoloading the DTC in avionics as what the user expects and what should happen on all types of hot start. Basically it would simulate the pilot loading DTC during the startup just like the startup manual/checklist says, and a hot start jet is ready to taxi.

In case you didnt’t know: The FILE on top of DTC interface is a menu button. Click on it and you can export a DTC file, which you can then similarly import later in any mission from the FILE menu. I agree these should be available automatically in the same way loadouts are, instead of having to import the file every time.

I don’t think that’s what I’m after. Hot/air starts should have the DTC loaded in the avionics without going through DTE or MUMI page. This should happen regardless of if a mission or client DTC is used. A mission maker obviously cannot have my personal DTC available in the mission or set as default. So say I join a random MP server and during slotting on an air spawn I load my personal DTC. I should not have to use DTE/MUMI because I would have done that as part of the startup procedure. It is least surprising to just have the DTC autoloaded in the avionics (DTE/MUMI).

This. It should look like a menu which it is. Now it looks like a label.

To be fair, in addition to CMDS programming, the DTC has comms presets.

Hi, I believe it would make sense for DTC to be automatically loaded into the jet avionics when spawning hot, or at least when spawning in air. Especially in air you're sort of pretending you already did your startup, takeoff etc. As part of startup procedures you would have loaded the DTC just like you would have started the jet and all sorts of systems that are on when you spawn hot or in air. Following the principle of least surprise, it would make sense for the DTC to be automatically loaded in the jet without needing to load it in the avionics. Thanks, itn

For the first one, AFAICT it's actually correct as is. After starting the count, second INC depress merely freezes the display, not the count. Third INC depress unfreezes the display, after which the display returns to show the count that has continued in the background. Unless, of course, you have some more relevant data for the DCS variant or something like that.

I wouldn't be surprised if this issue is similar to the feet/metric conversion/rounding logic issue I reported in Mission Editor a while back (and which was then fixed). Basically an error in rounding logic when converting between internal metric representation and others. In the Mission Editor it was about feet/metric conversion, but this might be similar.

Check the DCS F-16C Early Access manual (pages 200, 208-211) or Chuck's Guide (p. 701-702). Not sure what manual are you using, but check ED's and Chuck's and the MGRS thing is clear: It's available on steerpoints 21-25.

+1 yes please. Give the mission makers options to restrict some of these capabilities. It would enable historical and otherwise restricted environments.

Even if that's the reason for how it currently works, surely it should be classified as a bug as explained by OP. Sync cockpit controls enabled Physical control bound to a cockpit control The aforementioned cockpit control not synced