Possible TFAR compatibility issue

[michail-nikolaev]

I got some reports regarding issues in case of TFAR + AGM. Peoples hears other peoples like they are underwater, probably while they are unconsious. It may be caused by negative height level of unconsious players.
Could you please provide some information about the "unconsious" implementation details?

[michail-nikolaev]

Or maybe here nothing related to unconsious, but just to AGM....

[NickvdLee]

If the underwater issue plays in spectator mode, one of the latest updates
to the F3 framework made it so spectators wouldn't have a virtual unit at
[0,0,0] but at [0,0,5]. This fixed the underwater issue (which happened on
maps with water at the zero coordinates). This might be an issue for other
spectator systems as well.
On Mar 3, 2015 12:22 AM, "Michail Nikolaev" [email protected]
wrote:

Or maybe here nothing related to unconsious, but just to AGM....

—
Reply to this email directly or view it on GitHub
#2148 (comment).

[nicolasbadano]

@michail-nikolaev, I can't imagine this being AGM's fault. This is the only thing we touch in TFAR when falling unconscious:
https://github.com/KoffeinFlummi/AGM/blob/master/AGM_Medical/functions/fn_knockOut.sqf#L38-L40

Besides:

• nothing has changed on our end in months regarding unconsciousness
• I've personally haven't seen or heard reports of this on my community, while using both mods together over a hundred hours.
• AGM does not provide any spectator mode.

It could be an issue with F3 though; I have very little experience with it.

BTW: thank you very much for the hard work on TFAR; it's an excellent mod.

[jonpas]

Same findings as esteldunedain, no issues here and we play with TFAR+AGM all the time.

[michail-nikolaev]

Hm... Thanks for help. Will try to get more details

[JamesTheClarke]

We experienced this as well, but only during PvP, using one-life rule and F3 Framework Spectator mode. As @cptnnick said, this was solved for us with the latest update to F3 Framework on the 20th of February. Ever since updating we never ran into this issue again. Never experienced it outside of F3 spectator mode.