mbshaikh

Hi All, I have just finished up on a custom collective I made so I could fully enjoy the new helos. I really wanted the new Virpil unit but felt it was a bit out of my price range so decided to see what I could come up with myself. I’ve never really made anything custom like this before, so it was a learning experience. Still, I’m quite pleased with the result. Some technical facts: 1. Four momentary buttons, four two position switches, two analog joysticks, a slider and a rotary encoder. This is in addition to the collective axis. 2. Each axis sends a joystick button press at the extremes of its range, so any axis can be used like a digital button. In this way the hats and slider can be used digitally as in the KA50. 3. The rotary encoder can send either button presses or be used as a virtual axis. I use it as the throttle, since I wasn’t skilled enough to make a twist grip. 4. The whole thing is powered by an ESP32 microcontroller in the grip. It runs over Bluetooth. Next small upgrade will be to attach a 10000mah power bank under the boot to make it completely wireless. 5. Constructed out of a few handful of 3D printed parts, but mostly out of hardware from Home Depot. A lot of plumbing parts have been used. For example, the handle is PVC pipe covered with foam rubber pipe insulation, and the counterweight for the unit is an iron tee connector. The clutch that keeps the handle in place is a cut piece of nylon tube connector under great pressure (the end result stays in place and yet moves very smoothly with very little force needed) The bracket to connect to the chair is made out of a metal strap tie and some wood. The unit is removable from the chair in seconds by removing a single bolt. My sanding and painting work is questionable but good enough for my needs. All in all a super fun project, and I’m almost disappointed it’s finished. I need to find something else to build now! Anyhow, any comments or questions welcome!

For whatever reason tasimm’s solution does not work on my end. If the Ghub software is running and my wheel is connected, DCS simply does not load. The only way I can get DCS running with the wheel still connected is to do a clean boot without loading Ghub on startup and without running Ghub at any time prior to loading DCS.

One other data point for troubleshooting this problem in case helpful. I have found that on my PC, if I do a clean boot without loading the G923 software (ie turn off loading on startup) DCS will run ok with the wheel connected. However, if I open the software DCS will not run, even if I try again after closing the software. It seems to me as if loading software configures the wheel or USB configuration in such a way that it no longer works with DCS, and only a reboot will clear it

For what it’s worth, I used to have terrible trouble too with various games getting confused by my controllers. But my life got much better when I bought one of these https://www.amazon.com/Sabrent-4-Port-Individual-Switches-HB-UMLS/dp/B00BWF5U0M/ and use it to turn off and on my various controllers as needed. Much easier than unplugging and saves wear and tear on the ports.

While not strictly on point, I thought I'd pass along that my experiment with making my G923 pedals standalone to resolve this problem has worked perfectly. Using an arduino I was even able to make the device have axes for the individual pedals, as well as a combined rudder axis that averages two pedals. This means that I don't need to use Joystick Gremlin to combine axes anymore and both driving and flying sims work fine with my pedals without messing with software (and DCS does not crash as long as I disconnect my wheel). Happy to share the instructions/code if anyone is interested.

Thanks so much for your help on this Flappie! Attached is my log from last night, with full debug info enabled dcs.log

Thanks tasimm! I can confirm that uninstalling the Logitech g hub software works for me too. Unfortunately that isn’t a long term solution as I lose some wheel functionality doing that (mainly the Trueforce feedback on the g923). But at least we can narrow it down to a software conflict between DCS and the Logitech software My temporary solution until a proper fix is in place is going to be to use an arduino board to set up my pedals as a standalone device so I can disable the wheel for DCS while keeping the pedals working.

I agree this appears to be the “driving wheel bug.” Can someone on the Beta team confirm that the dev team is aware of the issue? It’s made DCS essentially unusable for me as I have no rudder control until it’s fixed (time to practice F14 RIO duty I guess!). Happy to help provide any additional data as needed. Thanks!

As a further update, I can confirm that if I start up DCS with the logitech wheel disconnected and then connect it, DCS immediately stops responding with the last line of the log file being: 2021-06-04 22:25:37.241 INFO INPUT: Joystick created[Logitech G HUB G923 Racing Wheel for PlayStation 4 and PC (USB) {6E3CA7D0-AD06-11eb-8009-444553540000}], ForceFeedBack: yes, guidFFDriver: {1ED6DDBB-0401-4498-A093-7D249203200C} I have been trying to get DCS working with the wheel by using HIDguardian to block the wheel while allowing Joystick Gremlin to see it, but so far no luck as DCS seems to always see the wheel if connected.

I am having the exact same problem and for me at least i've narrowed down the cause. Since the recent major Open Beta update, the game will hang on startup IF I have my Logitech g923 connected. If I disconnect the wheel, it loads fine. My log looks extremely similar to Silver Dart's except I see he is using a G29. Try removing the wheel and see if it solves the problem. Of course, since my wheel has my rudder pedals, this is not a real workable long-term solution but at least it might narrow down the problem some. Maybe something to do with detecting force feedback?