Smashy

You can add the relevant pages to [DCS rootdir]/Mods/terrains/[mapname]/Kneeboard This works great for all maps I have except Syria. I think there's a long-standing bug that affects Syria-specific custom kneeboard pages.

@Minsky - your module and aerodrome kneeboards really are works of art. Thanks for creating and sharing these!

Resurrecting a necrothread but I was just going to dig into this file tonight to do the same thing. I'm glad I found this post before I wasted my time. The first clue was that the default values for the AIM120 in this file aren't applied to a hot or cold started Hornet. Has anyone found a way to do what OP was trying to do in the last year? I'm also hoping for a data transfer cart. Hopefully we'll see something somewhere down the road.

In some of the joystick device diff LUA files, I noticed some interesting names in the name-value pairs found there: ["hardwareDetent"] = false, ["hardwareDetentAB"] = 0, ["hardwareDetentMax"] = 0, These are in the axis section for my new rudder pedals (which don't have detents). Are these old or are they something new for upcoming device support features? Maybe VKB TECS :D?

...it sends you to the E-Shop instead of the free-to-play page. FYI.

Hey @Dscross - I'm looking at upgrading my CH Pro Pedals and the Crosswinds and Ace Collection pedals are leading the race, with Slaw a close third. Would you mind posting an update on your thoughts on these? Which one ended up being your main set? Thanks!

Found the fix. The problem was caused by differences in the default.lua files in the following locations: [DCS basedir]/Mods/aircraft/Uh-1H/Input/UH-1H/joystick [DCS basedir]/Mods/aircraft/Uh-1H/Input/UH-1H/keyboard I made some changes to [DCS basedir]/Mods/aircraft/Uh-1H/Input/UH-1H/joystick/default.lua and can now switch seats via HOTAS button assignments. Make a backup copy of this file first just in case. Find the following lines and comment them out (prepend '--' to the line). It should look like this: --{down = device_commands.Button_1, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Pilot Seat'), category = _('View Cockpit')}, --{down = device_commands.Button_2, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Operator Seat'), category = _('View Cockpit')}, --{down = device_commands.Button_3, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Right Gunner Seat'), category = _('View Cockpit')}, --{down = device_commands.Button_4, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Left Gunner Seat'), category = _('View Cockpit')}, Add the following lines: {down = iCommandViewCockpitChangeSeat, value_down = 1, name = _('Set Pilot Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 2, name = _('Set Operator Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 3, name = _('Set Left Gunner Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 4, name = _('Set Right Gunner Seat'), category = _('View Cockpit')}, The orange warnings and duplicates are also gone from the control binding page. This appears to work so far but I'm not sure if it'll break anything else or violate IC. If it works for you, save the modified files in safe place or the next update will clobber them. Alternatively, you should be able to recover them from the most recent [DCS basedir]/_backup* that gets created after an update.

Did you go with the Cosmo or Avia cams?

With the latest OB patch 2.7.18.30765, it seems I'm unable to change seats with any joystick/throttle binds. The keyboard binds work just fine. I also notice that there are now duplicate control entries for these binds. Note that the keyboard column is grayed out for one pair of duplicates and the joystick column is grayed out for the other pair. Anyone else running into the same problem?

I'm curious about this too. I've tried various things - encoder rate, virtual axis on the encoder dial but nothing really worked the way I wanted. I'm currently using one of the hats to control radar antenna elevation. You might want to post this question over at the Virpil forums. I've asked a few questions there and have had good success in getting helpful answers.

I went with the Alpha Prime and CM3 base. The only thing I liked about the MCG over the Alpha Prime was the swappable ministick and hats. I would like to have 4 hats on the stick. I did try configuring the ministick on my CM3 throttle to send button presses and that will conceivably be a suitable workaround on the Alpha. The Alpha's ergonomics did look better to me and that's important since I have medium-ish hands. I also envision the scroll wheel encoder being pretty useful in a videogame context. Finally, while it's a generalization and personal preference, I like Western HOTAS designs over their Russian counterparts and the fictional but Western-looking (IMO) Alpha did speak to me louder than the MCG or T50CM2 grips. Oh, also finally, since I already have a Virpil throttle it'll be simpler for me to learn a single management software tool vs two tools. And lastly finally, Virpil might be a better option for the US guys in terms of support with the opening of their physical store here. At least that's the hope.

I totally get it. I'm using a CH Fighterstick and it's going to be hard giving up the four hats in the F-16 layout. However, the Alpha does provide a metric ton of more functionality over my trusty CH stick that I think it will be a significant improvement. I've been messing with the Virpil software and have found a way to configure the ministick on the CM3 Throttle to send button presses (thanks @imacken!) This would allow me to use the Alpha's ministick as a pseudo-hat if I still wanted a fourth hat on the stick.

@dburne - thanks for the feedback. It seems a common theme among most people who have owned both VKB and Virpil is that it both are great products and it comes down to personal preference. At this point, I think I'll give the Alpha Prime a shot along with the new CM3 base. Looking forward to the upgrade!

I'm in the process of deciding on a stick and two main contenders are the Virpil Alpha Prime and the VKB MCG Ultimate. Exciting times! It sounds like you prefer the MCG Ultimate grip over the normal Alpha. If you don't mind, could you tell me why? FWIW, I was just gifted the CM3, I love tactile, clicky things, and heavy, precise moving things.

Hey @imacken - are you using the WarBRD on the desktop? What grip are you pairing it with? If it's the Alpha, do you find the lack of a fourth 4-way hat limiting? I'm guessing I could find homes for the A-10/F-16 trim, DMS, TMS, CMS hats between a stick and my CM3 throttle. Sorry for the flood of questions, new owner of the throttle and trying to decide on what stick to pair it with is big decision. I'm considering the Alpha Prime + WarBRD base.

After firing up Virpil's software and feeling a bit overwhelmed, I was thinking the same thing about sticking with a single brand. I am in the US so that's another big nod for Virpil. edit: the one thing I like about the VKB is the ability to have four hats on the stick. That makes sense for modules like the the A-10C and Viper.

My awesome GF just got me a CM3 to replace my trusty CH Pro Throttle and I'm now looking to get something of similar capability and quality to replace my CH Fighterstick. I'm looking at the VKB MCE and MCE Ultimate along with the Virpil Alpha, Alpha Prime and MongoosT-50CM2. I'll be using these controller on the desktop for now until I can figure out a good mounting solution for my room. I'm looking for suggestions or things to look for when shopping for a new high-end stick. Thanks!

here's one I did for the Mustang flap position. Not exactly authentic or realistic, but in my non-VR cockpit, it's hard to tell flap lever position.

An alternative is to create a custom icon that includes the text and any graphical elements you might want displayed with any variable data. I've used both approaches, depending on what I wanted to do.

Ah, thanks @Minsky!

Thanks for the great work @Minsky. One question, is the RWR/HARM codes page missing? I did not see it in the zip file I downloaded. I'm keeping the older version around because the having the HARM codes readily available is pretty nice.

Whenever I change monitor options, DCS restarts itself. It's pretty painful to make the switch. The only thing different between my usual monitor config and the Apache is the viewport names: $ diff CUSTOM\ -\ AH-64D\ PLT\ MFDs.lua CUSTOM\ -\ default\ MFDs.lua 2c2 < name = _('CUSTOM - AH64D PLT MFDs'); --- > name = _('CUSTOM - default MFDs'); 18c18 < AH64D_PLT_LEFT_MFCD = --- > LEFT_MFCD = 26c26 < AH64D_PLT_RIGHT_MFCD = --- > RIGHT_MFCD =

From TWS, establish STT and then enter RAID mode. All visible trackfiles are shown with L&S star symbol. Additional oddities: entering RAID seems to "work" after establishing STT track from RWS EXP is boxed when entering RAID. Note: in the attached track, I'm not hitting the OSB to box EXP, I'm using the "RAID/FLIR FOV" HOTAS function to enter RAID weird numerical values displayed in RAID mode where target altitude differential is typically displayed multiple L&S with SCAN RAID.trk

I went to an airshow a couple of weeks ago and got a chance to look and touch an AH-64D on static display. The 2 pilots were there and really took their time to interact with the crowd. I was able to ask a bunch of questions. I asked why the FCR wasn't mounted and he said in the Apache's current role, it's a 300-lb weight sitting way above the helo's CG so it's usually not mounted. He said it would be useful in a peer/near-peer conflict but not in the COIN stuff they're doing now. I then asked if the TADS was where the magic happened and he said that it was a system from the 90s that was badly in need of an update. In his words, it was "trash", LOL. So it turns out even RL pilots wish for fixes and improvements even though the gear and tech is working as intended

Great video and I'm really looking forward to making some ham sandwiches after this feature drops. After watching it, I had a couple of questions. Was the cut landing grade a one-off error or does Mode 1 still need a bit of tweaking? This is more of a procedural question, but I notice Wags drops gear then trims for onspeed AoA, drops half flaps and does more trimming, drops full flaps and does more trimming. For CASE I, I drop gear and full flaps all at the same time while in the break and try to estimate trim so I'm close to onspeed AoA after coming out of the break. I do the same for CASE III but have to hold more forward stick to prevent full flap condition from pitching the nose too far up while I trim for onspeed AoA. With Wags' approach, it makes the straight-in dirty-up a lot less stressful. With a properly executed CASE I break, I don't know if there's enough time to do the sequential gear/half flap/full flap operation. Do real-life Navy guys follow a specific procedure for this or is this all personal preference? I'm genuinely curious so I hope this thread doesn't get locked, LOL.