I understand, thank you for your time.

I would also like to add I have tried deleting everything Arma related out of Windows Registry at this point, as some has said that fixed it for them. It did not in my case.

help me pleas

Idk why it says OS windows 7 its a ps5 not pc

Yup, I’ve already did that on multiple occasions. Also what’s really strange is that all the video settings seem to only save on display when i change them to the same value (High, or Low for example) but after saving the do no impact on the game graphics

I have found sort of a workaround. I have another computer in my house that is hardwired (Ethernet) the one that gives me the error is on WiFi. I'm not sure if this has anything to do with it... But I logged into steam, cloned the git repo for my mod, it uploaded the first time 👑 I still really hope to solve it this as my other computer is like a home theater and doesn't have a desk I can work at

ah sorry sent wrong one, but seems like the updates caused problems with "opencl.dll not found" error. this causes freeze and no logfile. Seems that reverting to earlier driver and then re-installing AMD cures the problem of crashes but there does seem to be a lot of stuttering in game even though fps is 144.

Hello kgr12.
Running the game on Linux client side is not fully supported. The game might run but we do not guarantee it will be without issues.
Regards,
Geez

Thank you for the report.
All hacking incidents are being investigated by BattlEye.
Regards,
Geez

Thank you, confirmed!

In T192598#2823054, @LouMontana wrote:

gaslighting

yeah right, that's what we do!
so we are both editing the issues list and not admitting to having issues by not adding them to the Known Issues list. I guess we just can't win :-)
or, hear me out, the page was updated a couple of hours later because of not being synchronised with the data release… but that may just be an excuse again!

Inside is also still up.

Hello, the base is still up. I am there now having a look and everything is still intact.

In the custom terrain of 2.18, this command is completely invalid, and the helicopter will ascend to 200 meters

Hello.
This is not something we can do unfortunately.

Additional comment:
Seems the randomization is broken as well on restore layer to default.
A test to randomly spawn 1 object it always spawns the same object when using restore layer.

Server is 4061 North America MI

Thank you.
These are being looked at.
Regards,
Geez

Hello BaconBuns.
Unfortunately the archive you have sent only contains dump files from april and february.
Can you please check for more recent ones?

Unfortunately not at the moment. The issue was not reproduced nor was reported from other users. It could be caused by the specific setup you are using.

Wouldn't removing the double quoting be considered a breaking chnage, as extensions would need to be edited to not handle it anymore.

We also have toJson now to generate a giant string.
But, passing it to extensions is very annoying because it double-quotes the string. I want to fix that anyways.

The wiki is wrong, the default is not nil.
The default is nothing, if the value is not there, _this is not set.
It behaves the same as call.

Signatures is possible, BattlEye is not

Problem is the game does not have the languages.
At game/mission start, when loading stringtables, it only reads the configured language and skips over everything else.

Spam is not appreciated.

Should not be any slower, I also made the sorting multithreaded. So it should be much faster too, and in my tests it was.

BattlEye had an outage.

Action scripts are recompiled everytime IF they just contain a script fileName, in that case they essentially do a execVM.

In T192649#2822848, @dedmen wrote:

Well if the server crashes, then we need the crash report files from the server.
Of course you loose connection when the server crashed.

In T192598#2822812, @LouMontana wrote:

It is present in the Known Issues list:

The fact that this info is in the Known issues list is just an excuse. And a bad one at that. The known issues list wasn't even updated until a few hours after the update (at least the date of last update mention in the Known issues main page), which means this was an unintended result, aka, a screwup. If this was an intentional change (or even an issue that had been noticed before the update in internal tests) this information would have been in the changelog, not in the known issues. Please stop gaslighting your loyal players.

How can I assist?

It'll be a simple issue in the shaders. But the impact is probably too low to invest time into it

The backpacks in vehicles (not just quads) are generally hidding to prevent clipping issues.
For example sitting in a seat with back support, you wouldn't want your backpack glitching through it.

https://github.com/WolfCorps/gf_scripts/blob/master/addons/gf_scripts/functions/fn_p_makeUnitCurator.sqf
I use this script to give units zeus access.
It spawns ModuleCurator_F in script, same as you show it.

There is no way to reproduce this problem.

@Geez

But what if both muzzle and magazine have different soundTypeIndex, how do we choose?

It was a BattlEye outage

A proposed fix was pushed in Profiling branch v31
It will reappear in 2.20 v1