Munkwolf

unfortunately in software development the last 5% takes half the time

I'm looking at picking up the throttle and another control panel. I see 0.5m and 1m cables available in the virpil store, but that isn't long enough to reach from where I'd put the throttle to where I'd put the control panel. Also I can't just run them separately as USB devices as I'm at a windows device limit - has to be the aux-out option. Anybody know where I can get longer XS9-5 cables (2m or 3m)?

On that note.. one of the interesting things to me in the Apache Controls Setup video he did recently was seeing version '2.99' down in the lower right of the menu screen...

In your screen it looks like one of the 3rd party stores on newegg? I haven't done any orders from newegg within the past year, but don't remember having any issues if i'm buying from them when it's 'sold and shipped by newegg'.

I've been happy with openwheeler for my rig: https://forums.eagle.ru/topic/263794-my-openwheeler-x-keys-rig/ Base rig, seat lift kit, flight pack for side mounts, rudder pedal plate. Then two of the keyboard trays mounted together have worked well as my center console. A custom 80/20 rig would probably be better, but I'm lazy and just wanted to throw things together quickly. Fyi openwheeler does offer a chassis-only option, where you can put whatever seat you want on it, as long as the rail width matches. If I were doing it again, I might go that route and get a pilot seat for it instead of the racing seat. https://www.amazon.com/OpenWheeler-Chassis-only-included-Racing-PC/dp/B07DPWGVMF/

It adds keybinds for controls that aren't bindable in the stock game. Axis for mixture is in there. To use the file, you'll need Quaggles Input Command Injector mod - the file is formatted for use with it. That mod lets you put custom binds in your saved games folder so you don't have to redo them after DCS updates. https://github.com/Quaggles/dcs-input-command-injector Also the I-16 file above is part of a larger effort across all modules, if you are interested in that. https://github.com/Munkwolf/dcs-community-keybinds List of axis commands added for I-16: axisCommands = { {cockpit_device_id = devices.ELECTRIC_SYSTEM, action = 3034, name = _('Sight dimmer rheostat')}, {cockpit_device_id = devices.ELECTRIC_SYSTEM, action = 3035, name = _('Cockpit light rheostat')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3022, name = _('Ignition switch')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3042, name = _('War Emergency Power')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3044, name = _('Mixture control')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3047, name = _('Motor cowl flaps')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3048, name = _('Oil radiator')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3062, name = _('Fuel valve')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3046, name = _('Supercharger switch')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3087, name = _('Rockets/bombs counter')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3088, name = _('Rockets/bombs master arm')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3060, name = _('Gun wing left Recharge')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3061, name = _('Gun wing right Recharge')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3070, name = _('Gun nose left Recharge')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3071, name = _('Gun nose right Recharge')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3037, name = _('Primary fuel Switch')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3005, name = _('Primary fuel Pump Pull')}, {cockpit_device_id = devices.MOTOR_SYSTEM, action = 3102, name = _('Fuel Collector')}, {cockpit_device_id = devices.WEAPON_SYSTEM, action = 3103, name = _('Jettison fuel tank')}, {cockpit_device_id = devices.OXYGEN_SYSTEM, action = 3074, name = _('Oxygen adjusting valve')}, {cockpit_device_id = devices.OXYGEN_SYSTEM, action = 3075, name = _('Oxygen emergency valve')}, {cockpit_device_id = devices.OXYGEN_SYSTEM, action = 3076, name = _('Oxygen shutoff valve')}, {cockpit_device_id = devices.GEAR_SYSTEM, action = 3086, name = _('Gear handle (Relative)')}, {cockpit_device_id = devices.FLAPS_SYSTEM, action = 3063, name = _('Flaps handle (Relative)')}, }

Same. Rolling back to Vaicom 2.5.26.4 fixes the issue.

I use the extensions. I used to have lots of issues with the Options menu, and only like every other voice command working. What fixed it for me is removing the NS430 module (vaicom support page mentions NS430 and DiCE mod as having compatibility issues). Do you happen to have the NS430 module or DiCE mod?

I'm not sure I can help with why the keys won't work, but macro keypads like that usually won't show up as separate devices unless they can run in a HID or game controller mode, where they'd output directx buttons. They'll be part of the standard keyboard device in DCS. Did you try mapping it as part of the keyboard controls in DCS?

