Panzertard

You guys are too funny. *giggles* Anyway, just a heads up regarding 'pings' in DCS. Pings in normal computer/windows terms reffers to ICMP packages being sent to a destination, and returns back again. ICMP is not the same as TCP nor UDP. DCS uses UDP and TCP to maintain a connection with a server. 'Ping timeout' in DCS often reffers to UDP packages being lost. 'High ping' often means it takes a bit longer for the UDP to reach you. UDP is meant to be quicker than TCP, but also a bit more unreliable. It is not possible to use ICMP to really tell wether your DCS will be able to connect or not. DCS doesn't require ICMP to be working. DCS requires UDP and TCP to reach the host server and back again. Summary: - high ICMP ping latency may tell you that it takes time to do a roundtrip, and you may experience problems - lack of ICMP doesn't mean you cannot play on a server. You cannot conclude anything by the 'lack of ping'. - reaching the server using ICMP ping doesn't mean you will be able to play there. - getting excellent ICMP reply does not guarantee a stable connection with a DCS server.

Also, don't forget the GUI documentation. Page 93 and onwards, ME.

Alt 1: Use the 'Go Advanced' button beneath the quick reply box, and then find the Manage attachments button a bit lower down on the advanced page. There you will be able to updload an attachment to use in your post. Better suited for larger bits of code. Alt 2: Code snippets. Copy and paste code into you post, and use the 'CODE' block tag in the 'Advanced' mode editor. The Code-tag is the # button on the Edit-toolbar. This is Coded text Suitable for small amount of code.

Nevada secrets; http://forums.eagle.ru/showthread.php?t=71156&page=2

Okai, I updated the OP to avoid more confusion.

Okai, just taking some notes here. .\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit\command_defs.lua PlaneNavSetFixtakingMode = 457, .\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit\PVI\PVI_commands.lua {command = Keys.PlaneNavSetFixtakingMode}, Hm. Arcade mode has a post-init LUA-file. .\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit\ARCADE\arcade.lua Some code there, which we may be able to decipher. function post_initialize() local [b]weapon_interface[/b] = GetDevice([b]devices.WEAP_INTERFACE[/b]) local laser_ranger = GetDevice(devices.LASERRANGER) local cpt_mech = GetDevice(devices.CPT_MECH) [b]weapon_interface:performClickableAction[/b](device_commands.[b]Button_1[/b],1.0); Perhaps we could make something like this work: pvi_interface = GetDevice(devices.[b]PVI[/b]) pvi_interface:performClickableAction(device_commands.[b]PlaneNavSetFixtakingMode[/b],1.0); You may need to put it somewhere in .\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit\device_init.lua Okai, enough digging in LUA for now. You're on your own. :)

Gupyzer0, you may not have noticed this: About Flaming Cliffs 3... by Wags.

1. It's the "“И-251В – ПРОЛ” (INU fix-taking method)"? 2. Is it the "“АП” (Emergency radio receiver) switch"?

"Cold at rampstart" is probably a correct term I guess?

From a few Aircraft disaster programs on Nat Geo, there's been a few rundown of similar situations like this: - Left & right airspeed indicators wrong/not showing the same data. - Left & right ADI not showing the same data. - Overspeed warnings + Stall warnings. - Stick shaker indicating stall. - Autothrottle pulling back. - Autopilot turning off. So what system is telling the thruth - which one should you trust? What do you do next? It's probably easy to see in hinsight.

Not sure, sorry. I just remember similar request regarding the UV-26: http://forums.eagle.ru/showthread.php?t=37116

Ah, so the initial startup position of these switches is not to your liking - you want to set it to another setting when you start the chopper? Now I get it - yeah, hm, probably something you can tweak in a LUA file. Okai, I think this is a good place to start: \Ka-50\Scripts\Aircrafts\Ka-50\Cockpit

Then you don't have 1.0.2 - it would say so. You can get 1.0.2 here: http://www.digitalcombatsimulator.com/en/downloads/patches/dcs_bs_patch_1.0.2_en/

Conflicting feedback. How to decide what information which is correct - and what information is false. Quite dangerous situation - a wrong choice and you may end up in a situation you cannot get out of.

Sorry, I still don't understand. Call me slow. Whats the issue at hand? Switches not working? Feature in game not working?

Okai, thread carefully - we don't need to get personal. Constructive comments please.

Use the Mission Editor, About.

What situation? What switches? Why lua or encrypted? Please elaborate.

Not that we're aware of any steam issues, no. And welcome to the community. o7

A slight derail - but since this flight hasn't been the only one going down due to sensor-problems: - I don't understand why the aircraft industry hasn't been more concerned over the fact that these sensors, monitoring and automation is now critical to stay airborne. The combine factors of: a) Automation of a lot of the standard procedures & operations. b) Putting either a computer or a human to monitor it (Airbus vs Boeing) - making decitions based on flawed sensors. c) Not having implemented sufficient faulty sensor detection d) Not sufficiently training pilots to detect faulty sensors together with safe standards to stay airborne even with critical sensors going offline. I hope the industry learns - and quickly.

No, lockon is too much of a legacy product - I've never gone near the code there. Sorry. Normally you would get the answer by calling a function either because you changed mission "load_mission" or and event "on_mission" and you could hook onto these. But I doubt current mission name is stored in a 'global variable table' aka _G due to access restriction from another LUA environment.

Okai, been working on moving all custom config files out of DCS install, to the \Saved Games\DCS Warthog\ServMan3 Somewhere in time, this means it'll be easier to load / change server behaviour on the fly - having multiple custom configs. Somewhere in time, just another requirement for me to support different server-config depending on the mission you run.

Hello Stadius. For a workaround, while learning keys: - I made my own print (A5 double page on A4, duplex print) and printed out a keychart to have on my desk. There's and "A-10C Key Command List.xls" in the installation directiory under the \Doc folder. Thats the one I used. But being able to adjust key assignments while in the sim, yes, that would be nice.

Here's an official update which involves US boxed versions: http://forums.eagle.ru/showpost.php?p=1208510&postcount=17

OK, so far: - 'Russian HeliSEAD' lacked the "CAS" task, you had removed this Auto-created task for the group. Hence it wont attack. - Same for your CAP group. To fix such issues: - Select the group. - Check Advanced WPT Actions for WPT0 - If no Auto-task is assigned for such tasks as CAS, CAP and similar: FIX: See image. You can find info about this in the manual "DCS A-10C GUI Manual" page 93 and onwards. p.123 for you. :) Additional: If you expect AI to attack soldiers, they might not see them. AI has same limitations to sport units as a human pilot when you use such 'auto tasks' If you need them to attack a specific group, assign a Action for a waypoint - and set 'attack group / attack unit'. Then they will attack regardless if they should have spotted them or not. But never remove the auto-assigned tasks, unless you're looking for another specific behaviour.