GregP

Yes, would be nice to have, as I believe the kneeboard will appear at its correct position if there's a pilot model.

The answer lies here and is going to make your day. :)

Actually MadCat's thread has figured this one out in this post. So Screamadelica, if you add those lines to your default.lua for the Fw190, you'll now be able to map separate switches/buttons to both Master Arm On and Master Arm Off.

Right, understood about how to quickly find control assignments. But as cichlidfan clarified, my complaint is that the controls GUI seems to a fixed size, in pixels, and does not scale with the actual in-game resolution chosen, thus leading to un-user-friendly interfaces like shown above.

No problem at all -- I realized my mistake a little while after posting. As an alternative, for those that are interested, I've created a separate thread for 3-way toggle switches here.

With thanks to Spy Guy for his excellent thread about toggle switches, it seems to me that given the big input lua changes that seem to have occurred post-1.2.8, it would be good to compile all the currently known working toggle switch commands, in particular those intended to be assigned to 3-position HOTAS switches such as the Warthog's flaps switch, pinky switch, and boat switch. I envision this to hopefully be as helpful as MadCat's thread about known working commands for multi-position switches (i.e. switches in DCS cockpits that don't by default have discrete commands for every switch position, primarily for pitbuilders who want to map each and every position to a separate physical switch). For those unfamiliar with how this works, I refer you to docfu's instructions. But the basic idea is that new default.lua input files can be created, with customized new commands, as described by POLARIS1 here, and then installed using JSGME as in POLARIS1's example for Fw190 flaps provided here, the actual code of which I've posted below under the Fw190 section. When offering additional commands to be added here, please enclose the commands within the 'code' brackets, as it makes copying-and-pasting into other's lua files easier. To start it off, here's an example for the F-86's 'position and fuselage' lights switch; when mapped in the controls GUI to say, the Warthog's pinky switch (i.e. map the new commands 'Pos & Fus Lights - Steady middle' to pinky aft and 'Pos & Fus Lights - Flash middle' to pinky forward), this makes pinky switch forward 'flash', 'off' in the middle, and 'steady' on aft: F-86 --Position and Fuselage Lights: {down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, up = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = 1, value_up = 0, name = 'Pos & Fus Lights - Steady middle', category = 'Right Forward Console'}, {down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, up = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = -1, value_up = 0, name = 'Pos & Fus Lights - Flash middle', category = 'Right Forward Console'}, Fw190-D9 --Alternate flaps {down = device_commands.Button_1, up = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, value_up = 1.0, name = 'Alternate Flaps Up middle', category = 'Flight Control'}, {down = device_commands.Button_3, up = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, value_up = 1.0, name = 'Alternate Flaps Landing middle', category = 'Flight Control'},

Enables toggle switches for the position lights for the F-86: --Position and Fuselage Lights: {down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, up = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = 1, value_up = 0, name = 'Pos & Fus Lights - Steady middle', category = 'Right Forward Console'}, {down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, up = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = -1, value_up = 0, name = 'Pos & Fus Lights - Flash middle', category = 'Right Forward Console'},

This is incredible work, guys! A few typos in the F-86 section though: There are extra (spurious) spaces in the 'down' part of these commands: External Light Brightness Battery Drop Tank Selector Engine Master Switch BTW, MadCat, I think those extra spaces will go away, and make copying-and-pasting easier, if you enclose all the commands with the "code" tags.

For a long time now, I've found it really frustrating that the controls GUI doesn't scale to the actual resolution you use. Instead you're always stuck with a small box in which you have to constantly scroll around, both vertically and horizontally, in order to see all the commands and all the devices. In extreme cases, like when using a resolution of 3840x2160 as shown in the screenshot, it's almost comical how small the window is. Does anyone know of a way to make this window bigger? If not, is this a feature that could be added to DCS by the devs?

Are you sure those are the only flaps-related commands in your lua file? Doesn't 3002 (flaps take off) have to be defined somewhere in that file? Those two commands alone don't make use of the middle switch position when I try them.

OK, and, the point I was originally trying to make, is that not everyone who's using TrackIR is having this 'problem': myself and Altflieger, at least, do not have an off-center default TrackIR view. Our default view is centered relative to the cockpit frame, and we have to lean right to see through the gunsight.

Agreed that it would be nice to have a 'lean to sight' command, a la IL-2, but it seems that most of the previous posters were saying that their default centered view is in fact already lined up with the gunsight, and therefore is not directly along the centerline of the aircraft, causing the cockpit frame to appear off-center.

I'm using TrackIR5 and don't have this issue; when I center my view, it's perfectly centered in the cockpit, and I'm not looking directly through the gunsight. I have to shift my head to the right in order to see the reticle. But you guys are saying that you're seeing the opposite? Strange.

Just wanted to say thank you for this mod -- absolutely fantastic piece of work. I remember about 2 years ago trying to figure out how this up/down stuff all worked, and it was frustrating to say the least. Your script and explanation has now automated 90% of the headache of getting switches like this working!

I finally got a up of a startup sequence using the 4K. Note that it has annotations but they only show up on non-mobile devices, so I'd recommend watching on a laptop or PC. Also, like the pictures I posted at the beginning of the thread, the video shows a serious blue tint that is definitely not there when you're sitting in front of it. I have no idea why it shows up in pictures and video.

If you were asking me -- nope, no problem at all. It's basically just like looking at four 1080p monitors stacked together, and feels very natural.

KaspeR32, yes, they do have VESA mounts. 8 months later and yup, still loving the 4K. :) My overall view hasn't changed; for DCS, the Seiki 4K line is undeniably the best bang for the buck you can get -- as long as you're OK with 30Hz. I've found that without question, I am. Everything sharp and on one screen was the ideal I'd imagined for years, and with a large 4K, it's now reality. I do other gaming too, and really can't complain there either. Sure, response time could be better, black levels could be better, etc. But for a cheap, huge, ultra-high-res monitor, I'm happy. I finished Wolfenstein recently, and lately have put a lot of time into Dark Souls 2. Both look fantastic at 4K.

D'oh! Yessir I am! Good find. Will disable that tonight and give it a try. Thanks!

I've had this problem for months now and have yet to find a solution. Whenever I try to switch position (e.g. co-pilot to pilot) DCS crashes. My me.log shows the following, which doesn't give me any clues as to what's going wrong. Any ideas? 00042.947 ERROR VFS: add_location {"My Missions", "C:\Users\Greg\Saved Games\DCS\Missions\"}: path already added as "My Missions" 00044.483 ERROR DXGUI_EDGE_RENDER: Cannot load texture '' 00044.587 INFO SOUND: loaded 782 sdefs from ".\sounds\sdef" 00044.599 INFO SOUND: XAudio2: Using device ID:'{0.0.0.00000000}.{5e93a997-9d3f-4941-8702-e3a2b3d89059}' Name:'Speakers (Sound Blaster Z)', channels: 6 00044.599 INFO SOUND: XAudio2: channel layout: FrontLeft FrontRight FrontCenter LowFrequency BackLeft BackRight 00044.645 INFO SOUND: Using SSE FTZ/DAZ mode. 00044.927 UNKNOWN main: Cannot load skin[windowHeaderSkin] from file [nil] 00046.156 UNKNOWN main: check unit WINDMILL 00046.738 WARNING LOG: 19 duplicate message(s) skipped. 00046.738 UNKNOWN main: Mission C:\Users\Greg\AppData\Local\Temp\DCS\tempMission.miz loaded 00049.033 UNKNOWN main: checking introduction C:\Users\Greg\AppData\Local\Temp\DCS\tempMission.miz 00049.033 UNKNOWN main: introduction NOT found 00053.179 UNKNOWN main: turning log false 00053.242 INFO SOUND: detaching sdef path ".\sounds\sdef\" === Log closed.

EDIT: SOLD! I bought these last year but recently got the MFG Crosswind pedals, so I'm selling the Saiteks for $100 plus shipping. They're in perfect condition, are only a year old and I have the original box. Sorry though, I can only ship within the US.

Ha! I took the exact same picture!

It's a Playseat Evolution, usually intended for use with racing sims, with some additional cushions added on top.

I, too, received my pedals today, and like sobek, I'm just blown away by the quality. These things are by far the best pedals I've ever owned. The movement is so smooth, so fluid, that you forget you're using sim pedals. Pricey, yes, and I never thought I'd spend so much on pedals, but now that I have them in my pit, I have to say they were worth every penny.

jkosnikowski, apologies for not seeing your question earlier! Don't know if you're still looking for input, but I believe that just about any modern card can support 4 monitors. I was using a 7970, and then switched to an R9 290, and both worked fine with 4. The caveat here is that I haven't used Nvidia cards in quite awhile so I don't quite know the details; you may have to run in windowed mode to run 4 monitors. As for monitor sizes, SoftTH will allow you to scale each monitor's image such that you can use mismatched monitor sizes; it just creates a little more work on your part to get it set up. But getting multiple monitors of the same size would obviously make everything much easier and would probably look better in-game too. Vahakyla, total cost: I really don't know as I've slowly assembled it over a number of years. And in fact back in December I completely ditched the 4-screen setup and went with a single 4K 55" monitor. But if I had to guess, all together I'd estimate $2500, something like that?

Loz, happy to hear you too have made the switch to a big 4K and are liking it. Looks incredible, and I'm jealous of your 60 Hz. Despite my model being only 30 Hz, 6 months later I'm still loving it. Honestly I rarely notice the 30 Hz limit because the size, the resolution, as well as simplicity of running just a single monitor, are more than worth it for me. As for the touchscreen, I tried in various ways to integrate into my pit and just couldn't get anything I was comfortable with. Eventually I sold it and now retain just one of my original 4 27" screens, a 3D model that I use for 3D gaming and temp/load monitoring when flying. I bought a second X-Keys programmable keypad and use it for the UFC/CDU, so really the only time I need to use the mouse to click inside the pit is for the MFCDs. Anyway, I'd definitely encourage others to consider 4K. Sure, it's maybe not worth it yet if you're planning to use it as a TV, but as a monitor, it's just incredible.