Attributes of grouped units synced?

[jarckn]

Arma 3 Version: 1.64 (stable)
CBA Version: 3.1.0 (stable fc3156bfd9cd0d4f4ff4bef4c4ad70a4bb7ed7d3)
ACE3 Version: 3.7.0 (stable 4ae4fca)

Mods:

• @CBA_A3
• @ace
• @rhs_afrf
• @rhs_usaf
• @Show Object ID's Eden plugin
• @task_force_radio

Description:

• In Eden editor: If you change an units property, i.e. ace_isMedic or ace_isEngineer to another value, the values of other grouped units seems to be changed too.

Steps to reproduce:

• Place several units on the field
• Make the units through the attributes-menu an Regular medic, Doctor, Engineer or Specialist.
• Group some of them, for example: 2x Regular with a Doctor as Sergeant.
• Watch as some of the units are going to get new properties.

Where did the issue occur?

• Editor (Singleplayer) / Editor (Multiplayer)

Placed Modules:

• None, raw map (Altis)

RPT log file:

• I have no idea, if rpt files are generated in the eden editor and if so, where to find them. But heres a video proof.

[commy2]

You selected both units... You have to select a individual unit and double click it.

[commy2]

It says in the very first line (green background) "2 Gegenstände editieren" ("Edit two items").

[jarckn]

Yes, because I wanted to edit both.

But take a look at 0:29 in the video: I've selected both "Reparaturspezialist"-units and opened their attributes. I've set both to playable, gave them a rolename and set them as engineer ("Pionier"). Then, I've added an "Truppführer"-unit, set his properties and grouped the four previously created units with him. After that, I've reopened the attributes of one "Reparaturspezialist"-unit (at 1:11). You can see there, that the unit, that should only be a engineer ("Pionier"), is now also a medic ("Normaler Sanitäter"). Just as the "Truppführer". The same happened with the 3 other units, which has been grouped to the "Truppführer", as shown in the video.

Furthermore, I've changed the two "Sanitäter"-units properties back to medic ("Normaler Sanitäter") and the two "Reparaturspezialist"-units back to engineer ("Pionier") and after reopening the attributes of one Reparaturspezialist at 1:58 , both role-properties have been resetted to "Standard". The "Truppführer" has been resetted to standard, even that I haven't done any changes to him since creation.

I don't think that It's really a "synchronization issue" which is going on here. It seems to be randomized, how the settings are set at the end.

[commy2]

If you change any of these properties they become the new default for new units placed. There is nothing that we can do about that. That's how BI decided to do these attributes.

[jarckn]

Good to know!
But that doesn't explain, why these properties are changing after placing all units down.

I've made another video as a proof of concept with a new map: Video
First of all, I've placed every unit, I wanted, down.
The same units as before:

• 1x "Truppführer"
• 2x "Reparaturspezialist"
• 2x "Sanitäter"

Then, I've grouped the 4 non-leader units to the "Truppführer".
After that, I've set all properties I wanted one by one. I did this via the entitylist to ensure, that I'm really selecting the right unit.
After finishing, I rechecked the properties of one "Sanitäter"-unit at 1:15, and hes now both: engineer and medic.

So It seems, that the new default value doesn't narrow on new units, but on already placed aswell.

[jarckn]

After taking a deeper look into the code (CfgEden.hpp in medical/repair addon), I guess I know what you've meant.

I'm not that into arma development, so I have a question:
Wouldn't It be possible to use set3DENAttribute and get3DENAttribute in those two lines:

Line 13: attributeSave = "(missionnamespace getvariable ['ace_isMeidc_temp',0]) - 1;";
Line 25: onToolboxSelChanged = "missionnamespace setvariable ['ace_isMeidc_temp',_this select 1];";

Like:
onToolboxSelChanged = "_this set3DENAttribute ['ace_isMeidc_temp',_this select 1];";
attributeSave = "(_this get3DENAttribute ['ace_isMeidc_temp',0]) - 1;";

I don't know if these two commands work with custom attributes, the documentation doesn't say anything about this.
But this might be an option, to save those options to the entity only, and not to the whole missionNamespace, am I right?

Or am I getting the sense of missionNamespacewrong? :)

[PabstMirror]

Should be fixed by #4905