DOF parameters [scale, focusDIstance, blur coefficient]
Sharpness parameters [scale]
Fisheye parameters [aperture, scale1, scale2] (aperture is between 0-180)

Solved in https://feedback.bistudio.com/T163827

Fisheye: https://feedback.bistudio.com/T188336

// Would have to stop pylon commands from working within here to prevent recursion

Fixed in next dev-branch update

ACE team is aware.

Oh my good friend the stack overflow. That's not nice.

If there is a timeout, its in battleye config. If there isn't then it won't be added

and it wrote to me (0xC000001D - STATUS_ILLEGAL_INSTRUCTION)

Your CPU is too old.

We just use Microsofts API to access the Microphone.
For most users it works fine on 64-bit. I looked into it and couldn't figure out why it would fail for some users.

The problem lies in automatic updates being pushed through that break one or more mods and potentially de-stabilize an ArmA unit's ability to play missions until the issues are trouble-shot and fixed(could take hours or weeks).

I'm firin mah lazor!

Indeed. "AddCrewWeight" internally.
When get-in process is finished, it adds 100 to the weight.
When get-out process is finished, it removes 100 from the weight.
There are all kinds of ways this can break, teleporting a unit out of the vehicle should do the same, a player disconnecting and their body being deleted too.
This is unlikely to be fixed because of low impact and complexity in fixing it.

Fixed 2.20

The list of whitelisted addons is not stored in savegame.
When the Curator is recreated when loading a savegame, the addons are default initialized with only the addons that are currently active in the mission.
So it lost any that were added after curator were created (like is the case when you set it to all addons)

You could make it a giant string, the limit for that is 9megabytes? With 2048 arguments, you can pass 19GiB in one extension call.
That should be plenty.

There are lots of odd things about Arma AI :D

It behaves the same as
call x vs [] call x

Stuck on loading screen is a common issue with badly made mods, we introduced the ENDLOAD cheat code to bypass that. But official/vanilla, I've not seen it happen in vanilla yet
https://community.bistudio.com/wiki/Arma_3:_Cheats#ENDLOAD

Also need to consider the mineDelay for mines that do not have a timer.
A tripwire mine with mineDelay = 2, would show timeToExplosion=2, and be stuck at it until something actually triggers it.

You can always fetch the time delay by yourself.

timeToExplosion is only implemented for Bullets with "explosionTime" config entry, basically UGL grenades that explode after certain time.

1/2 were already done with callExtensionArgs and ExtensionCallback.

3. is mostly done, allExtensions command returns signatures. But there is no way to enforce signature checking and only allow loading signed version of extension.

Scratch some part of that.
I can use the same connectToServer hack also for the direct connect UI.
So you have to specifically enter domain and port 0 (or manually empty it (it will be default filled with 2302)) in direct connect.
Then it will try to resolve the port via SRV record, if that fails it falls back to 2302 (same as would've happened before if you left it empty or entered 0 manually)

2.20
https://community.bistudio.com/wiki/connectToServer

This seems to have been done in 2.14
get/setOpticsMode
If wrong, ping me.

What are you doing that 2048 arguments are not enough??

Use getAttackTarget instead. If that is wrong then ping me.

Steam Beta Client was bugged for a while and caused crashes. Valve already fixed it.

Yeah well "cpu: Pentium(R) Dual-Core CPU E6300 @ 2.80GHz"
Too old CPU (That one is from 2009). That code that used the unsupported instruction was removed on profiling branch, but different code was added that uses the same instruction.
Your CPU is just too old, I'm surprised it can run windows 10.
We will not fix that.

Please. Stop openiing new tickets for the same thing.
You are getting an error message, it tells you why its crashing.

secExt_x64.dll That comes from the @Rocket Life modpack. Ask them. It failed trying to get your hard drives serial numbers.

Wiki documentation was wrong. Because https://feedback.bistudio.com/T178348 was not resolved until today. It'll be a thing in 2.20

2.20

??????
MarkerDeleted eventhandler only has two parameters, a string and a bool.
There is no _deleter. Not a bug.

Something is wrong with your Arma, there are lots of non-game files in the game folder. D3DCompiler, d3dx9, binkw, X3DAudio, xactengine?
Please delete all files (not folders!) in your game directory, then verify game files in steam to clean it up.
Does it still not work? Then https://community.bistudio.com/wiki/Arma_3:_Unusual_Process_Exit#0xC000007B_-_STATUS_INVALID_IMAGE_FORMAT (It currently links the wrong c++ 2013, it should be c++2022 now)

I need the crsah report files: https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/
Don't believe what a spam bot is saying, it cannot be graphics card, the error is CPU side. It might be your CPU is too old though.

22:05:02 DX11 error : buffer Map failed : DXGI_ERROR_DEVICE_REMOVED
22:05:02 DX11 - device removed - reason: DXGI_ERROR_DEVICE_RESET

Something is very wrong with that trace file.
The game failed to capture properly, it should not only contain extDB entries.
And no it doesn't seem to be a extDB issue, all the extDB scopes are very short, its just that everything inbetween is somehow missing.
Maybe the normal captureFrame log file shows better info, and its just the trace file that's bad?

"deleteParentWhenTriggered" has a default value of true
"explodeParentWhenTriggered" has a default value of false

Problemo. As usual backwards compat bites back.
Missions tend to spawn Missiles/Rockets/Bombs to cause explosions, by spawning them directly inside the target, expecting it to explode immediately (because it hit something).
For example YAAB benchmark is broken by this, it spawns R_60mm_HE rockets and Bo_GBU12_LGB bombs, both of which have a fuseDistance of 50. So after this change, they just don' t explode anymore.

2.20 and next prof

Should be fixed on profiling branch. There was an error in sorting textures which meant it marked some textures as not being visible on screen

Fixed profiling v26, Arma 2.20

Indeed specifically binarized files.
Just binarizing this

class AddonsMetaData
{
	class List
	{
		class Item0
		{
		};
	};
};

does repro the issue.

place blufor survivor and name "ted"
place greenfor survivor and name bill
place empty ATV
Press play (player is in first placed unit, so ted)
run ignoreTarget script.
Get into driver of the ATV, no crash or freeze.
Drive the ATV and run bill over, no crash.

When I asked for repro I did not expect a 6mb mission.sqm with tons of missing mods.

Fixed on profiling branch and dev and 2.20

The base game has no jerry cans?

You must be talking about some mod, the base game does not have fuel cans?

Montignac? Some modded terrain?

Please upload log files.

1. There is something very wrong with "mfr_dogs" mod.
2. It just says the graphics card disconnected, most likely a driver bug or crash.

Run profiling binary, and profile the game with captureFrame and see where the slowdown is.
It's Arma, not ArmA.

Bit of a problem is that you'd still expect the missile to hit and do damage, like a bullet does, without exploding.
For that we try to simulate it, like we do with UGL grenades. That is based on the projectile's mass, which for missiles is quite large.
So you can now one-shot kill people by shooting them in the chest with a vorona missile :D

Fixed in 2.20

Everyone has the Old man assets, no matter if they own apex or not.
They are in the "Expansion" folder. Verify you game files in steam.

If you want support, you gotta buy the game.

refresh entry is only used for full-screen mode selection.
If you play fullscreen windowed (Which I would recommend) it does not apply.

The RSA messages are known, but they are just noise and don't actually cause any issues.
I tried to fix them but couldn't figure it out and couldn't track down why they happen, its something related to bisign validation, I know our input data into openssl is correct (or rather, the same as on windows) but it just doesn't like it.

Mirror was never implemented, the wiki was wrong, and the wiki has been fixed since then.
5/6 are fixed in 2.20

The crash happened inside Microsofts XAudio code. Nothing we can do about that. We cannot fix Microsoft's errors.

Well I don't know either...
You have submitted 7 crashes.
Each of these is something different, and they all look random and seem to make no sense, and I have never seen any of them before.

The crashing thing seems to be some joystick that you have attached, "vJoy Device"
The crash is actually inside a windows library, nothing we can do about that. Probably just remove your joystick or gamepad.
In the rpt log I also see there are some issues with your joystick

It was ignored for player used weapons, not for AI.

2.20 also adds config entry for map controls
useRealViewport = 1 to enable it by default, then you don't need to use script command

Fixed in https://feedback.bistudio.com/T189016
due to backwards compatibility you need to run a command, or add a config entry to enable it.

Fixed in https://feedback.bistudio.com/T189016
due to backwards compatibility you need to run a command, or add a config entry to enable it.

Fixed in https://feedback.bistudio.com/T189016
due to backwards compatibility you need to run a command, or add a config entry to enable it.

Okey.
Due to backwards compatibility, we need to mess around a bit.

ctrlMapSetPosition, ADDS the position of the controls group, to the position of the map.