ACE3 Version: 3.3.2 Stable
Mods:
@CBA_A3@acePlaced ACE3 Modules:
GVAR(filterUnits) = 3Description:
Steps to reproduce:
ace_spectator_fnc_setSpectator;
[player, true] call ace_spectator_fnc_stageSpectator
(do not call it through the debug console; it will crash the game)
Where did the issue occur?
Everywhere
Can confirm I experience this issue from time to time.
:+1: Good report, will investigate
Not entirely sure what's causing this one. Looked through the code a few times and it checks out as far as I can see.
Might have to push fixing it back to the next milestone.
Just to update, can definitely reproduce this, still not sure what is causing it.
Just to clarify, is this why if a unit dies, you still have 4 people listed in a fireteam but it just repeats one name, for example:
Pre-death:
A1 ->
John
Thomas
Oliver
Dave
Post Oliver's death:
A1 ->
John
Thomas
Dave
Dave
Hit escape to force reload spec UI seems to clear it.
It's most likely related, in fact, your post is a little more specific with regards to reproduction and might help me to track down the cause
Fixed in #3147
Only partially fixed! :smile:
Since I'm quite busy at the moment and don't have much development time I'll write down my current thoughts on this issue in case anybody else wants to take a look:
- 1 like the similar lines 340 and 341. Probably worth investigating that.[grp,0,grp2,1,grp3,2,...])unitList (list of all current spectatable units) to remove any unnecessary iteration and simplify the code.2 notes for using the repro mission provided by @voiperr:
class ACE_Settings {
class ace_spectator_filterUnits {
typeName = "SCALAR";
value = 3;
};
};
ace_spectator_fnc_setSpectator must be called with empty array [], otherwise _this will carry over from spawn due to scope and be executed like 0 call ace_spectator_fnc_setSpectator, causing RPT error (since 1.54, it will still continue executing though)Duplicates should be fixed by #3781 :hammer:
Quick test with 4 people shows https://github.com/acemod/ACE3/pull/3781 working without any side effects, will run it on Saturday with 40+ and see how it handles that.
This issue appears to be fixed and the changes have been merged to master, closing! :tada:
Worked fine with larger numbers, forgot to update this :banana: