[NO BUG] RIO controls inaccessible with version upgrade/downgrade by Pilot

[Pikey]

This is resolved, but it's worth noting findings from yesterday that cost us some time.

 

On version 2.5.5.33552

the Pilot reverted to the previous version in OB to:2.5.5.33184

 

A Rio who had not changed versions, on a server and client version of 2.5.5.33184, on entering the pilots plane, found that no controls worked (HCU unresponsive). In the controls configuration, all axis and button presses worked correctly. We attempted several joins including airborne, both did repairs of DCS and cleaned and the result was consistent.

 

In another plane the affected RIO had perfect controls as a pilot

If the roles were reversed, the old Pilot in the back of the same RIO's plane found he couldn't access his controls now.

 

When both pairs of clients upgraded to 2.5.5.33552, the controls for the RIO worked fine again.

 

From this I've concluded, but could use advice on, that the versions of DCS is not the issue but the version of the module is forever changed in upgrades and downgrades.

 

My main question is, if the module is deleted, will it come back to match the version of DCS? Because no notes are made about this and it could basically nullify the ability to go backwards and forwards in version and retain compatibility in Multiplayer?

Edited July 22, 2019 by IronMike

[IronMike]

ok let me collect that a bit:

 

1. You should not fly mismatching DCS versions online. Yes, sometimes it works, but if something fundamental changed in the module, it wont work, as seen above. (IMO it is best to stay on the latest version of open beta always for online play)

 

2. Module versions cannot mismatch at all. This will cause issues 100%. If the module has not been updated over say two patches, then technically there should not be an issue if both players have each the other version of DCS, since the module version is the same, but even then I would refer to point 1.

 

3. If you uninstall a module and reinstall it again, it will always install to its version matching the DCS version that is installed. Rolling back or updating DCS versions always includes all installed modules, terrains and campaigns.

 

Hope that helps.

[Karon]

Almost correct; we were using the same version when the bug occurred.

 

 

Bullet points so it's more clear:

- he updated to latest DCS OB version;

- I didn't update (I was the RIO);

- he reverted to the previous version;

- the bug occurred;

- be both run DCS_repair;

- the bug persisted;

- we both updated again and the bug fixed itself.

 

 

 

So, technically we were both flying with the same version but by updating and later reverting, he broke something.

I understand this is a quite unique situation but we hope this report can lead to something useful (although I think it's a DCS thing, rather than yours).

[Pikey]

yes, this confirms what I was thinking, that making reversions of the game version doesn't change the module specific versions and it will causes issues. The correct process is then to remove the module and reinstall and it should then tally with the DCS version, which is an interesting point.