etcher

I'm actually pretty happy with the system so far. The "on/off requires two button" is easily solved by editing "default.lua". Agreed, it's a bit of work, but once it's done it's done and the end-result is something that very precisely does what you want it to do. Besides lua editing, there are so much possible solutions out there (Target, HELIOS, XPadder, any kind of "smart" keyboard/mouse/*thing with buttons*, etc.). I frankly am convinced that there already are tons of solutions for every concern raised in this thread, and that among them anyone would be able to find one that satisfies them fully. IMO it's a good thing that the system is as modular as it is, and that every 3rd party is able to do as they please. We would lose so much of the potential for pit-building, or even simple tweaking, if everything had to "fit in the box". There is so much to learn from the other people's approach to a problem, and being able to change things on a very low level gives way for all kind of tinkering. That is something I'm very fond of with DCS =) (also @ED: thank you so much for the diff.lua, I still have the occasional nightmare about the update process before that :beer:)

I vote Foxbeard, PeterP and Devrim

The modified "default.lua" does not change anything by itself, so it's pretty safe to use it. It actually makes new command available for you to map to your controller. Those command will be added to the default "settings/control" configuration page in the DCS interface. All you have to do is map them to a key (keyboard, stick, whatever, really) as you would map any other command in DCS. That's about it =) Let us know if you need more info !

It is enforced server-side, in the .miz options. See http://forums.eagle.ru/showthread.php?t=130341

The engine cutoff is already a "two-in-one" kind of command. If you go in the office and depress "LWIN+LSHIFT+E" you'll see the engine cutoff actually go down, then up. Now if you keep those keys depressed, you'll see them toggle back and forth indefinitely, which is the behavior described by Colseg. Thing is, the two actions are a toggle. Every time the switch is both engaged/disengaged (up and down in the lua), the throttle alternates between idle and cutoff. There's no actual way to tell the throttle to go idle/cutoff, at least I wasn't able to find one in the command_defs.lua.

Holy smokes you're right, thanks a lot for the heads-up. Here's a pastebin version: http://pastebin.com/7EeVatam. I'll remove the code from the original post. Sorry for the trouble =) EDIT: btw Tetra your RWR mod is *awesome*, I love it, been using it since it's out, thanks for that too :beer:

Sorry to hear that, they're working fine here. Perhaps it is because I added them to the custom "_ALTERNATE" category ? I like to have all my "tweaked" commands on the same page, usually I end up making one per DirectX button anyway, so it's convenient to have them not mixed up with all the rest (default ones). Let me know if I can help you in any way with the issue you're having, I hope you'll find a fix soon :beer:

Here are some I needed too. See this post for a pastebin (safe) version: http://forums.eagle.ru/showpost.php?p=2183447&postcount=31

Did anyone already figure out how to correctly map the throttle afterburner range on the Warthog? I'd like to use the physical "bump" on the throttle to delimit MIL & afterburner range, but I don't know exactly how to approach the issue. TARGET is an option, maybe there's a config file, maybe I'm dumb and missed the obvious :D Anyone got that figured out ?

Actually the problem is with ED. For some reason, and this has been a nightmare for me for years, they keep changing bits here and there, be it folders, file names, and random strings in the config files. This precise one is a back and forth, it went from generic to specific and now back to generic, so, modders, cheers, enjoy ! I understand they're working really hard on making DCSW better, but, frankly, they would benefit a lot from a good, deep, long, meticulous housecleaning. And I remember saying exactly that 2 years ago :D

Thanks a lot!

I posted a very enthusiastic review somewhere up this thread, and this is but an update. 6 months with the MFG, and they're still as awesome as first day. The hardware does not show the beginning of a strain, and I use them for a *lot* of different games (all the time). I honestly have nothing to say against the MFG. IMO they're just perfect, and that's it.

I've been using the MFG for more than 6 months now, and, frankly, they simply are perfect, there's nothing to say against them. Disclaimer: I have no interest, financially or otherwise, into praising this product. It's the honest opinion of a very satisfied customer. The hardware is top notch quality, still as responsive as first day. They're about as modular as those strange mouses nowadays, so the shape can be adjusted to feel just right for you. That being said, there's a limit, obviously, and... oh, that's not even true, there are spare parts that you can get if you want them really far apart. The software gets a lot of updates, and the guy that makes the MFG is both friendly and accessible, while being very professional about his product. This is at least the same quality you would expect from Thrustmaster or Logitech (IMO it's far above), and, as I said, 6 months into it, and absolutely nothing negative to say about it. I use them for a lot of different games; they are marvelous for each and every aircraft in the DCS series obviously, but one can tweak them so much that they can be used in any game that can accept DirectX input, button or axis.

+1

Hey this is great, thank you so much for your work ! So much easier to read your actual attitude while trying to maintain (or get to) a hover than to try to guesstimate it. It's also very nice to be able to know at all time when your wheels are perfectly aligned with the ground, it makes those "hmm do ya think I'd land on that napkin on top of that mug on top of that tower?" type of landing much easier to plan and perform. Bunck of kudos (can't spread rep), much appreciated :beer:

MFG. EDIT: review thread: http://forums.eagle.ru/showthread.php?t=119419

[edit]sniped by Ajax[/edit] If you'd like to dive into lua scripting for DCS, http://wiki.hoggit.us/view/Simulator_Scripting_Engine_Documentation is as good a place as any. http://wiki.hoggit.us/view/Part_1#trigger is a direct reference to the subject on hand. Have fun with the scripting :beer:

Many thanks for your time Mustang, this is a game changer, much appreciated :beer:

This is *awesome* !!! (yes, 3 =)) Thank you so much :beer: I was in the process of making something similar (exactly the same, actually), but I went for an external application, your method is way nicer. Billions of kudos to you, sir !

Kudos for a wonderful job making our skies nicer Mustang, much appreciated ! :beer:

Awesome information ! I'm still struggling with the 1.2.8 and the new diff.lua format, especially with the KA-50. So far, my solution is to append the custom combos at the end of the "\DCS World\Mods\aircrafts\Ka-50\Input\ka-50\joystick\default.lua" file, and map them directly in the GUI. This is fine, but given the amount of work required to make each and everyone of them, I thought I'd better make a simple script that would build them *all* for me, and share the result. Attached to this post is a ~500 lines text files that has every possible clickable_data (except the useless 3 linked to "device_id 0"). I arranged them in a category named "CUSTOM", for convenience. They are labeled "_TOGGLE" when there are but 2 possible values (1 / 0), _3WAY when there are 3 (0.0 / 0.1 / 0.2), and _NWAY when there are more than 3 (up to 34 !). The exact value is added right after the label, for example: { down = 3001, cockpit_device_id = 34, value_down = 1, value_down = 0, name = "CUSTOM_TOGGLE: GEAR-PTR", category = "CUSTOM"}, { down = 3003, cockpit_device_id = 14, value_down = 0, value_down = 0.1, name = "CUSTOM_3WAY: MAIN-ROTOR-PTR_DOWN", category = "CUSTOM"}, { down = 3003, cockpit_device_id = 14, value_down = 0.2, value_down = 0.1, name = "CUSTOM_3WAY: MAIN-ROTOR-PTR_UP", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0.1, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0.1", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0.2, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0.2", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0.3, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0.3", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0.4, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0.4", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0.5, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0.5", category = "CUSTOM"}, { down = 3005, cockpit_device_id = 6, value_down = 0.6, name = "CUSTOM_NWAY: CONTR-SAPROTATE-PTR_value0.6", category = "CUSTOM"}, Disclaimer I'm like Jon Snow, I know nothing. I had a need, made a dirty script and shared the output hoping it would save time to others as well. I obviously did *not* test all of the switches provided, they may or may not work, but at least the device_id and the device_command should be correct. Please fell free to help me make this better ! THIS IS ONLY FOR THE KA50 AT THE MOMENT Installation Simply append the commands you're interested in (or all of them) at the end of "\DCS World\Mods\aircrafts\Ka-50\Input\ka-50\joystick\default.lua" between: keyCommands = { ... some very long text .. [color="Red"]_ INSERT CONTENT HERE _[/color] (should be around line 672) }, axisCommands = { (this is *not* update-proof, mind you, but if ED decides to change the ids/commands, I have the script ready to generate them again :P). Feel free to give them new names/category to your liking. The new commands should pop up in the 'options/control' GUI. Map them to your DX buttons and you're good to go ! Cheers :beer: Changelog v4: commands are now sorted by category and categories have a name (*much* easier to find something in the GUI) v3: fixed a very bad typo v2: names of commands made more human-friendly ouptut_v4.txt

It's perfect. As other people said you may need to attach it or stabilize it somehow (I just put a wood plank under it) because they're not too heavy and may tilt to the sides depending on how you use them. Besides that, just plug them in and you'll be sh*tting rainbows all over the place. Milan Sim has a lot you Youtube videos and Google Docs explaining the ins and outs of the rudder, and they've been very supportive and proactive over email (dozens of email exchanges/day) (and yes, even after they got my money). Milan Sim supplies a home brewed software to set it up or upgrade the firmware (the one I received already was upgraded to the latest firmware). In that software you can: - see just how precise the baby is (4096 position for the rudder and for each brake pedal) - set up all axis the way you want them (average filtering, round filtering, dead zone start %, dead zone center position, dead zone end %, revert, slider mode) - assign a DX button to the brakes axis (old games or just customization) - other MFG-specific stuff Hardware customization is also a thing. You can choose which actual physic curve you want to have (many available, ask Milan for more info). Then you can *very precisely* tune the intensity of the centering. Or, you can switch from having a center to having the rudder roam freely on its axis *very easily* and in less than 5 seconds (switching from plane to helo for example). You can adjust the position and inclination (up/down but also left/right) of the brake pedals or change the force of the brakes. Milan also provides plates to increase or decrease the width of the rudder set. In-game, well ... it does not do the maneuver for you, but it sure makes it an awful lot easier to control your aircraft. For the sake of comparison, let's assume you own a TM Warthog. Now imagine having to fly with a Logitech Extreme 3D (and I actually own one, it's actually a good joystick). This is what I'd feel if I had to go back to my good ol' Saitek rudder set ...

I obviously have no access to the source, but judging from the overall consistency of *all* the lua files inside the game folder, I can't picture it being anything else than a motley of (huge) code squirts (this is a personal opinion, and a guess). The pace at which things get added and complexity increases in DCS World are probably the reason behind that, and I'm quite astonished that the game (simulation) is both playable and stable. This is ant work, and keeping on debugging the astronomically big code base must be at best excruciating (adding new feature is fun, making them work flawlessly less so). ED has both my respect and my admiration for what they've done during all those years. Now concerning the issues raised by Dimitriov, my guess (another one) is that the Kamov code has not been touched in a while. Translated, re-factored, maybe, but no major overhaul. From update to update, pieces of this almost untouched code start breaking. This is maybe a sign that some of the underlying processes are not working as expected, or aren't anymore. I don't know to what length EDGE is going to take over the previous code base, but perhaps now would be a good time to make sure the ground you're building on is solid ?

This is a great addition to DCS ! Thank you once again PeterP for the incredible amount of time spent on modding, and for sharing the result of your work. I would like use this mod to have all airfield charts available in the Ka-50, and in the A10, plus some mission-specific info (*.miz included files). No problem setting it all up, the show/hide and glance keys are working fine, however it seems that I cannot change the displayed page whatsoever. There are some files in the Common_Charts folder, and some other ones in Custom_Charts\Ka-50. Also, I made another test with a *.miz that had KNEEBOARD/IMAGES. I'm stuck at the default kneeboard page. My understanding is that PeterP won't help, as the 1.2.7 version is in BETA, but I read in this thread that multiple users were very happy with the Ka-50 / A10 version. Is there anything I could have done wrong, or plain forgot ?

Hi ! We were having a blast in MP last night, thank you so much for all the work you put into this, it's mind blowing. I can't even begin to imagine the amount of time you invested into this ... much, much appreciated ! Sadly, we were having issues with the radio menus. SP is perfectly fine, but in MP, the following problems occured: - sometimes the F10 as a whole disappears right after take off (leaving the service zone) - MAD and sonar can't be retrieved once deployed, for no apparent reason - can't launch torpedo, for no apparent reason Probably DCS trigger functions overwhelmed by the amount of awesomeness you throw at them :P Just let me know if you wnat/need anything related to these issue ! Cheers ! :beer: