I confirm fix in rev. 148680
Close ticket, please

ok, I understood
Confirm fix in rev. 148680, might be worth a close ticket

can be closed

Possible to get this looked into please? Really easy to repro with above

@BIS_fnc_KK Is there a chance to still see this addressed one way or another?

So I noticed that this crash occurs due to Arma saving some stuff that it shouldn't.
Maybe because I store displays into global variables, and it tries to deserialize those global vars.

I will add that I am also experiencing this error.
A "Veteran" user from the Discord server advised that I fix the issue "by removing one of the files that tracks subscribed compositions". The only file that I could find that displayed subscribed items, including compositions, was a file called " subscribedcontent.list " located in "...\Documents\Arma 3\Saved\steam\meta". It's true that compositions with the ID can be found there, when it is unbinarised. And it's true that the offending (in my case 2) compositions could not be found anymore on the workshop. However, neither removing the specific entries in the file, nor deleting the entire file, fixed the issue.

I did some further investigating into this issue and i've confirmed the real issue is the 'wheel' animation source is whats broken and nothing to do with UVAnimations. Similarly I've found a better vanilla vehicle with the issue.

где скачать DLC «Контакт и глобальная мобилизация». ????

Прошу помочь разобраться как начать играть. Игру купил если не можете. Прошу вернуть деньги

скачал но не могу начать играть

при входе выдаёт ошибку

Can confirm it seems to happen faster when switching seats in a vehicle.

Crashes upon loading with mods

Thank you for requesting the feature.
Due to the current phase of Live Ops development in Arma 3, we cannot commit to any new features, though we will try to consider them.

I've been wondering if this was possible by now and somehow stumbled upon this suggestion. As outdated squad.xml is, it's what very many active units still rely on.

Hello and thank you for reporting the issue.
Please understand that sometimes to understand the problem we need more information, even if you feel you have already given it.
Either way with the new information i was able to confirm it on our internal build.
We will see what we can do.

Hey thank you for reporting the issue,
I was able to confirm the problem on our internal version as well.
We will see what we can do.

Maybe @reyhard will take a look at this little config error?

Maybe @reyhard can help with this little error in configuration?

should be solved in next devbranch update

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Seems related to https://feedback.bistudio.com/T161292.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for reporting this issue.
We were able to confirm it on our internal version.
We will see what we can do at this stage.

Thank you for reporting the bug.
I checked it on our internal version and i can confirm the issue is in the base.
However due to the current phase of Live Ops development in Arma 3, It is unlikely we will be able to work on this issue.

Thank you for requesting the feature.
Due to the current phase of Live Ops development in Arma 3, we cannot commit to any new features.
Its very unlikely that we will change any of the features mentioned as the mesh is not prepared for it.

Hello, to help we would need more information on what is causing the issue.
Please look in your files for the files mentioned in the link below, with the date of the crash and add them to the ticket.
https://community.bistudio.com/wiki/Crash_Files

rev 148671 changes reverted to the original state. After careful consideration, the issue is now a "won't fix"