resolved A-10C and A-10C II mod unplayable after DCS July update

[TheBiggerBass]

A-10 C and A-10C II mod became unplayable after DCS July update. It does no longer respond to pitch/roll/rudder axis. Even complete reinstallition of A-10C/A10C II module did not change anything. Other mods work fine.

Any ideas?

[HC_Official]

check that DCS has not messed up your control bindings (which DCS corrupts from time to time)

[TheBiggerBass]

vor 7 Minuten schrieb HC_Official:

check that DCS has not messed up your control bindings (which DCS corrupts from time to time)

Checked. Control bindings are ok and working as usual. Same result.

[Yurgon]

Your config is stored in Saved Games\DCS, or in full:

C:\Users\{Your Windows Username}\Saved Games\DCS
or
C:\Users\{Your Windows Username}\Saved Games\DCS.openbeta

Re-installing modules and repairing DCS doesn't touch this.

I would first check Saved Games\DCS\Config\Input\A-10C and Saved Games\DCS\Config\Input\A-10C II respectively.

As a first measure, create a backup of Saved Games\DCS just in case.

Then get rid of your config in Saved Games\DCS\Config\Input\A-10C\joystick and see if you can create new axis and keybinds.

DCS shouldn't change this config with an update, and mine has been working fine since at least DCS 2.5 with no interruptions (except when I upgraded to a new joystick base, or when I moved my config to a new PC so I wouldn't have to bind multiple controllers in dozens of modules across several DCS installations from scratch ). No idea why yours got corrupted, but it's almost certainly tied to something within Saved Games\DCS

[TheBiggerBass]

Ok, got it.

Controls were still working but only responded in very slow motion. After pushing trim nose down button pitch/roll/rudder axis are working normal again now. I have seen this strange behaviour before with FC3 mod, also with another stick (Turtle Beach VelocityOne flight deck). Seems to be a bug in DCS input modul.

[Yurgon]

You could try a DCS repair, only costs a few minutes.

Otherwise, I'd try and rename the entire Saved Games\DCS and start with a blank config just to see if the issue persists.

[BIGNEWY]

disable forcefeedback in dcs settings and see if it helps 

[TheBiggerBass]

vor 3 Stunden schrieb Yurgon:

You could try a DCS repair, only costs a few minutes.

Otherwise, I'd try and rename the entire Saved Games\DCS and start with a blank config just to see if the issue persists.

Well, that would be a major task for me. I have all maps, most of DCS modules and several mods. My web connection is just 50MBits. A complete DCS reinstalltation would be >1TB download for me. But I guess it also would not change anything. As I wrote above I already found a workaround and I have also seen the error before with completely different settings.

vor 3 Stunden schrieb BIGNEWY:

disable forcefeedback in dcs settings and see if it helps 

It was already disabled.

Edited Wednesday at 03:45 PM by TheBiggerBass

[BIGNEWY]

can you attach your dcs log, we may see some clues

Ive checked my public version and all seems ok 

 

[Yurgon]

34 minutes ago, TheBiggerBass said:

A complete DCS reinstalltation would be >1TB download for me.

Uh, no. Do NOT touch your DCS installation directory. No need to do that. That is C:\Program Files\Eagle Dynamics\DCS World by default, and there is pretty much no reason for you to do anything to that directory whatsoever.

A DCS repair will go through this installation directory and check for broken and missing files. It should only take a few minutes and your Internet connection should be perfectly fine.

What I'm suggesting is to rename Saved Games\DCS instead. That's just your config and stuff. DCS is going to download exactly nothing at all when you rename Saved Games\DCS.

Then check if the issue persists and report back. In either case, you can later remove the newly created Saved Games\DCS and rename your backup back to this name and you'll have all your settings back.

38 minutes ago, TheBiggerBass said:

As I wrote above I already found a workaround and I have also seen the error before with completely different settings.

Well if you want to figure this thing out and get rid of it altogether, or learn how you can tackle it in the future, let us know.

If I understand correctly that you can now control the A-10 in a kind of degraded manner where you always have to apply nose down trim before the controls start to respond normally, that sounds less than optimal, but if it's good enough for you, then happy flying.

[TheBiggerBass]

vor 17 Minuten schrieb Yurgon:

What I'm suggesting is to rename Saved Games\DCS instead. That's just your config and stuff. DCS is going to download exactly nothing at all when you rename Saved Games\DCS.

Then check if the issue persists and report back. In either case, you can later remove the newly created Saved Games\DCS and rename your backup back to this name and you'll have all your settings back.

I guess that disables all mods in Saved Games, correct? Ok, I will check that.

vor 17 Minuten schrieb Yurgon:

If I understand correctly that you can now control the A-10 in a kind of degraded manner where you always have to apply nose down trim before the controls start to respond normally, that sounds less than optimal, but if it's good enough for you, then happy flying.

I need to push nose down trim only once at the start of a flying session. The work around works, however I would like to eliminate that.

Edited Wednesday at 04:43 PM by TheBiggerBass

[Yurgon]

9 minutes ago, TheBiggerBass said:

I guess that disables all mods in Saved Games, correct? Ok, I will check that.

Yup, exactly. Which, incidentally, you should always do as a very first step in troubleshooting anyway.

10 minutes ago, TheBiggerBass said:

I need to push nose down trim only once at the start of a flying session. The work around works, however I would like to eliminate that.

Yup, sounds annoying. However, I'm not sure if this is something DCS actually does - does your stick work when you look at it in the Windows game controller dialog before pushing the trim button?

I recall the TM F-16 FLCS needed to be woken up with a single tap on the MSL STEP button. Haven't heard of any current day hardware that does this, though.

Might also be worth trying different USB ports. Maybe it's some kind of USB power saving that was enabled through a Windows update?

It sounds like something that DCS would have no control over - unless you have mods that mess with DCS' input handling, hence the suggestion to rename Saved Games\DCS and try with a clean config.

[TheBiggerBass]

The stick (VKB Gunfighter 4 ultimate) works fine in A-10C (II) DCS controls menu. It also has worked with A-10C (II) module before and still does with all other DCS mods. I don't think it's somehow related to the USB port, stick hardware or driver. But, as mentioned before, I have seen the same strange behaviour with my previous stick, a Turtle Beach VelocityOne flight desk and another module (FC3).

[Czar66]

9 minutes ago, TheBiggerBass said:

The stick (VKB Gunfighter 4 ultimate) works fine in A-10C (II) DCS controls menu. It also has worked with A-10C (II) module before and still does with all other DCS mods. I don't think it's somehow related to the USB port, stick hardware or driver. But, as mentioned before, I have seen the same strange behaviour with my previous stick, a Turtle Beach VelocityOne flight desk and another module (FC3).

I've never seen such issues (VKB here too). This looks like it is on your end.

Do you have a gamepad connected in any way or another controller connected that's causing interference on the same binding?

[TheBiggerBass]

Just made some more tests. Disabling the option 'Synchronize Cockpit Controls with HOTAS Controls at Mission Start' in Misc menu seems to fix it. However I don't know why.

[BIGNEWY]

2 minutes ago, TheBiggerBass said:

Just made some more tests. Disabling the option 'Synchronize Cockpit Controls with HOTAS Controls at Mission Start' in Misc menu seems to fix it. However I don't know why.

good to hear you have it resolved, no idea why that would create the problem however, Its just for syncing your hardware switches to the game at the start of a mission.