Munkwolf

I would give the edge to the Blackshark. It has a very capable autopilot / flight director mode where you can set it to hover or set it to fly to a point, and then focus on systems and buttons. The A-10 is also easy to fly, and I'd recommend it too, but absent using Active Pause it's doesn't quite sit as still as the KA-50 can to allow time for learning. Fwiw, the L-39 and C-101 are both fun and a bit underrated imo! @freehand thanks!

Great post. I bet it sure brings in the views though. "Try this one weird trick to increase your frames!".

Here ya go, just tested it and this works: {down = device_commands.Button_17, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = -0.8, name = _('Flaps 10%'), category = _('Flight Control')}, {down = device_commands.Button_17, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = -0.2, name = _('Flaps 40%'), category = _('Flight Control')}, Did need to address Button_17 command, but then the axis range is -1 (full up) to 1 (full down), so the value_down in my first post was way off.

You should be able to do it by editing the lua files. In <DCS>\Mods\aircraft\P-51D\joystick you'll see default.lua, that has all the controls available for hotas. If you wanted to add this to keyboard as well you'd need to edit the \P-51D\keyboard\default.lua. Around line 242 are the flap controls, you'll see: {down = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Flaps Up'), category = _('Flight Control')}, {down = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Flaps Down'), category = _('Flight Control')}, You can see the flaps go from 0 (fully down) to 1 (fully up). Try adding these lines somewhere in there (doesn't technically matter where, but best to add them right below the lines above so the flaps commands are grouped in the lua) {down = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.9, name = _('Flaps 10%'), category = _('Flight Control')}, {down = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.6, name = _('Flaps 40%'), category = _('Flight Control')}, Edit to add I just realized/remembered that might just be changing the amount each press trims. If above doesn't work, try this instead, it points to a different command (the flaps axis) {down = device_commands.Button_17, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.9, name = _('Flaps 10%'), category = _('Flight Control')}, {down = device_commands.Button_17, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.6, name = _('Flaps 40%'), category = _('Flight Control')}, I'm finishing up some work and then will be able to test it in a bit.

not specific to that, but some general guides that have helped me and cover that stuff: aircraft carrier operating procedures https://drive.google.com/file/d/1hShIyjq1Cf8MQSAcwk5k1IhSMdvqpUok/view?fbclid=IwAR20L_LgoorqeL0ndDuF3Bgpa5b_XGiC-XajdTEj35rj8yaOLNlGp55tzXM edit to add that the section on entering cca and initial marshall contact starts on page 49, and then goes into case 1 cyclic ops guide https://drive.google.com/file/d/1gCUyoDQ-DGGBCFEOvgpER9L1w7hc0TT5/view?fbclid=IwAR0NN6L1YpKXuyGdzOI0nB4UyHH8_0Zwf1mJ2i_dZjncHFVsamRhO3gkIvY hoggit's guide https://wiki.hoggitworld.com/view/Carrier_Air_Operations then there's ED's Supercarrier Operations Guide that'll be in your <DCS>\Mods\tech\Supercarrier\Doc folder

I'd recommend saving them as profiles, then you can find the profiles in <User>\Saved Games\<DCS>\InputUserProfiles. Copy em over, and then can load them up for each device on the new rig.

Tried it a couple of months back with those new drivers.. the tracking is amazing in their test app.. and I got really excited... until I got into SteamVR. Put the leap back in the box, box on the shelf, and haven't touched it since.

At least for me, it's more immersive. I don't like holding the mouse in my right hand to then look to my left and click on a control on the left rear console, for instance. It's also more effective imo, because I don't have to look somewhere first. Able to keep my head up more and focused where I should be instead of using my eyes to look for a control..

I always play in VR, and have a *lot* of buttons. Putting bump dots in a pattern on the keys helps me find the right key. Then it's just been practice and memory. Plus I configure the buttons to be close to where they are in the cockpit.. so part of it for me is just looking around the cockpit to remind myself where the buttons /instruments are. For planes I know well, it's nice to not have to look around at all and be able to hit any control in the cockpit. Or sometimes I practice doing things like engine starts with my eyes closed. Press key on 3rd in on 3rd row for left rear console? Feel for corner of that device and then bump dots to locate. You could put your cheatsheet in as a custom kneeboard page? bump dots: https://www.amazon.com/s?k=bump+dots and my button rig, for reference:

Ha! Apparently ED wants you to purchase the Sabre. Was just reading this thread yesterday, was cool to then see the fix listed in today's notes.

