holy bonkers my ears :D

Fixed in 2.06, or next 2.04 profiling branch update (probably early next week)

Fixed in 2.04 RC.
I don't know if we'll push a RC branch update

Crash during saveProfileNamespace, can't make out a reason, looks like random memory corruption

All your graphics memory is used up it seems.

They never accepted Team member, as you were already told in Arma discord, "agents" command doesn't return agents.

I agree.

It would have been sufficient to upload your report once instead of 3 times.
Also it would be benefitial if you could actually describe your issue, instead of a title that provides no real info, and log files that don't actually show any issue

Make sure you're actually checking selections in the visual lod.
Your last image says "List Points" which to me sounds like you're listing memory points, memory points are not selections that you can hide.

Alternative would be forced game crash...
I'd rather leave it like this.

supress on position, creates a local object to use as target. which ofc isn't known over network.

It will land in profiling branch v9 today.
Would be neat if you can test it

Found it. Fix is coming

If it still doesn't work in next dev or RC, ping me directly in discord

Does GM have motorcycles?
Crash seems rather random, maybe are you using a USB Headset? thats known to cause issues on windows 10.

So to answer my own question of "What did the error message tell you?"

I already told you. corrupted file, verify your game files via steam. This is the exact same issue as the last ticket

The crashing is not in Arma, its in C:\Windows\USB Vibration\7906\EZFRD64.dll
I have no idea what that is, but its injecting itself into Arma, and its crashing.

Are you using a USB Headset?
Very much looks like it, try unplugging it.

No to any of these

0xDEAD means "read the error message I just showed you before"
Which in your case says

No repro in profiling v8, no freeze no error (error was fixed yesterday)

Cannot reproduce.
I went to campaigns, selected "Drawdown 2035" and it loaded "Drawdown 2035"
maybe profiling v8 fixed it already?

Fixed in v8

Made it for 2.04, rev 147499

Seems like a bug. colorOutside of OutsideTerrain class is never read.
But even vanilla terrains use that parameter, seems like they expect it to be read.

You can upload files. Please don't try to copy paste small parts of the logs.
Just upload the whole file

Thanks for the report, I know where the problem will be.

not gonna make it for 2.04

Please upload your crash report as described here:
https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

Remove all these start parameters. They are all nonsense

Corrupted model. Verify your game files in steam.
If steam doesn't want to redownload anything, delete Arma 3/Addons/weapons_f.pbo manually, and verify files again.

Steam error, nothing we can do

A lightpoint is a point.
Point sources have no direction.

Arma3_x64_2021-03-19_15-03-53
random memory corruption
Arma3_x64_2021-03-19_15-11-21
Same?
Arma3_x64_2021-03-19_15-16-36
Same...
Maybe not so random afterall.

Arma3_x64_2021-03-21_19-27-10
Random memory corruption crash.
Maybe you#re using a USB Headset? besides that not much to go by.

Arma3_x64_2021-03-22_23-51-00
random memory corruption. Possibly related to using a USB Headset.

Arma3_x64_2021-03-24_15-45-03
random crash, can't really make out anything

Do you know if this is a new issue that recently appeared? maybe with 2.02 release?

0xDEAD means the game showed you an error message before killing itself.
What did the error message tell you?

Fix perf v6 tomorrow

2.04 rev 147451

Please upload the report.
Press the left button in that dialog you got.

Nice idea

Nope too much effort

in dev branch

CAn you confirm that its good?

createHashMap creates a empty hashMap.
Same as objNull creates a empty object, and [] creates a empty array.

Workaround fix in profiling branch update hopefully today.

Some mods you are running are doing something weird with the marker placement UI.
The OK button to confirm marker placement is not present, while it should be.

Sadly there is no information about the freeze in your report logs.

Sorry we are not able to solve the USB Headset issue. Its something with Windows 10 and some USB Audio driver, nothing we can do on our side.

Are you using a USB Headset? If so please try unplugging it and checking whether that fixes it.

Fixed thanks to your crash report, we had multiple other reports but none had sufficient information.
Next dev branch, or performance/profiling build will have it.
We might get performance/profiling update tomorrow but not sure yet

We don't have our own whitespace detection code.
https://en.cppreference.com/w/cpp/string/wide/iswspace

play music module

That module is Zeus exclusive, so makes sense its not available.

Fixed in next dev-branch or profiling branch v3

Can you upload your specific composition to the workshop so I can get it for testing?

Arma3_x64_2021-03-02_08-31-08
crash in physx. Maybe verify game files via steam?

That crash should be generating a .mdmp file that I need to see whats causing the crash.
That file isn't in your report logs. It should be in

Looks like corrupted files.
Try letting steam verify your mods, or redownload them.
See if you can reproduce after that

Additional crash report file in the duplicate

Its caused by your Arma profile name

Both crash reports wer inconclusive. Looks like random memory corruption but no indication that its our code.
Maybe something funky with memory allocators

Crash in igd10umd64.dll, intel graphics driver I'd say.
And there are no symbols for it, Intel has a symbol server https://software.intel.com/sites/downloads/symbols/
but EXACTLY that problematic dll is missing, nothing I can do here, or rather not within acceptable time investments.

Caused by a mod that removed items from the scenarios menu.
Found other reports and fixed in Hotfix

Please follow this guide: https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/
I need the report and especially mdmp file.