_self set ["#base.#create", DICE_fnc_hmo_onCreate];

https://community.bistudio.com/wiki/ignoreTarget

you really want T178693 so we'll do that there

Destroy task. transitions into a so called "Brown Move" when it cannot find the target.
They then issue a move order to the targets last known position.

All that was viable has been done for 2.18.
If there is new stuff then probably a new ticket for that (link it to this one tho)

Probably not 2.16
2.16 profiling branch though, shall be good enough

Storing stringtable keys, like "Is this defined" would be acceptable in this specific case. And also the package/container names would be okey in this specific case.
But this only applies to base game's stringtables from un-encrypted PBO's. For CDLCs I would say no.
I assume your mostly vanilla mission is unlikely to use CDLC stringtable keys anyway.

We will add a "Auto" ultra-wide option. That should take care of you.
Its the same as the old Auto but it disables triple-head.
Dev branch tomorrow. maaybe profiling branch

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

Newtarget is not feasible.
Target is already detected before its known. NewTarget triggers, while nearTargets still returns empty list.
Then when unit becomes known, it appears in nearTargets, but NewTarget wouldn't trigger, because the target has already been in the list, it was just updated. And for that we already have KnowsAboutChanged.
Looks like a won't do.

We'll try to research and provide some documentation on the timeouts of different WP types.

ENDLOAD cheat code. Does the same as the internal key combo
Next week dev branch

That message isn't easy to expand.
Also this is not problematic. It means it ran past our pre-allocated storage. The array will just expand dynamically and work fine. It just means we allocate twice.
Unless it spams that message, its not actually a problem that needs solving.

next week dev branch, and 2.16

That is because view distance is based on the center of the object. And the beams center is in its center, so far away.
Though max beam length is 1000m, so it really should be 500m.

You're writing about new command. But all I see is new eventhandler?

No repro on latest internal build.
No repro on latest profiling branch.
No repro on 2.14 stable.

https://feedback.bistudio.com/T177742 because Magazine is also a WeaponSlotItem

Arma 3 fix will be in 2.16 update.
DayZ Team has been informed. Thank you!

Maybe also a separate endpoint just for a mods version.
Many people will want to check simply "is this mod up to date", and fetching the whole description and stats for that everytime would be a waste.

scopeCurator is coming. If set to zero will disable in zeus

"don't show up in Zeus"
Mine do.

We would have some trouble testing this. Maybe you can help test it for us?
in Arma 3\Launcher there is a Utils.dll
Replace it with this one.

Figured something out.
The !Workshop folder is actually not needed. The Launcher has a fallback for when creating the links inside !Workshop folder would not work.
We know it has issues in Proton, but its actually not activating that fallback.
Next Arma update we will enable the fallback. !Workshop folder will never be created but the mods will be loaded directly from Steams content folder.

Ref https://feedback.bistudio.com/T178384

!Workshop folder seemed to be empty, with no shortcuts

I like that idea. But oof.

The RPT doesn't have enough info. We would need the minidump (.mdmp file), but according to log, none was written.
The crash is in your AMD video drivers, maybe updating them could help

"ErrorMessage: Include file userconfig\DVD\DVD.hpp not found."

No, not possible. Engine limitations

Delete the file it mentions, its corrupted.
You will loose your keybinds if you changed them from the defaults

The fix is available on Profiling branch. You can switch to it in the Steam game options under the Beta tab.

The fix is available on Profiling branch. You can switch to it in the Steam game options under the Beta tab.

Revision: 151264

Blocking a mod file does not cause the game to crash.
The crashes you are having, were already fixed on Profiling banch. You can switch to it in the steam beta options. The fix will also be in the next game update

You are loading some corrupted mod.
Maybe you recognize what this is:
"Nvme_Game" "fit_on_backpack_nnwinter_v8"

This bug is already fixed on Profiling branch. You can switch to that branch in Steam.
Also ref https://community.bistudio.com/wiki/Arma_3:_Steam_Branches

Your log files don't contain any crash.
The RPT logs just end, and there are no crash dumps.
Nothing I can do without that crash information

Just use the -mods= parameter.

That doesn't exist, you meant -mod.

Ist bekannt, ist auf Profiling branch schon gefixed.
Soweit ich weiß passiert das nur nach nem server disconnect.

The message already prints the group.
"%s: Cycle as first waypoint has no sense"
is the whole message, and the group gets inserted at the start.

You have multiple files with (1) in the name. None of these should exist.
Delete them all and then verify your game files in Steam.

UI/HUD changes, won't do.

Markers do not have an "Owner"
They have a Creator, which is stored ine the Marker name.

There is no RPT, and that folder not existing is also normal as this is the first time you're starting Arma.
See this https://community.bistudio.com/wiki/Arma_3:_Unusual_Process_Exit#0xC0000135_-_STATUS_DLL_NOT_FOUND

Its a UI thing..
Very interesting find, thank you!

Please don't re-create duplicated tickets.
Yes its missing some parts, but its still fundamentally the same thing.
You can post a comment on the old ticket, but not really needed as duplicate tickets are linked and will be seen when the ticket is processed.

Related to T151698

the AI-animated character ([this,"WATCH","FULL"] call BIS_fnc_ambientAnimCombat;) icon does not match the color of the faction.

Incorrect. It does match.

Next week dev branch

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