reported Can't Launch DCS after 2.7.1.6709

[tasimm]

Ok, here is my log with Logitech G Hub software uninstalled.

dcs.log

[Flappie]

Thanks. Let's compare your logs:

 

Works (G29 plugged in + Logitech software uninstalled):

 

2021-06-15 18:48:14.977 INFO    VISUALIZER: cascade shadows init (preset:'default' quality:4 layers:4 size:4096)
2021-06-15 18:48:15.168 INFO    INPUT: Device [Keyboard] created.
2021-06-15 18:48:15.178 INFO    INPUT: Device [Throttle - HOTAS Warthog {26155C20-A76D-11eb-8005-444553540000}] created.
2021-06-15 18:48:15.178 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {26155C20-A76D-11eb-8005-444553540000}], ForceFeedBack: no
2021-06-15 18:48:15.184 INFO    INPUT: Device [Logitech G HUB G29 Driving Force Racing Wheel USB {8F7C63E0-C5F7-11eb-8001-444553540000}] created.
2021-06-15 18:48:15.184 ERROR   INPUT: Joystick Logitech G HUB G29 Driving Force Racing Wheel USB {8F7C63E0-C5F7-11eb-8001-444553540000} set spring autocenter failed! Not implemented

2021-06-15 18:48:15.190 INFO    INPUT: Joystick created[Logitech G HUB G29 Driving Force Racing Wheel USB {8F7C63E0-C5F7-11eb-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {1ED6DDBB-0401-4498-A093-7D249203200C}
2021-06-15 18:48:15.219 INFO    INPUT: Device [Joystick - HOTAS Warthog {26161F70-A76D-11eb-800B-444553540000}] created.
2021-06-15 18:48:15.219 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {26161F70-A76D-11eb-800B-444553540000}], ForceFeedBack: no
2021-06-15 18:48:15.243 INFO    INPUT: Device [Mouse] created.
2021-06-15 18:48:15.244 INFO    SOUND: Opening audio device "{0.0.0.00000000}.{8082d408-7ea3-496d-a594-80afa61066d4}"
  ...

 

Doens't work (G29 plugged in + Logitech software installed):

 

2021-06-14 20:59:36.931 INFO    VISUALIZER: cascade shadows init (preset:'default' quality:4 layers:4 size:4096)
2021-06-14 20:59:37.211 INFO    INPUT: Device [Keyboard] created.
2021-06-14 20:59:37.220 INFO    INPUT: Device [Throttle - HOTAS Warthog {26155C20-A76D-11eb-8005-444553540000}] created.
2021-06-14 20:59:37.220 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {26155C20-A76D-11eb-8005-444553540000}], ForceFeedBack: no
2021-06-14 20:59:37.263 INFO    INPUT: Device [Logitech G HUB G29 Driving Force Racing Wheel USB {8F7C63E0-C5F7-11eb-8001-444553540000}] created.
2021-06-14 20:59:37.275 INFO    INPUT: Joystick created[Logitech G HUB G29 Driving Force Racing Wheel USB {8F7C63E0-C5F7-11eb-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {1ED6DDBB-0401-4498-A093-7D249203200C}
2021-06-14 20:59:37.311 INFO    INPUT: Device [Joystick - HOTAS Warthog {26161F70-A76D-11eb-800B-444553540000}] created.
2021-06-14 20:59:37.311 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {26161F70-A76D-11eb-800B-444553540000}], ForceFeedBack: no
(END OF LOG)

 

Nothing much to learn here, unfortunately.

[tasimm]

I have zero experience in dissecting these logs, but the only difference I see is that when G Hub is uninstalled it fails the steering wheel centering test, loads the guidFFDriver and moves on.

 

When it’s installed it looks like it finds what I’m assuming is the force feedback driver, (guidFFDriver), but doesn’t test the wheel. After that it seems to hang.

 

I have no idea if this is normal behavior or if it should run the test after it finds the driver.

Edited June 15, 2021 by tasimm

[tasimm]

Problem persists after today’s DCS update.

[KathoriasTV]

Experiencing this as well. I've got a Logitech G29 wheel and pedals. With the Logitech G Hub software installed, DCS doesn't start. Uninstall G Hub, and DCS starts with no issues. Reproducible every single time, with a fresh DCS install.

 

This is not an acceptable long-term solution - uninstalling G Hub gets me reduced FFB functionality in racing sims. And no, I'm not going to crawl behind my desk and unplug things every time I want to play one thing or the other. I've refunded several games when they detected my HOTAS or pedals as a controller and freaked out.

 

Quote

2021-06-19 23:01:17.529 INFO    INPUT: Device [Keyboard] created.
2021-06-19 23:01:17.540 INFO    INPUT: Device [Controller (XBOX 360 For Windows) {7A98F270-B39E-11ea-8003-444553540000}] created.
2021-06-19 23:01:17.540 INFO    INPUT: Joystick created[Controller (XBOX 360 For Windows) {7A98F270-B39E-11ea-8003-444553540000}], ForceFeedBack: no
2021-06-19 23:01:17.540 INFO    INPUT: Device [T-Rudder {7A9B3C60-B39E-11ea-8004-444553540000}] created.
2021-06-19 23:01:17.540 INFO    INPUT: Joystick created[T-Rudder {7A9B3C60-B39E-11ea-8004-444553540000}], ForceFeedBack: no
2021-06-19 23:01:17.585 INFO    INPUT: Device [Logitech G HUB G29 Driving Force Racing Wheel USB {C697F9B0-308E-11eb-8005-444553540000}] created.
2021-06-19 23:01:17.590 INFO    INPUT: Joystick created[Logitech G HUB G29 Driving Force Racing Wheel USB {C697F9B0-308E-11eb-8005-444553540000}], ForceFeedBack: yes, guidFFDriver: {1ED6DDBB-0401-4498-A093-7D249203200C}
2021-06-19 23:01:17.613 INFO    INPUT: Device [Joystick - HOTAS Warthog {7A9B3C60-B39E-11ea-8008-444553540000}] created.
2021-06-19 23:01:17.613 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {7A9B3C60-B39E-11ea-8008-444553540000}], ForceFeedBack: no
2021-06-19 23:01:17.614 INFO    INPUT: Device [Throttle - HOTAS Warthog {7A9B3C60-B39E-11ea-8005-444553540000}] created.
2021-06-19 23:01:17.614 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {7A9B3C60-B39E-11ea-8005-444553540000}], ForceFeedBack: no

 

The last lines of the log.

[mbshaikh]

6 hours ago, KathoriasTV said:

This is not an acceptable long-term solution - uninstalling G Hub gets me reduced FFB functionality in racing sims. And no, I'm not going to crawl behind my desk and unplug things every time I want to play one thing or the other. I've refunded several games when they detected my HOTAS or pedals as a controller and freaked out.

 

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. 

Edited June 20, 2021 by mbshaikh

[mbshaikh]

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

[Flappie]

I'm reading here the G923 wheel uses sound as a Force Feedback input ("True Force").

 

Quote

This system is based more on the audio than on the telemetry of the vehicle so it is slightly different.

 

Can this sound input be disabled in G Hub without disabling FF completely?

iRacing allows this (trueForceVibePhysics=1).

[tasimm]

Telling the GHub S/W not to load at start up seems to be the answer for me until this gets fixed.

This way I can still utilize the pedals as rudders and fire up GHub when I want to play AC.

 

it’s an extra unnecessary step, but it will work for now.

 

UPDATE: I discovered last night that as long as I have load at startup disabled on GHub, I can start the GHub s/w manually and DCS will still work.

Edited June 21, 2021 by tasimm
Updated

[mbshaikh]

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.