Duplicate unit names no longer auto-increment.

[Tippis]

It may have happened in an earlier patch, but not that much earlier and I only noticed it on the Dec. 4 patch (DCS 2.5.5.40603 Open Beta), but if you enter a duplicate name for a unit, it will no longer add an increment at the end of the name and instead revert to its previous name.

 

It used to be the case that you could iterate through a group and just change the unit names to the same thing, and the editor would detect that these names were duplicate and add an incrementing number at the end to resolve the conflict.

 

You'd have Unit #001, Unit #002, Unit #003 etc. and go through and paste "MBT" for every name, and up with the units being called MBT, MBT #001, MBT #002 etc. This no longer happens. Instead, if a conflict is detected, the name change simply doesn't happen and the unit name reverts to what it previously was.

 

So instead of

"Unit #001" -> paste "MBT" -> new name "MBT"

"Unit #002" -> paste "MBT" -> new name "MBT #001"

"Unit #003" -> paste "MBT" -> new name "MBT #002"

 

you now get:

"Unit #001" -> paste "MBT" -> new name "MBT"

"Unit #002" -> paste "MBT" -> reverts to "Unit #002"

"Unit #003" -> paste "MBT" -> reverts to "Unit #003"

 

This makes mass-renaming of large groups quite annoying since you either have to manually add differentiators every time you paste in a suitable unit name, or go through a fiddly process of only selecting the "Unit" part of the name before pasting in what you want, retaining the numbering for the unit.

[TheBamse]

I can confirm on my end too with 2.5.5.40603

[discwalker]

working as intended in 2.5.5.40647

 

for aircraft and vehicle groups

2,5,5,40647auto_increment_duplicates_ok.miz

2,5,5,40647auto_increment_duplicates_unitnames_ok.miz

Edited December 6, 2019 by discwalker

[BIGNEWY]

Hi all

 

We are unable to reproduce this issue.

 

Please remove all unofficial modifications and run a cleanup and repair.

 

then test again if you still see the same would someone please make a short video showing the issue and attach your dcs log straight after so we can look for clues

 

thank you

[Tippis]

Nah. Glitch in the matrix.

It seems to be back to normal in build 40647.