Chump

The original line is found in: <DCS>\Config\Input\Aircrafts\common_keyboard_binding.lua:109 {combos = {{key = 'L', reformers = {'LAlt'}}}, down = 3256, cockpit_device_id = 0, value_down = 1.0, name = _('Flashlight'), category = _('View Cockpit')}, For some reason, this does not seem to be "common" in all aircraft. I would guess that common device ID 256 is hidden in a DLL, since I've yet to find it defined in LUA?

Bought it in anticipation, waiting on bug fix to start playing. :)

Add this to the end of <DCS>\Mods\aircraft\A-10C\Input\A-10C\keyboard\default.lua or <DCS>\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard\default.lua: {down = 3256, cockpit_device_id = 0, value_down = 1.0, name = _('Flashlight'), category = _('View Cockpit')}, and then just set a key bind for it in Settings. I'm sure there are other ways to achieve this, or maybe even an OVGME mod somewhere.

I got it working. I do not take credit for the original script, and could not get in contact with the author. If anyone has an issue with this being posted, I will remove it. https://github.com/chump29/DCS_Mod/tree/master/CDU%20Wind https://github.com/chump29/DCS_Mod#briefing-addons

I just updated to 20H2 today and do not have any problems. Log file?

Ensure that you have the Sync Cockpit Controls option checked. This usually fixes the issue for me.

Nice setup, bro! I can't have nice things. :( Looking forward to flying with you soon!

I do not think you can uninstall A-10C (original). I believe that they might share some code. https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-a-10c-ii-tank-killer/290173-make-sure-a-10c-1-is-installed-before-installing-upgrade

\DCS World OpenBeta\CoreMods\aircraft\A-10\Liveries\A-10CII is where the new skins are located. I made a junction between the two A-10C directories so that I can use the old skins on the new plane. It works, mostly, as Grimes mentioned.

Some of the HOTAS commands have changed (check out the new manual in the A-10C_2 Docs folder). There is no more TGP boresight command, unless you turn the TGP to standby then back to A-G.

Have you created a template/unit/group in the mission named RAT_A320-1?

If you are using MOOSE, they can be found @ https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Wrapper.Airbase.html##(AIRBASE).Syria

You might try updating to the latest version of MOOSE https://github.com/FlightControl-Master/MOOSE/releases/tag/v2.5.1

Excellent information! Can you explain how you obtain the offset value a bit more?

https://www.faa.gov/documentLibrary/media/Advisory_Circular/150-5340-18G.pdf Page 1-5 concurs with your awareness of runway signage. Maybe they do what they want over there!

According to the flight manual, "When in the up position, the flaps are closed using aerodynamic pressure."

@SnowTiger, delete these files from your system: <DCS Directory>/coremods/aircraft/fa-18c/shapes/fa-18c_lod4.edm <DCS Directory>/coremods/tech/uss_nimitz/shapes/nimitz_cvn_73_lod_1.edm <DCS Directory>/coremods/tech/uss_nimitz/shapes/nimitz_cvn_71_lod_1.edm <DCS Directory>/MissionEditor/modules/mul_chat.luaThen run a repair (DCS_Updater.exe repair) again. I would suggest that you upload your <DCS Directory>/autoupdate_log.txt next if you are still having issues. This will tell us if the repair actually detected and downloaded the deleted files.

2020-09-07 18:33:39.488 WARNING SECURITYCONTROL: IC fail: models/fa-18c_lod4.edm @ coremods/aircraft/fa-18c/shapes 2020-09-07 18:33:39.488 ERROR SECURITYCONTROL: Manifest check failed for resource 'models/fa-18c_lod4.edm' 2020-09-07 18:33:44.257 WARNING SECURITYCONTROL: IC fail: models/nimitz_cvn_73_lod_1.edm @ coremods/tech/uss_nimitz/shapes 2020-09-07 18:33:44.257 ERROR SECURITYCONTROL: Manifest check failed for resource 'models/nimitz_cvn_73_lod_1.edm' 2020-09-07 18:33:44.820 WARNING SECURITYCONTROL: IC fail: models/nimitz_cvn_71_lod_1.edm @ coremods/tech/uss_nimitz/shapes 2020-09-07 18:33:44.821 ERROR SECURITYCONTROL: Manifest check failed for resource 'models/nimitz_cvn_71_lod_1.edm'Looks like you have some modded/invalid model files. There is also a script error from an invalid file: 2020-09-07 18:35:41.468 ERROR Lua::Config: Call error onGameEvent:[string "./MissionEditor/modules/mul_chat.lua"]:705: attempt to index field '?' (a nil value)You might try to do a repair again.

The invalid files should be listed in your log file also.

What's wrong with os.time() in LUA?

No order status on the website. Did you pay for tracking?

@glide, try something like this: https://www.timeanddate.com/moon/georgia/batumi?month=6&year=2016

Wouldn't you need to alter MissionScripting.lua? --require = nil

The English manual states (page 79): [b]REV Mode[/b] The reverse localizer mode is selected by pressing the REV push-button. It allows to fly a back course approach and it can be used with both pitch modes, PAT and ALT.

@shu77, mine took around 50 days due to absolutely nothing that I could reasonably figure out. It took two days to cross the ocean, then sat a state away for over 45 days. Even the Post Office did not know why it hadn't cleared Customs. Customs said they'd never heard of it. I thought it was over. Then one day, it simply showed up, no further tracking updates. I don't know who/what to blame either, but Deltaalphalima1 is not it. Patience, my friend. It's on its way, and it's worth it!