-MadCat-

Well, the Ka-50 could easily keep up. And if the Mi-8 doesn't give it all, the UH-1 can too. Unfortunately I have no idea about my current fps in mp, don't know if it would be a slide show for me with all the Mi-8. And I have to confess not having too much experience with the Mi-8 either, would feel lot more comfortable in Ka-50 or UH-1. Greetings MadCat

Changelog for this thread can be seen at the end of the first post. Hi everybody! Motivated by the current discussions about the controls and ED's recent introduction of diff.lua files, I think we can help ED to give us more convenient controls by default. As I'm not the greatest .lua editor, but managed to implement some controls myself, I'm sure out there are people who know a lot more about .lua edits. Hence, this thread is a try to collect .lua edits that: Add commands that can then be normally assigned in the controls options Create stateful commands that place a switch in 1 position and 1 position only Are not of the press/release type (would defeat #2) Sole exception for #2 and #3 is, if the created command actuates a button or switch that is spring loaded by design [*]Are easy for ED to just put in the default.lua files (since the different working now) [*]Are confirmed working How to use this : Only use Notepad++ to edit dcs files Copy and paste the desired commands into the default.lua of every controller you want to use them with. (DCS World/Mods/aircrafts/ "aircraft" /Input/ "device" /default.lua) Add the code before the last 2 curly brackets (keyboard .lua files) / before the last curly bracket prior to the "axisCommands" section (joystick .lua files) .lua files are read per line, make sure each line starts with " { " and ends with " }, " (you can add comments, that are ignored when the .lua is read, by starting a line with "--") If in game a control column turns completely empty, don't panic, there is just a " { " or "}, " missing, a typo or obsolete spaces in the according default.lua (search in the code you added last) Assign a button to the commands in game and enjoy :) Before I get going: If you are rather looking for toggle commands (up & down commands in one button), you may want to have a look at GregP's thread ->here<-. He also links to other helpful threads about toggle actions. I'll go ahead and post what I managed to do: Working perfectly: Ka-50 : Burst length switch: {down = 3004, cockpit_device_id = 12, value_down = 0.2, name = "Burst length - Long", category = "Ins Weapons Status and Control Panel PUI-800"}, {down = 3004, cockpit_device_id = 12, value_down = 0.1, name = "Burst length - Medium", category = "Ins Weapons Status and Control Panel PUI-800"}, {down = 3004, cockpit_device_id = 12, value_down = 0.0, name = "Burst length - Short", category = "Ins Weapons Status and Control Panel PUI-800"}, Engine protection system:{down = 3014, cockpit_device_id = 4, value_down = 0.0, name = "Engine Protection - Dust", category = "Ins Overhead panel"}, {down = 3014, cockpit_device_id = 4, value_down = 0.5, name = "Engine Protection - Off", category = "Ins Overhead panel"}, {down = 3014, cockpit_device_id = 4, value_down = 1.0, name = "Engine Protection - Anti Ice", category = "Ins Overhead panel"}, Laser range finder:{down = 3001, cockpit_device_id = 11, value_down = 1.0, name = "Laser - Standby", category = "Ins Targeting Mode Controls Panel PVR"}, {down = 3001, cockpit_device_id = 11, value_down = 0.0, name = "Laser - Off", category = "Ins Targeting Mode Controls Panel PVR"}, Gun auto tracking / gunsight:{down = 3017, cockpit_device_id = 12, value_down = 1.0, name = "Cannon Automatic Tracking", category = "Ins Targeting Mode Controls Panel PVR"}, {down = 3017, cockpit_device_id = 12, value_down = 0.0, name = "Cannon gun sight", category = "Ins Targeting Mode Controls Panel PVR"}, Gear lever:{down = 3001, cockpit_device_id = 34, value_down = 1.0, name = "Gear lever down", category = "Ins Forward panel and gauges"}, {down = 3001, cockpit_device_id = 34, value_down = 0.0, name = "Gear lever up", category = "Ins Forward panel and gauges"}, Rotor anti-ice:{down = 3013, cockpit_device_id = 4, value_down = 1.0, name = "Rotor de-icing system On", category = "Ins Overhead panel"}, {down = 3013, cockpit_device_id = 4, value_down = 0.0, name = "Rotor de-icing system Off", category = "Ins Overhead panel"}, Landing light:{down = 3001, cockpit_device_id = 44, value_down = 1.0, name = "Landing light On", category = "Ins Landing Lights & Voice Warning Panel"}, {down = 3001, cockpit_device_id = 44, value_down = 0.5, name = "Landing light Off", category = "Ins Landing Lights & Voice Warning Panel"}, {down = 3001, cockpit_device_id = 44, value_down = 0.0, name = "Landing light Retract", category = "Ins Landing Lights & Voice Warning Panel"}, UV-26 Dispenser Board:{down = 3002, cockpit_device_id = 22, value_down = 0.0, name = "UV-26 Dispensing board Left", category = "Ins Countermeasures dispensers UV-26"}, {down = 3002, cockpit_device_id = 22, value_down = 0.1, name = "UV-26 Dispensing board Both", category = "Ins Countermeasures dispensers UV-26"}, {down = 3002, cockpit_device_id = 22, value_down = 0.2, name = "UV-26 Dispensing board Right", category = "Ins Countermeasures dispensers UV-26"}, P-51D (TF-51D) : Gear lever (by Olethros):{down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = 'Gear Up', category = 'Systems'}, {down = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = -1.0, name = 'Gear Down', category = 'Systems'},Fw190D-9 : Commands for the Fw190D-9 can be found in post #17. Almost all commands were adopted by ED and thus I deleted them from the post. If the remaining two turn out not to be true to the real plane, they will be deleted too. F-86F : Commands for the F-86F can be found in post #20. UH-1-H : Commands for the UH-1H can be found in post #3. Mi-8MTV2 : Commands for the Mi-8MTV2 can be found in post #25 and post #26. Bf109K-4 : The (very few) missing commands for the Bf109K-4 can be found in post #36. Almost working: Ka-50 : Cut-Off Valves (commands move the mouse clickable boxes correctly, but move the cockpit levers themselves both ways):{down = 3009, cockpit_device_id = 4, value_down = 0.0, name = "Cut-Off Valve Left Engine Close", category = "Ins Engines start-up control panel and levers"}, {down = 3009, cockpit_device_id = 4, value_down = 1.0, name = "Cut-Off Valve Left Engine Open", category = "Ins Engines start-up control panel and levers"}, {down = 3010, cockpit_device_id = 4, value_down = 0.0, name = "Cut-Off Valve Right Engine Close", category = "Ins Engines start-up control panel and levers"}, {down = 3010, cockpit_device_id = 4, value_down = 1.0, name = "Cut-Off Valve Right Engine Open", category = "Ins Engines start-up control panel and levers"}, . . . . . . So please, dear fellow members, let's help ED to help us: Please post .lua edits that are conform with points 1-5 (see above) Please post .lua edits that are almost working too (like I did with the Cut-Off Valves for the Ka-50, maybe with a little help we can get those to work properly) Please don't post edits that don't work at all Please keep discussions about controls to other, already present threads Please use the following template for posting your edits Working perfectly: "aircraft": "switch": ".lua edits" Almost working: "aircraft": "switch" ("short explanation"): ".lua edits" . . . In case I work out more working .lua edits, I will update this post. I will also update the first post with all the posted edits from time to time, to maybe make this into some kind of ( ? stickied ? ) "library", until ED gives us more detailed controls. Edit away and show ED our direct support! :thumbup: Greetings MadCat Changelog: 03062014 - TF-51D commands added (Fuel boost pumps) 08062014 - Ka-50 commands added (UV-26 Dispenser Board) 07082014 - Fw190 commands added (too many to name all) ; UH-1 commands added (Post #3) 08082014 - F-86F commands added (Post #3) 09082014 - F-86F commands added (Post #3 (Rockets Release Selector, thanks Highwayman-Ed) ; obsolete spaces in codes removed ; codes wraped in code-windows ; Fw190 command added (Rocket Emergency Release Cover Close) ; "How to" added 10082014 - All Fw190 commands moved to post #17 ; more Fw190 Commands added 11082014 - All F-86F commands moved to post #20 ; more F-86F commands added (thanks LiveBait) 11082014 - UH-1 commands added (Post #3) 12082014 - Mi-8 commands added (Post #25 & #26) 13092014 - Merged P-51D and TF-51D ; P-51D/TF-51D command added (Gear lever) (thx Olethros) 19092014 - Deleted Fw190 and P-51D/TF-51D commands that have been made default by ED 10122014 - Commands for Bf-109 added

