Jump to content

Can't Launch DCS after 2.7.1.6709


Recommended Posts

Updated to 2.7.1.6709 and I’m unable to launch. I play in VR with an Oculus Quest 2, I’ve updated, removed all mods, repaired, and tried without VR. It launches the title screen on pc and the application screen in oculus and just loads indefinitely. Any help would be hot.

Thanks

 

dcs.log

Link to post
Share on other sites
Posted (edited)

The log cuts off when detecting controllers/joysticks so there is no info about crash there.

But you can try to rename the C:\Users\User\Saved Games\DCS.openbeta Folder to something Like "DCS.openbeta_OLD" and then running the game and see if that solves that issue if so then your save game folder was corrupted, you can copy some of things such as controls and liveries from it and paste into the new generated one.


Edited by RosyPlays
Link to post
Share on other sites

Is this still an issue with the OB patch released yesterday?

Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 1TB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

Link to post
Share on other sites

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?  

  • Thanks 1
Link to post
Share on other sites

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. 

  • Thanks 1
Link to post
Share on other sites

Bug still in effect as of today. Pretty positive it is the ‘driving wheel bug’. Files from such as bazar and shaders like cloud.fx are missing yet verifying through DCS does not show any problems. Any ujr I use doesn’t seem to hide the wheel.

Link to post
Share on other sites

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!

Link to post
Share on other sites

Have any of you with this issue tried removing the Logitech G Software? I had the same issue, and it went away when I uninstalled it, returned when I reinstalled.

  • Thanks 1
Link to post
Share on other sites

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. 

  • Thanks 1
Link to post
Share on other sites

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.


Edited by mbshaikh
Link to post
Share on other sites

I see the name of the joystick gets incredibly long when G Hub is installed ("Logitech G HUB G29 Driving Force Racing Wheel USB"). Since your issue goes away when you uninstall the software, I guess the device name changes and gets shorter. Can you please confirm my theory?

 

I don't know if there is a way to change the name of a device but if it is possible, I'd like to test this.

Link to post
Share on other sites

I was able to change the name of one of my devices. I named it exactly like yours but DCS is still able to reach main menu: this is definitely not a name issue.

 

2021-06-14 22:21:23.863 INFO    VISUALIZER: cascade shadows init (preset:'default' quality:4 layers:4 size:4096)
2021-06-14 22:21:23.949 INFO    INPUT: Device [Keyboard] created.
2021-06-14 22:21:23.973 INFO    INPUT: Device [Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}] created.
2021-06-14 22:21:23.973 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}], ForceFeedBack: no
2021-06-14 22:21:24.006 INFO    INPUT: Device [Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}] created.
2021-06-14 22:21:24.006 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}], ForceFeedBack: no
2021-06-14 22:21:24.007 INFO    INPUT: Device [VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}] created.
2021-06-14 22:21:24.007 INFO    INPUT: Joystick created[VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}], ForceFeedBack: no
2021-06-14 22:21:24.008 INFO    INPUT: Device [Logitech G HUB G29 Driving Force Racing Wheel USB {F21FC040-73B8-11e2-8001-444553540000}] created.
2021-06-14 22:21:24.008 INFO    INPUT: Joystick created[Logitech G HUB G29 Driving Force Racing Wheel USB {F21FC040-73B8-11e2-8001-444553540000}], ForceFeedBack: no
2021-06-14 22:21:24.034 INFO    INPUT: Device [Mouse] created.
2021-06-14 22:21:24.042 INFO    SOUND: Opening audio device "{0.0.0.00000000}.{6d06dd60-d65e-4a14-bfc9-cb695b02060e}"
2021-06-14 22:21:24.042 INFO    SOUND: Speaker layout: auto
2021-06-14 22:21:24.045 INFO    SOUND: Driver reports 2 channels with mask 0x3
2021-06-14 22:21:24.045 INFO    SOUND: Using 2 channels at 48000 Hz
2021-06-14 22:21:24.045 INFO    SOUND: Channel layout: Headphones/Stereo
2021-06-14 22:21:24.061 INFO    SOUND: Opening audio device "{0.0.0.00000000}.{6d06dd60-d65e-4a14-bfc9-cb695b02060e}"
2021-06-14 22:21:24.061 INFO    SOUND: Speaker layout: forced_stereo
2021-06-14 22:21:24.062 INFO    SOUND: Driver reports 2 channels with mask 0x3
2021-06-14 22:21:24.062 INFO    SOUND: Using 2 channels at 48000 Hz
2021-06-14 22:21:24.062 INFO    SOUND: Channel layout: Headphones/Stereo
2021-06-14 22:21:24.081 INFO    DCS: gDescription: "NVIDIA GeForce GTX 1080 Ti" gVendorId: 4318 gDeviceId: 6918 gMemory: 11127 MB
2021-06-14 22:21:24.096 ERROR   EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH
2021-06-14 22:21:24.096 ERROR   EDOBJECTS: Destruction shape not found GAZ-66_P_1
...

 

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...