sorting by count is done.

in cases of

This crash was only present on profiling branch for a very short time.

Correct, we do not support cloud saves. And we do not plan to change that.
The default user profile name, is the username of the account playing the game. If the username stays the same, every new profile will have the same name.

This happens when joining a server, and the mission download fails.
So you are joining into a mission, while you don't even have the mission file.
This was already fixed, the server must've been running the pre-hotfix A3 version.

That error is directly forwarded from Steam.
Why steam says it, I don't know either.

So basically, it tells the HC to turn it on locally, and print into its own console.

Ihre Organisation hat diese App unter Verwendung von Device Guard blockiert.

And why is this a problem or a bug?

Illegal instruction. Your CPU seems to be quite old.
The bug has been fixed on the performance profiling branch https://community.bistudio.com/wiki/Arma_3:_Steam_Branches, it will be quite a while until the fix makes it to the main branch.

https://community.bistudio.com/wiki/setObjectScale
Scaling is not supported. Bugs like this will not be fixed.

I can see you were pirating our DLCs. If you want support with the game, you better not pirate it.

The game now uses Visual c++ redistributable 2022, not 2013 anymore.
You have 2022 installed, but only the x86 version, the game by default uses the x64 version, which seems like you have not installed.

What is a jamming tower?

What is a "MED pod"?
What are naval scooters?
Which base?

What tank are you talking about? What active protection? This sounds like some mod, which is not anything we would deal with.

What sectors?
What mission are you talking about?

What mission?
Are you talking about some server?
If it doesn't seem like a bug, why are you reporting it in a bug ticket then?

This is fixed. But it would still be broken if a player joins your server using the old Arma version who has disabled automatic updates.
So to fully protect against this, you need to set minBuild in your server.cfg to 152405

The code responsible for this, has been removed on performance/profiling branch, and will also be gone in 2.20. So the issue is already fixed, but won't make it to stable release until 2.20 next year

Fixed 2.20

deleteVehicle has received a local check and should be fixed.
If there is a repro, I need a repro to see whats happening

Oh I see the mistake.

"the cloud file provider is not running"

What is "faulty" input? Examples?

Why would you open the dialog, without capturing anything.
I don't see the usercase.

Should for now be fixed on profiling branch.

Add class name and vehVarName (if assigned) to network objects

https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

That's what you get for pirating

With EF CDLC release

These config entries are only read on Transport vehicles.
On people, they do have the entry in engine, but its always initialized to false, and never read from config.

Fixed in profiling branch v9, and next dev branch.

Cannot reproduce.
Running 2.18 (post hotfix) 2.18.152302
Both working and "broken" buttons work for me.

2.18 prof v6 and later

"DXGI_ERROR_DEVICE_REMOVED" your graphics card got removed or disconnected long enough for the game to die.
Don't know why. You can run the game in fullscreen-windowed mode, and you won't have issues with tabbing out.

The crash there is related to the CPU you are using, not the operating system. It is not supporting a specific instruction.
That code was removed on profiling branch (v6 and later), so it should run if you switch to it.

on profiling branch only. Fixed.

Well yes. The game updated. its now a different version.
The tool Lou posted above, can probably update your savegame.

The patch is out now, please confirm fix

The message, is not the reason that you cannot play. There must be another reason.

I have attached a file including the error message

note: Minidump has been generated into the file C:\Users\pod\AppData\Local\Arma 3\Arma3_x64_2024-10-14_15-29-54.mdmp

I need that file, please pack it in a zip and also upload it here

"saves crash"
What do you mean by crash? I don't see any crash report?

Is it reproducible in an empty mission (Say VR terrain) with some AI's placed down? they are also stuck in animation?

No

Mac update (as every time the game updates) is lagging behind, it takes a while for it to receive the last game update.
And you cannot play on servers that run a newer game version.

fix is on profiling branch tomorrow, serverside installation might be enough to fix it

This was interesting.
We had a big issue with container entities being "leaked" and spamming server logs. So we fixed that.
Turns out, the inventory system requires entities to leak.

https://feedback.bistudio.com/T142540

It was not removed. Dupe bugs should be private tickets, so people cannot look here for basically a guide on how to dupe.
Your ticket was not private, so it was made private manually, but a mistake was made and you were removed access to. I'll fix that.
https://feedback.bistudio.com/T185232

Thank you.
The .txt file doesn't tell you what exactly happened, I don't know if there are any better files.
Please go to %localappdata%/Arma 3 launcher, and see if you find any "dump file" or .mdmp files in there. Pack them into a zip and send them here too. I would expect there to be some.

You have several script/mod issues.

Verify game files in steam?

Please run the game with -debug parameter.
And attach the full RPT log file for this error

As with every game update. The Mac update is slightly delayed. We have no ETA, hopefully soon.

seems like its really only intended to contain objects.

since there can be thousands of them.

See https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

Corrupted game files.
Delete Arma 3/Addons/air_f_beta.pbo
Then verify your game files in steam.

Objects outside of map bounds are not supported.

Visual Studio 2013 c++ redistributable is missing or not installed correctly.

If you want to play the game, you have to buy it first.

We don't have separate crash/script logs.
Won't do.

The freeze dump, is currently inside "modParams" script command. It is looking if a mod's picture exists, and trying to find what PBO it is in.
A freeze dump is only a snapshot of a instant in time. That's why we always write two freeze dumps, so we can see atleast two points and judge where the freeze might be at.