Often times and for almost any business, too much diversity does more harm than good. ED should stick to its core competences, developing aircraft with the highest fidelity possible. About the lots of "hobby" moders, too many cooks spoil the broth. Their work, even if absolutely excellent at first glance, still needs to go through ED's quality assurance, what again occupies recources. And in the end, only a very small percentage might stand up to the ED standard. Sorry, but I voted for the aircrafts, that is what I am here for, the best flight simulation available. Greetings MadCat

Don't have the time to take new ones right now, so will just try with some old ones ^^ At times he'd like to be a tanker.. You cannot hide, now get to work, lazy! The Zombie UH-1 2 skids are for beginners UN Coast Guard on duty Good luck to everyone ! MadCat

Lots to tell, so I'll get right to it, some good, some bad. First off, the 100% fresh reinstall didn't do much, I installed from scratch, just installed the UH-1 with world, and worked from there, no old files whatsoever. Created a new mission, didn't bother to edit any units, just places a UH-1 and a cargo, tried, and it worked perfectly, no crash. Then I got an idea, the default nationality is "USA" when you first place new objects. Changed UH-1's nationality to "Germany", tried, no problem. Changed cargo's nationality to "Germany", tried, crash. After that I got curious and tested all nationalities for cargo, here is what I found: USA works perfectly in all aspects. Russia and Ukraine don't crash the game upon unhook, yet once you unhooked the cargo it is not available anymore for another pickup. Every other nationality for the cargo results in a crash upon cargo unhook. Manually unhooking in the air doesn't crash the game either, regardless of nationality, yet cargos get destroyed as expected. All hooking and unhooking was performed from a hover and the cargo standing on the ground, just used automatic unhook this time around. If those findings can be confirmed I'd say it's an official bug. On a second note: I managed to crash your mission that way too, BIGNEWY, as well as the unavailability with Russia and Ukraine. Then tried with an old mission of mine, same results. Eager to hear from you, BIGNEWY :) Nice greetings MadCat

First repair (actually the 2nd, did one past night already) no luck. Next repair I deleted the "Mission Editor" folder in the main directory and at random the "Scripts" and "distr" folders too. Repaired, still crashing on a 100% freshly created mission... :cry: Will try a 2nd 100% reinstall tomorrow, then report back, have had my share of crashes for today... Thanks so far MadCat

As I already said in another thread: There are underlying switch states within the simulation for all switches, in all positions, for all cockpits. Just an example for the Ka-50: There are no seperate commands for the short, medium, long burst, just 1 command to circle the switch about its positions. I edited those definite positions in via .lua, they work and I now can assign button "xy" to short burst, and it will set the switch to short burst, no matter the previous position. If it already is in short burst, the keypress does nothing, but at that point my 3-way switch is in that position already anyway. For every position of every switch in every cockpit, the simulation has to know what to do, so there absolutely needs to be a value assigned to all of those. All those values need to be fed through to the GUI so we can assign them directly. All those commands in the "default.lua" and everything that we changed in the .diff files would be the holy grail. The simulation reads the default first, then overwrites everything we changed (with the .diff files). At that stage, ED only updates the "default.lua" and everything we change from that point gets added to the .diff files, which remain untouched by ED. No need to ever rewrite all our controls, just update them with what gets added by ED. My 2 cents, greetings MadCat

