[RESOLVED]2.5.5+ Mission editor static naming stuck on "Ammo"

[Pikey]

I've seen the following.

 

 

if you select a static and place it, then name it anything, if you click away it renames itself to "Ammo". What's more, keep clicking on and off it, renames between "Ammo '001" and "Ammo".

 

If you put a second one down, you can call that anythign too, and it will renamie iself back to Ammo or Ammo #001 and if you keep clicking between the two they keep shuffling renaming themselves between Ammo, Ammo #001 and Ammo #002 incessantly.

 

Is this me or do I need a repair? Should be a quick check to verify.

[Hash]

It's not only You.

I've also checked on missions created and saved prior this patch - click on any static object with right name and it will start changing names to "ammo".

[Nasder]

Just noticed this too. I can rename other units without problem but Static Objects stick to Ammo and Ammo #NNN

[wopski]

Yep same here just logged in to report this issue!

[Capn kamikaze]

Static object names changing to "ammo"

 

I can type in a name such as "Generator 1" for a static object, but once I close that and click on the unit again, the editor is changing it to "ammo" with a # number after it, it's doing it to other units aswell.

[ruxtmp]

I am having the same issue. Wondering if this is why many of my missions wont load and just crash to desktop.

[remus77]

Ditto

 

Same here. Devastating to my mission I'm making for a wing event. Think I could revert to the last patch, keep on designing, and when it's finished, update and play in the current ver?

[Pikey]

https://forums.eagle.ru/showthread.php?t=264356

[TBear]

Same here. This makes lot triggers not work even if they are refferred to "Ammo xxx" names. Also if You click on an abject called Ammo #1, then click to another, then u click back to the first one, this one has been renamed to "Ammo #xxx". Really weird

Edited February 23, 2020 by TBear

[Theodossis]

Agree, happened to me too. Destroyed couple of my missions with static objects... If you rename it without clicking it again, the rename works.

[discwalker]

Cargos are exceptions

 

Those are renameable with ease, but

"planes", "helicopters", and "ground vehicles" statics follow the "ammo" naming scheme

after reselection.

statics_wait_for_hotfix_due_ammo_naming.miz

[Alpenwolf]

Heliports Bug

 

If you place the object "helipad single" or "FARP" from the category "heliports" that unit will have the name "Ammo". And there is no way of changing the name. Even after I do so and unclick the unit, once I click on it again it shows the name "Ammo" every time.

 

 

EDIT:

Looks like it's the issue with maybe all static objects. Just placed other objects and they all end up having the name "Ammo". Other units that are not static objects are fine.

 

 

 

Edited February 24, 2020 by Alpenwolf

[Pikey]

there's two other posts about this

https://forums.eagle.ru/showthread.php?t=264356

https://forums.eagle.ru/showthread.php?t=264585

Come join in there, dont think they have been acknowledged yet.

[Pikey]

and now https://forums.eagle.ru/showthread.php?p=4223767#post4223767

[Pikey]

another post here

https://forums.eagle.ru/showthread.php?p=4223767#post4223767

and

https://forums.eagle.ru/showthread.php?t=264585

 

Would be good to have this picked up. The impact to older missions saved as this version could be catastrophic if anyone uses a name via any scripting to identify something. As it is, making new missions you can no longer do anything with scripts that use prefixes to identify the static. Whilst names are somewhat an abstract convention and ME can change triggers based on the ID, for external scripting that collects groups and counts them according to a name convention you setup eg SET_STATIC:New():FilterPrefixes('Ammo') will now pickup all the statics and farps and give you nightmares. I'm sure Mist has a prefix tool. It completely wrecks some things.

[Hangar200]

Me too…or "Me ninth" about now.

[Alpenwolf]

I can only confirm this:

 

https://forums.eagle.ru/showthread.php?t=264791

[Alpenwolf]

+1

[Nevyn]

+1

[Adamastor]

+1

MIST went all down. Also, can´t pick airborn troops, even DCS standar

[mono6020]

yep. same problem. a total mess

[BIGNEWY]

Merged thread

 

Reported

[TheTrooper]

[ALREADY REPORTED]Static object bug.

 

Hi I don't know if this one has been reported yet.

 

Static object naming issue I found in Open beta 2.5.6. I created a video of it.

 

[Hash]

Yes, it breaks all missions and triggers...

but i think it was reported here

https://forums.eagle.ru/showthread.php?t=264356http://

[BIGNEWY]

Already reported but thank you for your video

 

thread merged

Edited February 27, 2020 by BIGNEWY