A couple of workarounds might be: + editing the lua file for the plane controls to reduce the amount of trim each button press sends + mapping the hat buttons to be a relative axis, using something like joystick gremlin to control the value applied per button press for the first.. couldn't help but look after typing that.. haven't tried it (yet).. but in <DCS_Install>\mods\FA-18C\Input\FA-18C\joystick, you'll see default.lua. in there, around line 50, you'll see the trim controls, like: { pressed = hotas_commands.STICK_TRIMMER_DOWN, up = hotas_commands.STICK_TRIMMER_DOWN, cockpit_device_id = devices.HOTAS, value_pressed = 1.0, value_up = 0.0, name = _('Trimmer Switch - PUSH(DESCEND)'), category = {_('Stick'), _('Flight Control'), _('HOTAS')}}, might be able to change value_pressed to like .5 and have it trim half the amount it currently does. edit to add modified block to set value_pressed to .5: { pressed = hotas_commands.STICK_TRIMMER_DOWN, up = hotas_commands.STICK_TRIMMER_DOWN, cockpit_device_id = devices.HOTAS, value_pressed = 0.5, value_up = 0.0, name = _('Trimmer Switch - PUSH(DESCEND)'), category = {_('Stick'), _('Flight Control'), _('HOTAS')}}, { pressed = hotas_commands.STICK_TRIMMER_UP, up = hotas_commands.STICK_TRIMMER_UP, cockpit_device_id = devices.HOTAS, value_pressed = 0.5, value_up = 0.0, name = _('Trimmer Switch - PULL(CLIMB)'), category = {_('Stick'), _('Flight Control'), _('HOTAS')}}, { pressed = hotas_commands.STICK_TRIMMER_LEFT, up = hotas_commands.STICK_TRIMMER_LEFT, cockpit_device_id = devices.HOTAS, value_pressed = 0.5, value_up = 0.0, name = _('Trimmer Switch - LEFT WING DOWN'), category = {_('Stick'), _('Flight Control'), _('HOTAS')}}, { pressed = hotas_commands.STICK_TRIMMER_RIGHT, up = hotas_commands.STICK_TRIMMER_RIGHT, cockpit_device_id = devices.HOTAS, value_pressed = 0.5, value_up = 0.0, name = _('Trimmer Switch - RIGHT WING DOWN'), category = {_('Stick'), _('Flight Control'), _('HOTAS')}},

I haven't had any issues with the mic. Use Vaicom all the time with it. The speakers though.. one of mine blew and was really crackily. I'd recommend setting system volume to like 40% - 50% when first using the headset. It pumps too much signal to the speakers by default. Silver lining for that.. I had read tons of horror stories about HP support... and while they may be true... at least in my case, I contacted HP support via their website, had a ticket created, and had replacement speakers in hand within a week free-of-charge.

It's possible - SimShaker for Aviators shakes when I fire the gun. I see references to gun and cannon stuff in the SimShaker.lua that Export.lua includes.

It went smooth, or at least I can't remember any hiccups with it (it was a few months ago). It seems to point parts of SteamVR to WMR.. I'm checking the SteamVR settings, and it has "Windows Mixed Reality" listed for "Current OpenXR Runtime" in the Developer tab, with an option to set it to SteamVR. So if you wanted to switch between the Index and G2 there might be some extra steps beyond just switching which one is plugged in.. but after using the G2 honestly I haven't thought for a second to go back to the Index. I've actually considered getting a 2nd G2 as a backup / guest headset. Imo, the Index has better design, better speakers, better controllers, faster frame rate... basically everything about it is better than the G2... except for the display. But the G2 display looks so good, it outweighs all that other stuff.

I had that issue with it when I was using my warthog base. Like the amount of trim needs to be halved per button press. Sometimes it's either a little too much one way or the other.

I upgraded from an Index to a G2 and didn't have to do any kind of uninstall of the Index stuff.

warbirds with 40s jazz playlists going on your music streaming service of choice.. :chefskiss: what heatblur did with the viggen and f14 is cool, and it would be nice to see that extended to other planes in historically appropriate ways. warbirds can tune to one of the radio channels for music, but can't ff/rewind :). walkman/tape for 70s and 80s, where you can ff/rewind but not skip songs. modern planes get ipod/zune. small 3d model attached somewhere exposing music player controls. one of the super low-to-no priority things that, once there, is awesome and something people didn't know they needed.

Glad to see this issue isn't something specific to my machine - thought I had messed something up with the 51 settings somehow. Had to fiddle with the lua files to get the flap/warm/cold levers working somewhat like I remember them doing pre 2.7. Have them bound to a CH throttle quadrant. Controls window showed proper movement with all 3 axis, but no animation or perceived effect in-game.

if i'm reading it correctly, it's not via the controls/bindings.. the request is to be able to grab both throttle controls at once with mouse/vr cockpit cursor. kind of like how warbirds have the throttle locks. seems like a good request to me. might be able to do it via lua editing to point the cockpit definition for like the right throttle to affect the general throttle axis.

I upgraded my warthog stick to VKB stuff and am quite happy with it. I've done 2 orders from https://vkbcontrollers.com/. Gunfighter base with F14 and MCG Pro grips, then a later order for the MCG Ultimate when it came back in stock.. plus the KG12 grip because why not. Orders shipped from China via DHL (to Colorado), around $70 for shipping first order, $50 for second one. Both orders arrived on time, within about a week and a half from when I ordered. Really pleased with the whole experience and actively recommend VKB. Imo the clutches give the gunfighter the edge over the other bases. Hoping VKB releases their throttle soon before I'm tempted to go ahead and upgrade to a Virpil or WW throttle.

Check bignewy's post right before yours. There's a new post for 2.7.

imho, i'm very excited to be flying around in some great looking clouds. I also want the other stuff you mentioned, but I trust ED to prioritize things how they see fit, seeing as they are the ones in position to know what works best for them with effort level, resourcing, and timelines. The other stuff will come in time. Maybe the new clouds will bring in new users, and thus more money, to better fund the development of the features you listed. imho, proper ATC isn't going to pull as many users over from other flight sim titles like MSFS. Having clouds that look as nice or nicer than MSFS will.

Hope the timing works out! I went the more conservative route and took friday and monday off.

Between DCS and iRacing, I've honestly been surprised and depressed by the number of people that conflate the spelling.

Ha, agreed!