Ok, here I go again. My current version is 1.2.8.27203. A manual update didn't bring any newer version to light. Tried your mission, no problem. Tried mine again, crash... Tried yours, no problem. Created a completely new mission, crash. Tried yours, did 5 consecutive pickups and unhooks without a problem. Created yet another totally new mission, again nothing in it just a UH-1, and a cargo, crash upon cargo touching the ground (auto unhook) or me unhooking the cargo on ground manually... Looks like my mission editor creates corrupted missions, I'm close before another 100% reinstall... What's your sorcery? :cry:

It's your birthday and you bother with other people's problems, that must be pure dedication. I'd say you deserve a day off ;) Mission file is right at hand, freshly created today within 1.2.8 release version to rule out problems with older missions. CARGO TEST.miz

Track-folder in saved games is empty, none created, and after I clicked "OK" for the notification that no debriefing could be generated, I get right back to the mission editor, no chance to manually save one. :( Besides that, Happy Birthday, BIGNEWY ! :yay::clown_2::juggle::balloon:

Hi BIGNEWY, didn't expect that fast of an answer, thanks a lot! He goes the logs folder out my saved games directory. Thanks again ! MadCat Logs_Cargo_Crash.rar

Hi everyone! My game crashes all the time I let go of a cargo. Manually releasing in in air works fine, but if the cargo touches the ground manual and auto unhook result in the game crashing, every time. My install of 1.2.8 is 100% clean, freshly installed from scratch, new mission created, no mods, no old configs, nothing old. Can anyone confirm if I'm not the only one with that problem or if I am. Game crash is reproducable every time, mission briefing cannot be loaded then and I end up in the mission editor. Greetings MadCat

AFAIK the current behaviour is correct. The benefit to seperate collective from cyclic control mechanism is, that when you apply full cyclic in whatever direction, you still have full available servo travel for the collective control as well. If both controls are to be handled by the swashplate alone, you may have trouble to apply even more control deflection if you already moved the servos to their extremes with full cyclic input. So for one and the same servo you'd need to allocate a certain movement range for the cyclic and another additional for the collective control. The servo needs enough of a movement range for both maximum deflections at the same time. Seperating the controls just is the easier design. Greetings MadCat

Just to further support sobek's point. Excerpt from an F-51D Handbook: Am "cleaning out" my engine all the time like that, never had any trouble with the one minute max power and engine always runs smooth (provided you operate it within limits the rest of the time). AFAIK, carburetor iceing isn't modeled yet. Greetings MadCat

Hi everybody, i didn't find an appropriate thread like a Ka-50 wishlist or questions for features. If I missed such a thread please point me to it or just merge this with it! My question (or wish) is, if it is possible to add 2 (already existing things) to the Ka-50 as well: Opening and closing the door with the mouse. Ka-50 is the only (DCS level) aircraft where the cockpit cannot be closed and opened by mouse. Ability to set engine conditions in the mission editor, like it is WIP for the UH-1 and MI-8. In fact this would be nice to see on all current and future DCS level airframes. (No idea how much coding is needed to implement engine deterioration for already existing modules) I think this thread would be smartest to ask for implementation of features that already exist for other modules and "only" need to be "moved" to the Ka-50. If you have other suggestions or opinions, don't hold back! Maybe this brings some fresh paint to our shark :thumbup: Greetings MadCat

DCS never was to provide a complete and coherent war scenario, Wags said that himself. Hence it's futile to complain about modules that "don't fit together" all too well. The "Spitfire in the middle of Strelas" is a problem introduced by the mission builders alone, not by ED. But to comment, why I voted "No": We need more different airframes instead of variants of already existing ones. Another variant of the UH-1 can in no way whatsoever bring as much enrichment to DCS as a totally new airframe would. My 2 cents. Greetings MadCat

Schade das zu lesen :( Verständlich aber allemal, wenn Geld ausgegeben wird für ein Hobby, aber nichts vernünftig bei rumkommt. Permanent 550+ KIs laufen lassen klingt enorm. Ich weiss nicht ob sich an der Stellschraube was machen lässt, aber vielleicht ist leichte Besserung zu erreichen wenn man das etwas "ausdünnt" und Einheiten rausnimmt. Nur mal zum Beispiel, bei dem kleinen Airfield nahe Kobuleti stehen (geschätzt) 25 LKW zum "abknalln". Würden es nicht auch 20 oder gar 15 tun ? Wenn man hier und da etwas abspeckt, lassen sich so sicherlich jede Menge Einheiten einsparen, ohne dabei die Mission merklich zu beschneiden. Ist natürlich nur eine Idee und keine Ahnung wieviel Stabilität das bringen würde, wenn überhaupt. Auch wenn ich in letzter Zeit wieder weniger Freizeit für's Fliegen habe, wäre es sehr schade sich wieder neu nach Freeflight-Servern umsehen zu müssen. :cry: Drücke fest die Daumen und sage vielen Dank für all die Bemühungen ! MadCat

I don't think the problem is all about certain joysticks or some like that. As I already described -> here <-, I came to believe there is something wrong with the trimmer in the sim. That is my opinion, based on knowledge and observation. So everybody please don't start to hate or telling me I'm doing it all wrong and have no idea how to fly it, which I know quite well how to. I've PMed Evil already with my concerns, but didn't get an answer yet. Greetings MadCat

Turn the helicopter in the indicated direction and then yaw left and right. When the needle deflects in the opposite direction of the turn, you fly towards the station. If it deflects in the same direction, you fly away from the station. Greetings MadCat

Currently bugged and subject to be fixed. See here: http://forums.eagle.ru/showthread.php?t=117921 Greetings MadCat

Look here ! Maybe it's worth getting that thread sticky? http://forums.eagle.ru/showthread.php?t=117551 Greetings MadCat

Sad to see that officially confirmed bugs have never been fixed up to this point.:cry: Greetings MadCat

Sorry to disappoint: How does the trimmer work and how am I supposed to use it? Now we bring together, you saying the "oversteer is correct", and from an official source that "trimming in discrete presses" is advised to real pilots. That would mean, the real pilots do have the same oversteer as when we trim in discrete presses. How come I highly doubt that, until confirmed by an official ? !:music_whistling: I'll give you that we don't know how the real trimmer works (on the software level). I was about to write a rather long thought experiment, but then noticed another little detail in that linked post. Now how I understand that quote, is that the press of the button does nothing else than to take away control forces. However it does not interfere with the 20% control authority in any way. Only when it is released, the new center position should be updated to the AP and the control forces are reengaged. The control authority is never ever disengaged at any point, only updated. That would mean, temporarily disabling the AP authority upon pressing the button is all wrong to even begin with! Doesn't this make more sense than what we have now ? Switching from "compensated controls" to "raw stick input" upon pressing (and holding) the trim button ? Think about it. And I would really appreciate an official statement on this! There are so many misconceptions about the Ka-50 trim system out there, and this may be the cause for many (or even all) of them. Greetings MadCat

If this really is the cause for the "trimming too far" when using just one click to trim, I wonder why ED doesn't fix this? Should be so easy to do, the game already knows how much authority the AP applies (and therefor how much you "oversteer" to get to a desired cyclic position). That known information can easily be used for the new center position calculation. (displaced joystick position) - (AP authority currently applied) = (new center position once the trim button is pressed) Tada, we got rid of the trim "oversteer", easy isn't it ?! Please ED have a look into this issue! Greetings MadCat

This! You fly the helicopter all alone, no interference by the autopilot yet still dampening is active. In combination with the PVI-800 you can consider the FD as some kind of "manual Route mode", you fly the helicopter and the computer directs you with the HUD indications. Greetings MadCat