Munkwolf

Finished a keybinds update for the A-10C today if anyone is interested: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/A-10C_2/Input/A-10C_2/joystick/default.lua Please note that the file is formatted for use with Quaggles mod: https://github.com/Quaggles/dcs-input-command-injector Highlights are separate on/off/on-else-off bindings for lots of switches. Yaw trim and light dials available as axis binds. Bindings added for non-functional stuff like IFF, KY-58, and the 6 button block on the UFC.

Finished a keybinds update for the A-10C today if anyone is interested: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/A-10C/Input/A-10C/joystick/default.lua Please note that the file is formatted for use with Quaggles mod: https://github.com/Quaggles/dcs-input-command-injector Highlights are separate on/off/on-else-off bindings for lots of switches. Yaw trim and light dials available as axis binds. Bindings added for non-functional stuff like IFF, KY-58, and the 6 button block on the UFC.

Not worth installing target, imo. Something like joystick gremlin is better for that kind of customization. +1 on the thrustmaster drivers. Then through windows usb game controllers window you can set the ID's. I run 3 MFD's, and before installing that driver I had 2 'F16 MFD 2' devices that would sometimes get mixed up. With the driver can set the third to ID 3.

Nice write up @AKA_Clutter My experience has been similar, only differences being I've had a bit more time with it (into the dozens of hours with it so far), and I didnt have my WH throttle reversed I adjusted the friction when I set it up, but haven't had to touch it since. Just enough friction so it sticks if I move the lever up a bit, instead of falling back down. Tried all 3 cams for about an hour each, ended up using the middle (40deg) cam. Also using SharKa grip on it. No regrets there, as I really like flying the Shark with it and having the controls line up.. but I could see myself getting a LH Alpha grip for it at some point for more options.

voiceattack and vaicom both work with beta. what red circle? do you have plugin support enabled in voiceattack settings? and put vaicom files in voiceattack/apps folder, then imported the profile into voiceattack? for configuration window, It shows the default hotkey in the log in voiceattack when vaicom loads ("Press LCtl + LAlt + C for config"). or you can verify the hotkey in the voiceattack profile (assuming you have the profile imported). In the About tab of the vaicom configuration window is where you can enter key. page 5 of the user manual is a good guide for this part of the process https://www.vaicompro.com/uploads/7/5/4/3/75436709/vaicom_pro_user_manual.pdf

Along with powered hub (or plugging directly into motherboard usb port), I'm wondering if it might be a power setting thing? Under windows power options, do you have your computer set to high performance? under additional power options is usb selective suspend turned off? In device manager, under mixed reality devices it should list headset, and under it's power management tab, is the 'allow windows to turn off this device to save power' setting unchecked? That same setting is available for other usb devices too

did you map the twist to throttle? is it inverted? is another device mapped to throttle? fyi hind grip rotates opposite from huey. twist out for max throttle in huey, twist in for hind.

from the docs: "If >1, the game will render at its "native" resolution, and afterwards the image is upscaled to a higher resolution as per the given value." With a >1 value I'm using the FSR magic for better clarity. Probably not much different than if I upped the pixel density or steam supersampling some.

Mi-8 comes to mind as far as number of commands.

Unfortunately I'm not seeing a way to get those working as an axis. I had hope, because for map_display_commands there's alternate HorAdjEXT and VertAdjEXT commands defined, but they seem to be amplified versions of the VertAdj and HorAdj commands that I use in the keybinds project, and are relative instead of absolute. I think ED would need to add HorAdj_AXIS and VertAdj_AXIS commands that take an absolute value from the input like they have for some of the other controls (ex: Range_Value_EXT vs Range_Value_AXIS for the ASP controls). @BIGNEWY feature request please for _AXIS versions of map_display_commands HorAdj and VertAdj to be wired up to command_defs for Hind? Also, for anyone having an issue using the keybinds, please note that it is formatted for use with Quaggles Input Command Injector mod: https://github.com/Quaggles/dcs-input-command-injector Once you have that going, you'll put an InputCommands folder in your Saved Games\DCS folder. The base version included in Quaggles mod is the Skeleton version available on the keybinds project - a blank structure for you to add your custom binds to. Or use the full set from the keybinds project with the InputCommands available there in your Saved Games\DCS folder. Also, after updates to DCS remember to toggle Quaggles mod off/on for it to re-apply changes (best practice would be disabling it before updating).

Thanks for the write up. I've been tempted to switch from the G2 to VP2 (clarity) or 8KX (fov)... but my gut is telling me to wait until next year. Maybe an Index 2 will be announced and/or seeing how the Apple VR headset rumors play out..

Agree that saving down to profiles can be a bit of a headache upfront, but when devices get mixed up (and they do for me, often, with my XK-80 pads that have same name that can't be changed), imo saving to profiles is a time-saver. I can just reload a profile from in the game instead of having to edit GUIDs in the Config\Input filenames (after the headache of reworking the GUIDs in my gremlin profile).

Added Virpil collective and control panel! Now at maximum HID devices. Only able to fit control panel under device limit courtesy of Virpil's great design of supporting chaining the panel through the aux port of their bases. Rig is now "complete" for foreseeable future (until VKB releases TECS).

I've got FakeHDR and LumaSharpen running at default values, then in color adjustments of VR_CAS_Color I've got 1.02 for contrast and brightness, and 1.2 for saturation

I use both. I like the color and contrast options available via the reshade plugin, but then have FSR going as well for a little upscaling (renderScale = 1.1). I use the sharpening in both (openvr_mod.cfg sharpness = .75, then the LumaSharpen reshade filter on top of that) as the extra contrast helps me with spotting, especially ground targets.

Random fyi based on some troubleshooting I went through recently.. if you have the NS430, make sure that module is disabled. I've been having trouble with recognition for a while. Almost like it'd recognize every other command. Worked great every time, 60% of the time. Did a lot of voice trainings but that didn't help. Also the comms menu starting popping up... but ONLY for the Ka-50, and redoing the export.lua didn't fix it like it has before when that's happened generally. Also a few other miscellaneous things I had chalked up to bugs or config problems I couldn't figure out. Was re-reading troubleshooting section, and noticed "The Garmin NS340 module must be disabled in DCS module manager." I think I had noticed that before but disregarded it because I don't have the NS430 enabled for any planes... but I did still have the module enabled. Disabled it, and now not having any problems. Working great every time.

first usage impressions after flying the shark, huey, and hind around for about 30 minutes... helicopters all weekend. 30deg cam is installed by default, i'm gonna switch that out for at least the 40deg. still need to tune the friction a bit to find right balance for the lever. and/or maybe add a small counterweight to back of rotor base. throttle doesn't seem in too bad of a position since (at least i) won't use it too frequently during flight. it would be better if it was up next to the grip but not a huge deal for me. i wasn't sure if the idle/off button for the twist throttle would be an actual button, but it is. cool having that mapped for the huey. a little odd for the hind, where have to use that button to get to max throttle by default if axis calibrated where it goes past lock to allow engine shutoff with the huey. can address that with reduced curve saturation in hind. throttle lock switch does not throw a button. movement feels great. thought i might be adding some nyogel (like i do for everything with an axis) but after using it i don't see the need for now. nice rubber feel for the bottom of the sharka grip. everything with the collective and grip has at least met expectations. only issue i've had is i haven't been able to get the control panel #1 i got with it to slave to the rotor base, where (afaik) they should be able to operate as one device.

annnndd.... after cutting off sides of seat.. a couple of U brackets on the back left post of my rig have worked out well.

First impressions: a) it's made well, and b) i have no clue how i'm going to mount it to my rig yet

When that happens to me, it's the WMR portal sitting on the calibration screen (look side-to-side and look at floor). If you load into just the WMR portal (no SteamVR, no DCS), do you see the apartment or that calibration screen? edit: related

Well.... it was supposed to arrive friday... but just got notification that it's with the courier now (thanks DHL!). Exciting.

There might not be many reviews for the Rotor TCS Plus yet - the first batch of them just started shipping this week. I've read some good things and some bad about the non-Plus (ie, odd how the base rotates, some reports that the axis isn't totally linear). I ordered the Plus with the SharKa-50 grip. It's due to arrive within the week. The other option I had considered is something from https://komodosimulations.co.uk/collections/collective ... but have heard lots of good things about Virpil so decided to go that route. I use the thrustmaster pendular rudder for both planes and helis. I think with helis you'd ideally want to have pedals setup with zero spring, and some dampening, so they don't center. I don't feel like switching my pedals around whenever I switch, so I have light springs going, and just roll with it using the rudder trim option in DCS (where when you push the trim button, it affects the rudder position as well). edit to add that virpil also has a UH-60 grip coming (hopefully) end of this year:

I find the RS F-16 grip to work a lot better than the Warthog on the FSSB. Seems to be case-by-case. When I mentioned on hoggit how I couldn't get the Warthog to seat solidly on the FSSB, some people commented they didn't have that issue. I tried it with 2 different Warthog grips, same thing, just one better/worse than the other (slight shift/pop crossing the center vertically.. I was using the angle adapter, maybe that was the issue. When using the RS F-16, it uses the straight adapter since the stick is 1:1 with proper curve so angle adapter isn't needed like with Warthog). The RS F-16 also made me realize when it comes to metal vs lightness, I prefer a light grip (the RS F-16 feels like it's a tenth of the weight of the Warthog). Between how solid the attachment mechanism is for the RS F-16, and how light it is, it feels more precise than the Warthog did. Just the slightest pressure and there's response, where the weight of the Warthog kind of dampened that. The construction/feel of it reminds me of the VKB MCG Pro. (MCG Ultimate really set a new standard for feel vs weight, imo). Another little side note that might be easily missed in the product details for the RS F-16 grip is all the buttons/hats are 5-ways switches (even nws and weapon release). That was big for me because I could mirror how I've got my MCG Ultimate setup (my center stick), with zoom/etc functions on the side hat. Also, under the trim hat is a rotary that allows you to easily switch between configurations. Configuration software is pretty flexible with what you can do with the buttons and such. Here's a screen of it from a different thread I found via google images: updated pic of it as my side stick and vkb as center stick in last comment in my rig thread:

Some really good points being made. I don't have much to add except for one small thing regarding: Afaik, wasn't the russian law that made modern redfor a non-starter enacted rather recently (last year year or two)? Ie, when ED began developing the 16 and 18, there was still the possibility of doing more modern redfor? If that's right, maybe not fair to call it short-sighted.

You said "end of the day most of us"... the "most of us" part is purely speculative. You stated it like a fact. Then I wasn't trying to counter your opinion, I was stating my own opinion in support of the OP's thread. I also don't need to "reduce your facts to an opinion", because it's an opinion to begin with. I have no clue what the majority wants, and neither do you.