Repro steps :

• Replace C:\Users\<windows_login>\Documents\Arma 3 - Other Profiles\<arma_player_name>\<arma_player_name>.vars.Arma3Profile with eRazer.vars.Arma3Profile (see attachments)

• Add test.Stratis mission (see attachments) to C:\Users\<windows_login>\Documents\Arma 3 - Other Profiles\<arma_player_name>\mpmissions

• Start test.Stratis mission and open Arsenal by executing commands from open_arsenal.txt (see attachments) in debug console

• Check profile "mace_tanoa_east_mg" and notice that it is grayed out and when you click on it the Load button is active (which is an abnormal situation, the Load button should also be grayed out)

• Click on "mace_tanoa_east_mg" profile and then push the Load button (the profile is loaded although it doesn't match BIS_ADDVIRTUALWEAPONCARGO_CARGO)

Another strange thing:

• Save "mace_tanoa_east_mg" profile it under a different name (eg: "my_test_profile")

• Before closing Arsenal load "mace_altis_west_rifleman" profile (which is different from "mace_tanoa_east_mg" profile)

• Open Arsenal by executing commands from open_arsenal.txt (see attachments) in debug console

• Notice that it is possible to load "mace_tanoa_east_mg" profile, but it is not possible to load "my_test_profile" profile even though it is identical to the problematic "mace_tanoa_east_mg" profile (it should be identical since "my_test_profile" was saved after loading "mace_tanoa_east_mg" without any changes)

• Looks like newly saved profiles are working correctly, could this bug affect profiles saved before patch 1.64 only?

Request: players should no longer load profiles that don't match BIS_ADDVIRTUALWEAPONCARGO_CARGO variable?

Note: I can't ask players to delete their old profiles to fix this issue