Andy t

My ecosystem: TM Warthog on WarBrd TM FA18 on TM base WW stick on WW base VKB MCG on GF3 Comparions: I find that the TM FA-18 grip is feels more "premium" and is of better quality than WW. Also, they are slightly different in size, with TM being 1:1 replica, while WW is slightly smaller. The WW's tiny 5 way hat is a bit of a pain to use. I much prefer TM's approach of having a button and a separate roller with a middle press in the area of "EVENT Mark" switch. I purchased a TM adapter to allow me to use TM on WW base, but didn't install it yet. TM on Warbrd: Configuration: default cams and default "heavy" spring. Issue: due to the TM's grips heavy weight, it feels "bouncy" especially in the center, even with the standard heavy springs. However, I like the linear movement across the entire range (same resistance). TM sticks work without the need for any adapters. TM FA18 on TM base: Stick feel/quality is awesome. The base has some issues, one can even "twist" the stick a few mm when trying to press some buttons. WW stick on WW base: OK stick quality. The base is decent. However, it increases the force necessary to move the stick as it moves further from the center. I don't like this feature and as such an not installing a TM stick on it yet. You can purchase a TM adapter for this base. VKB: Stick feels "toyish" but good base quality.

To add to the problem: some USB on the back of the PC work while others don't for flashing purposes... At this point I am done using their software.

I started up SimAppPro and it prompted me that there was a lot of bios updates for both panels as well as the throttle and the throttle base and the stick (I own WinWing's entire product line). However, my pit is removed from my PC and all of my devices are plugged into powered USB hubs. Getting to the computer either requires a usb extension cable or dismantling my "PIT". I decided to try flashing things while plugged into the USB hub. Unfortunately, the panels went dark due to flash issues. I was able to get both panels and the throttle flashed by using a USB extension cable to the PC. However, the "control panel" - that's attached to the throttle is still dark, despite me trying to plug it into various USB ports, back front, etc - I did find a port that worked... For some reason the USB port that worked for panels didn't work, but I was able to find a working one. This has been a MAJOR RECURRING ISSUE . At this point I blocked SimApp's internet access via windows firewall. While it does prevent "sign in" at least I don't get unwanted firmware forced on to me and have to go through the song and dance every time. Would it be possible to have someone investigate the issues with flashing over USB hubs? I was able to flash VKB and Virpil via a USB hub. Also, the whole "FORCED FLASH" MUST STOP.

When selecting HUD only view (ALT F1), both left and right MFDs are exported on top of each other in the right hand corner with a transparent background. Can you make it appear like all the other modules, where the MFDs are in their respective corners with a solid background.

I am trying to use win wing's exports along with dcs export scripts. It appears that these two "step on each other's toes". Whichever line occurs later in the file, "wins". In the attached example of my export.lua below, the win wing's functionality wouldn't work, while DCS-export scripts (used by ctytler's excellent streamdeck plugin) works. By putting the win wing's export, the behavior is reversed. Before winwing, I was having the same issue with DCS-UFC and DCS-exportscripts not coexisting as well. What could be causing this issue with my export.lua? Are others able to have multiple apps that rely on DCS state export co-exist? Any guides on interpreting DCS's export.lua and other .lua files? local wwtlfs=require('lfs') -- win wing dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[scripts\DCS-ExportScript\ExportScript.lua]]) local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

How are people mapping Win Wing's throttle for A-10C II? Since it's a close replica of Hornet's throttle, it doesn't have all the switches from Warthog. I am curious to hear others' thoughts.

I just installed F-18 grip on an older Warthog base. In DCS, if I move the stick all the way left or right the plane is not getting any input. I have to keep the stick a few milli meters short of max deflection on x axis. How do I fix this? I tried calibrating the stick using USB device panel, but I think it caused issues with VKB stick I have plugged in and didn't fix this issue.

Yes. I only use it for Streamdeck. Could you provide more detail about "turn off individual sending options...". Where/how would I do that?

Greetings, I am also having issues with your app "stepping on" DCS-Export scripts that use with ctytler's Stream Deck plugin. Here is my main Export.lua: In this state, stream deck is working, but your app isn't. If I were to move your export line to be below DCS-ExportScript, your app would work, but Stream Deck wouldn't. I would appreciate any advice/suggestions.

HOTAS discord. Look for winwing channel.

Get the XL. I bought the regular than the XL. Is is able to fit much more without the need for folders. Just getting a Hornet or Harrier UFC on the small one is a challenge due to the amount of buttons.

ctytler's plugin provides widgets that allow for a bi-directional communication with DCS. Another component of a quality streamdeck profile is icons. For that purpose, I use the excellent project Togg-streamdeck. Togg's project can also be used without bi-directional DCS integration. The provided with keyboard .lua's that would allow to use it as is. However, I prefer to customize my key commands it and only use the icons from that project. Ctytler also provides a sample streamdeck profile with DCS integration and Togg's icons for A-10 so you can use that as a reference as to what a finished product supposed to look like.

Thank you! I guess I can't fault WinWing as it seems the real Hornet buttons behave the same way (momentary). I will definitely be keeping my eyes open for F-16 replica.

Thank you for the info! Is there a way to prevent friction lever from friction adjustment? Also, are any of the button on the throttle grip are "Positional" - i.e. they stay in place similar to F-16's DGFT switch? I am wondering which would be the best candidate for that.

If the WinWing's friction lever is used for zoom, how does it affect the actual throttle friction when moving it?

streakeagle - can you share the details/screenshot on how you did that. Thanks!

A few more suggestions (Hornet UFC, specifically but also others): > Consider making the UFC buttons larger > Remove the border around the UFC to increase the actual screen real estate available to working controls > Change radio channel rotaries - they don't appear to work correctly - to buttons

Something, I suspect DCSFlightPanels, changed the name of my VKB MCG Pro by adding a space in front of it. As a result, this caused issues in DCS, etc... I found a guide on how to rename controllers in Windows 10. Any weird/ potential side effects that I should be concerned with before renaming? I have one of everything running through a USB hub: Warthog Throttle VKB MCG Pro MFG Pedals Virpil T50M2 throttle (disconnected) - but I ran its config software Saitek Control panel (with landing gear) 3 TM MFDs

I am having issues with DCSFlightpanels stepping on VKBDEVCFG. For starters, if I press "save" on DCSFP profile, and try to open VKBDEVCFG, the VKB software will hard crash. Also, the VKB Joystick was renamed in windows -a space was added before its name causing issues with DCS, etc...I suspect DCSFP - what could do that?

I remember reading somewhere to set the rotaries to "bufferred" in the button assignment. That should make the keypresses fire faster.

Another vote for changing up radio channel rotaries into simple buttons. So far, works great!

Possibly check the binding in DCS. Probably the middle position of the crank switch is sending "Crank Off" command.

It also hands off targets to HARM and in NAV mode cages VV/Pitch ladders on the HUD.

I like throttles that replicate actual look/feel of ones found military airplanes. At present only Warthog and WinWing offer that. I own a Warthog throttle and while I am satisfied with it, I would love to try WinWing, but I don't need a stick - I already have Warthog on VPC and VKB GF Pro - and therefore I am not buying anything from you.

I am looking for a more information about the button layout/function description of the newer gen SU family (SU-35/30) HOTAS. Any suggestions?