RM-51 and RM-70 of the CSLA CDLC seem to not work with this EH. The EH doesn't seem to fire. Only these two vehicles from the CDLC seem affected. I tested vanilla, GM, CSLA, RF/WS artillery units, and they all work except these two.

Adding some stuff from Discord #dev_rc_branch channel:

@BIS_fnc_KK thanks for this!

Having a native vanilla garrison module for 3den would be very useful. It could support the area scaling widget too. IMO it should be able to:

Yes, would be really useful to have area widget support for these modules -- i was going to create a ticket for the minefield before i found this.

Issue is no longer present, please close this ticket.

Given that this happens in vanilla arma buildings too... might be something that can be fixed more widely. Assuming BI cooperates...

Same issue with the M113, and to a lesser extent the Fuchs. Vanilla vehicles do show a similar behaviour, but the difference is that they have a tighter turn radius which makes it more controllable. Note that boats seem to handle very differently to amphibious vehicles.

Can confirm that this doesn't happen when slotting a Virtual Spectator slot from the lobby. @Wulf

point number 3 has been resolved (either 1.82 or 1.84, i don't remember). The rest I don't know, probably fixed by now /shrug

Authored by reyhard, fixed by reyhard 👌 😄

In T124664#1704168, @Krycek wrote:

So it seems this was assigned since May 2017 but I don't see any fix for this. Still won't lock on with laser designator to this date.

Another example: https://streamable.com/afwpn

Still seems to happen post 1.82, although I've had at least one mission where the markers did NOT disappear for me, but they DID for another player.

Does it hit the ground or just detonate early?

I'm assuming it's fixed on an internal build, but otherwise this is clearly missing sounds. Compare vs the CUP SPG-9, which should also be a BI-made asset if i'm not wrong. https://youtu.be/KoYQwqZ9KhM

Thanks, I hope you manage to isolate it. For us it seems to be pretty consistent - at least on the dedicated server. Haven't tried while self-hosting. Will try testing it from a spectator slot during our sessions and see what happens in that case.

Markers disappear at around 2:30. The freeze after I die is because of me alt tabbing and switching TeamSpeak channels.
https://youtu.be/Zmk7n7WIqFw?t=141

Yup, those ones. Will create a video tomorrow hopefully and put it up. Sorry about the late reply, didn't see this.

Allegedly fixed on dev branch today

BTW more resources:

So...looks like they've been doing *something* with it:

Well, it seems this is intended:

Fixed for ghosthawk on dev (v1.77), not sure about the rest

Fixed: Ghosthawk crew spawned in the wrong order in Eden Editor

Fixed as of 1.76

Potentially fixed with 1.76.142942. I can't repro with the F3 template anymore, although I'm testing a different system now, with the latest Win 10 feature update (Version 10.0.15063). Waiting for more people to confirm.

Still an issue with 1.76, seemed to have been caused by the Chinese localisation support hotfix.

Another thing i didn't add - Nikko removed all init code from the placed curator modules, i.e. no units were added to zeus. Still crashed.

Discussed with @Dwarden over PM

I have a duplicate ticket: https://feedback.bistudio.com/T123850

Repro mission:

Yeah i think you're right, if i turn off datalink from the emitter then the symbol goes away after a few seconds (although it should go away instantly, as it does when the radar is turned off).

Yes, can confirm, have observed this behaviour too.

Wipeout does not have active radar anymore, only "passive" radar, i.e. can detect other radars active in the area. It has a visual and IR sensor, and its weapons use IR lock. The target object must be hot (i.e. have its engines on) for successful lock. they've improved locking behaviour in 1.72, btw.

Still seems to be an issue with 1.72 hotfix, both local MP and DS. Can't change slots.

I thought Oukej said it would only be 8km? To be clear, I don't mind it being 10, it's just a mismatch between the display and the observed detection range. Can't actually lock so it's not that big a deal.

Come to think of it, could be related to the Shikra, since I had a crash with it last week too...