reported Confusion with non-CW and CW control bindings bug and workaround

[imacken]

I started a thread here

which started off with me asking a question about the confusion over CW and non CW bindings in the Spit module.

It ended with me taking some time to investigate this behaviour, and coming up with conclusions about what is going on so that we all understand it.  

Here is what I said in one of the posts in that thread:

'I was interested in what is going on here, so I made some investigations.

I deleted (renamed) my Input folder so that DCS would create a new one on demand.
I loaded DCS and started in a non-CW mission, made a bind, and a SpitfireLFMkIV folder was created in a new Input folder
Quit that mission, loaded a CW one, then the bind above was there from the SpitfireLFMkIV folder
I then made a bind while still in CW mission, quit, then loaded a non-CW mission.  Bind was there and still only SpitfireLFMkIV folder.
However, I then quit out of DCS, reloaded, then started in a CW mission, there were no binds.
I made a bind, and then a SpitfireLFMkIVCW folder was created, and the binds applied to the non-CW missions as well.

So, conclusion 1) is that whatever variant you start in, the binds in the appropriate folder apply in that session to both variants.
This is awkward because, for example, if you start in a non-CW mission, make a bind change, then the next time you load DCS, if you start in a CW mission, the change will not be seen. This means that you have to make any bind changes to both variants by starting a mission for both on a DCS loading, or copy and paste the relevant folder.

The next question was, what does selecting from the main DCS UI menu ‘Options>Controls>SpitfireSim’ do?
1) If no mission has been loaded, or, if you loaded a non-CW mission, then changes made there are directed to the SpitfireLFMkIV folder and apply to both variants within that session’s missions.
2) If a CW mission has been loaded and quit from, then any changes in the main DCS menu are applied to the SpitfireLFMkIVCW folder and apply to both variants within that session’s missions.

In conclusion,
1) Binds apply to both variants and are dependent on what mission you have loaded first. If it was a non-CW mission, then the binds in SpitfireLFMkIV apply to both within that session. If it was a CW mission, then the binds in SpitfireLFMkIVCW apply to both variants within that session.
2) Changes made in the main UI Options>Controls menu are applied to SpitfireLFMkIV if no mission has been loaded, but if a mission has been loaded then changes are made to the variant folder of the mission that was first loaded.

All in all, this seems like a mess, and I’m pretty sure that this is not the way ED want this to work.

I feel we should raise (or update) a bug report on this after this. Unless someone else has already come to the same conclusion as me, of course!'

So, hopefully, ED will look at this and will now be able to reproduce the issue every time and raise a bug report.

[NineLine]

I will take a look soon, thanks.

[imacken]

@NineLinehave you had a chance to look at this yet?

[imacken]

@NineLinebeen 3 months now. Have you had a chance to look at this yet?

[NineLine]

I havent heard anything back from the team yet, I will kick the can again and see if I can get some answers. 

[imacken]

Thanks a lot, BN. Any help appreciated in this annoying situation for Spit flyers.

[Proteuswave]

Bump... Any update on this issue?

[Habu_69]

DCSW 2.8.5.40170. I have a similar issue. If I start DCS and directly start a P-51D-30 mission, only the default key commands load -- none of the joystick commands. No amount of controls applet manipulation, other than loading them from a saved file, restores the joystick assignments. If I start DCS and first go to the DCS config controls applet, all the key and joystick command assignments are present and I can then load a mission and fly it normally. A full repair made no change to the behavior. I must always check for controls joystick assignments prior to flying.

 

[imacken]

Yes, it's the exact same situation.  It happens in the OB and Stable versions.

So, the workaround is basically the same as the Spitfire. You need to copy the folder from Saved Games\DCS.openbeta\Config\Input\P-51D-30-NA to Saved Games\DCS.openbeta\Config\Input\P-51D and pretty sure you'll have to do that every time you make a bind change.  I might be wrong there as I don't use the P-51 often.

Post in the P-51 bugs forum and link to this thread. Maybe after a year we'll get some action on this.

[NineLine]

On 6/5/2023 at 2:35 AM, imacken said:

Yes, it's the exact same situation.  It happens in the OB and Stable versions.

So, the workaround is basically the same as the Spitfire. You need to copy the folder from Saved Games\DCS.openbeta\Config\Input\P-51D-30-NA to Saved Games\DCS.openbeta\Config\Input\P-51D and pretty sure you'll have to do that every time you make a bind change.  I might be wrong there as I don't use the P-51 often.

Post in the P-51 bugs forum and link to this thread. Maybe after a year we'll get some action on this.

I dont see this on the P-51 here. 

[imacken]

Yep, still the same for the P-51.

Here is how to replicate:

1) check that there are 'P-51' and 'P-51-30-NA' folders in SG Input.

2) run DCS

3) load Instant Action P-51 'P-51D D-25 Ferry Scramble' and make a bind change. (Make sure it's the D-25 mission.)

4) QUIT TO DESKTOP. (Don't just quit back to main DCS menu.)

5) run DCS

6) load  Instant Action P-51 'P-51D D-30 Ferry Scramble'. Bind change made above has disappeared!  (Make sure it's the D-30 mission)

[NineLine]

Ok, I got a good solid reproduction of this, reported for the P-51 and Spit. 

[NineLine]

This is fixed internally, please back up your control settings as it could be possible that you will lose assignments when this change comes through. I have not tested it yet but wanted to let you all know. Thanks.