Public Beta — This Feedback Tracker is currently in public beta. For most issues, please visit feedback.bistudio.com
1
Issue Key
State
Access
Public
Project
Creator
Created
Apr 9, 2026
Views
10Attachments
No attachments
Experimental Version
If modded, list mods
No mods
Description
The signals values in AISoundHandling.c aren't being replicated on dedicated CLI servers to clients. The only thing that gets properly synced is ECommunicationType (i.e. whether is a REPORT_CONTACT or REPORT_MOVE etc), but values like TargetDistance (line 436) and DirectionAngle (line 467) do not get replicated, I suspect it's something to do with signalsManagerComponent:FindSignal() not returning the correct output (i.e. not finding a signal when on a dedicated server and returning -1 )†.
The result is that AI will always report contact as "Unknown man, 50m north" on dedicated servers, whereas on listen-servers (player hosted) they can report things like "enemy AT soldier, 200m south-west." Also, in reports like REPORT_MOVE the teamleader will say "One, move to grid 000 000" instead of setting the correct SoldierCalled value to say "Squad, move to grid ..."
Beyond that, SetSignal_GridValues has faulty logic resulting in only the last digit of the 6-digit-grid being saved, so AI units reporting movement >2500m will say "grid 000 008" or something like that, with only the last digit being properly evaluated.
† I have tried making a mod that changes the FindSignal function to use other functions like AddOrFindSignal and AddOrFindMPSignal function instead and it worked for the latter, though the replication was too delayed, and so when using GM to tell a team to move >2500m the grid said would be the one set previously and not the most recent one.
N.B. this has been an issue for a while even before 1.7 patch, however seeing this patch address the 'neznámý stan' issue, I thought there might be some focus on AI sound/comms handling. I couldn't find any previous reports on this either on the discord or the older feedback tracker. Let me know if I should duplicate this issue on the older tracker as well if this tracker is mostly aimed at issues of the 1.7 experimental build.
You are not signed in. Please sign in to see more details.
Issue Key
State
Access
Public
Project
Creator
Created
Apr 9, 2026
Views
10Attachments
No attachments