InputUserProfiles are where the lua files are for any profiles you save, via the dropdown menu available at the top of each device's column in the Adjust Controls menu. I personally use them a lot, as I have some devices that have the same device name and occasionally get mixed up when they get a new ID in windows. When that happens, it's quick and easy to load the profile into the right device in DCS.

I would like that. If not additional functionality with separate training vs practice mode or module, than maybe just how the training missions are structured. The Harrier has an incredible set of actual Training missions (short/full versions, night/day versions), and the Hornet has an incredible set of training missions under Missions (the mission/weapon/combat qualification ones). Having each of those as a standard for modules moving forward would be fantastic.

Not sure of the metrics used (sales? views? manually set?), but there is a 'popularity' sort option for the shop page. Apache is top spot, followed by Hornet, Viper, Tomcat, Warthog, Hind... seems accurate.

Also I've got a lot of keybinds done for all modules that are formatted for use with Quaggles injector mod: https://github.com/Munkwolf/dcs-community-keybinds/ Here's my F-14 pilot seat binds as an example: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/F14/Input/F-14B-Pilot/joystick/default.lua Edit to add: The midi2vjoy stuff looks awesome. I'm capped out with number of HID devices I can use, but I've got space on my vJoy device and now thinking of how/where I can put some midi devices on my rig.

Thanks for the heads up Blackbird! I'll have that fixed in the next update.

Looks like you're missing a comma after the keyCommands object. Instead of } axisCommands = { try it with }, axisCommands = {

Yes, because it's been an issue for a while now that hasn't been addressed. It could be years more before some modules are fixed. Adding a separate IPD setting for each module could be done quicker (the setting is already there, just needs a per-module override), and would allow VR users to have greater enjoyment of the sim until the time comes when all modules are updated.

Not all cockpits are uniform scale for VR yet. Ideally they would be, but until then this would be useful. This is for the IPD setting in DCS under VR options, which is more like 'cockpit scale'. Could be added under existing per-module Special menu. +1

I've used the Sabrent 10-port powered hubs the past few months with no issues: https://www.amazon.com/dp/B0797NZFYP?th=1 2 of them for my center console, then 2 other 7-port hubs for my side devices. Probably will replace the 7-ports with 2 more of the 10-ports - having the separate power button for each port has been nice.

Definitely will be ordering at least a pair, maybe three. Would not be buying any sort of mount for them. Definitely interested in abris strip & tedac... thought I'm at device limit, so the abris strip would hopefully not be a separate device. Speaking of, it'd be amazing if they could be daisy-chained where 2 of them could show up as one device.

This. I enabled pilot bodies for the first time last weekend, and was surprised most of my saved views I thought were good had my head in the pilot's chest.

If you want to use mods, 2-way options for landing gear are in the community keybinds: https://github.com/Munkwolf/dcs-community-keybinds/blob/f9f82b690fcf62901c1e1b3b5650b7271a41e106/InputCommands/FA-18C/Input/FA-18C/joystick/default.lua#L73

Those are in the community keybinds project: https://github.com/Munkwolf/dcs-community-keybinds/blob/140b7080e457c04b5001ff0f4925f7e939f4a565/InputCommands/Mi-24P/Input/Mi_24P_pilot/joystick/default.lua#L224 Files are formatted for use with Quaggles mod: https://github.com/Quaggles/dcs-input-command-injector/

All good, sometimes it just takes a second set of eyes!

Ah, you have Quaggles Mod going into Saved Games\DCS? It should go into the DCS main install folder like the other mods. It overwrites the default DCS\Scripts\Input\Data.lua. Can you try that? Then my mod with the keybinds, yes, those do go in Saved Games\InputCommands.

The laser commands are in there. Also confirmed that they work, tested them last night after replying to bones1014. Are you using Quaggles mod and have it enabled? If so, in your dcs.log there may be an "InputCommands" error showing the line number it is having trouble parsing. Thought it was worth a mention as you mentioned disabling all mods. Did you add the stores config switch to the original files that DCS uses, or to the Saved Games\InputCommands folder that Quaggles mod uses? If you had added that in the original DCS files, and then Quaggles mod isn't running, that would explain what you are seeing