Thanks for investigating, we are going to take closer look before 2.02

will be hotfixed, it is fixed in internal already

The event handler should fire on any message getting added to the local chat. Which messages display in local chat but not fire EH?

with the release of 2.00 assignedTarget seems completely broken

It has not been touched

Can you remind me how do you get to mission selection screen on dedicated? What dedicated server set up?

@_connor You will have to experiment to find out, not sure myself

@_connor updated documentation: https://community.bistudio.com/wiki/Arma_3:_Event_Handlers/addMissionEventHandler#HandleChatMessage

could always disable 3d person in server options

Is this intentional?

we will look at it later

fixed in 146763

fixed in internal

This is scripted and the names of the parts are stored in config in multiStructureParts[] property

https://feedback.bistudio.com/T120317 related

Added in 146751

Nope, can't reproduce on internal. Could you retest it on the next DEV please (soon)?

@Cyprus Could you provide repro mission, I cannot reproduce the bug in internal.

Fix is on the way, fingers crossed it might make it to 2.00

Thanks!

Ok when next DEV is released (soon) please try on that, if it is still happening I will have a look

I'll try that but there's 5 of us that play same maps and I'm the only one having this problem

It needs to be determined what causes the issue for YOU, so please disable the mods first and report back.

Could you please provide copy paste repro?

Is this still relevant on the latest DEV?

Have you tried in on DEV? I cannot reproduce this on internal DEV

Bugs are priority, if there is a bug I need to look at it. So can you provide a repro for the bug?

Profiling branch?

no what I need is something I can exec in debug console that creates the rope and another command line that shows the bug. but if you say no biggie, then I guess I will leave it

@Parcival Switch to dev branch and see if that crashes

try disabling all mods and then adding them one by one to see which mod causes crash

Could you upload crash dump without mods?

repro please

try creating new soldier with default control scheme

"enable" was enabled for a short time then reverted because it caused unspecified problems with handling of controls. ctrlEnable called from onLoad EH is safe however. A bit inconvinient but at this stage any deep engine changes are not possible. Won't fix.

"enable" was enabled for a short time then reverted because it caused unspecified problems with handling of controls. ctrlEnable called from onLoad EH is safe however. A bit inconvinient but at this stage any deep engine changes are not possible. Won't fix.

Can you try this on the latest dev branch? It should be better balanced if not please report back

lineIntersectsSurfaces uses engine method if it is a bug then this is how it has been since the dawn of times. Why don't you test other doors on other maps to know for sure?

Still broken?

it has "instant" param now

I‘be sent your ticket to our QA let’s see if they can reproduce it

Probably not happening, lineIntersectSurfaces uses engine method that doesn't have provision for RoadWay LOD, this would require deep changes so most likely won't happen at this stage.

Actually even red section depends on angle

i have both green sections intersect when door is open but not red section

foregroundColor and activeColor are non existent properties for CT_BUTTON, but backgroundColor is and it is a bug that it cannot be set with script command

Could you tell me why would you need this and how it can be useful in general? there are only a few color getters for controls, mostly color setters, so I'd like to know how useful this could be and possible uses that could benefit everyone.

picture button is special case, so yes this is a bug

Obviously I went into 3rd person. Are you using mods? What Arma 3 version you have. Is this MP, SP, or both?

cannot reproduce

this can be prevented with adding items into arsenalRestrictedItems[] mission config param

Well maybe it would have been better if this was implemented from the start with higher priority, but this cannot be changed now, so won't fix