View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000016Falcon BMS Known BugsGeneralpublic2020-12-31 09:232021-03-05 22:01
ReporterIronman3 Assigned Tomav-jp  
PriorityimmediateSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformPCOSWindowsOS VersionWindows 10
Product VersionBMS 4.35 
Target VersionBMS 4.35 U1Fixed in VersionBMS 4.35 U1 
Summary0000016: THREAT WARNING RECEIVE FROM SHIPS WHILE MP
DescriptionWhile flying multiplayer against ships we noticed that only host could receive a threat warning in his RWR. All other clients were "naked" from the ships.

We flew the same mission with a lot of aircrafts just to be sure that is not a receiver problem. We also tried a variety of ships and the result was the same.

Note that every client was hitted by the ships(without warning) and every client was able to lock and see visually the ships. The only problem was the threat warning.
Steps To Reproduce1)Go at TE and create a mission with one or more type ships.

2)Create at least a pair of aircrafts(other team than the ships in order for them to be able to hit you), and save the mission.

3)Fly the mission with another client
Additional InformationDuring the mission we were carrying HARMs too in order to see if we could obtain any symbol at any table at HAS mode.
We took some shots too but all of them(from the clients) were unsuccessful.

We run the missions with different hosts too but that made no difference.
TagsNo tags attached.
Theatre of OperationsKTO

Activities

mav-jp

mav-jp

2020-12-31 09:37

manager   ~0000025

Last edited: 2020-12-31 09:37

 what is a "threat warning" ?

please be mor especific
Ironman3

Ironman3

2020-12-31 09:38

reporter   ~0000026

A symbol in the RWR.
mav-jp

mav-jp

2020-12-31 17:28

manager   ~0000029

Last edited: 2020-12-31 17:28

 Check fix next release

note that the same bug happens if a SAM has been deaggregated before a client join in mP

this is therefore a very serious bug

Good catch that allowed me to have a reliable repro case since by chance , taskforces are always deagged no matter what :)
Blu3wolf

Blu3wolf

2021-03-04 00:20

manager   ~0000332

@Ironman3 could you confirm if you are still seeing this issue in U1? We can close it if its all sorted.
Blu3wolf

Blu3wolf

2021-03-05 22:01

manager   ~0000351

Closed by pm on forum. Thanks for reporting.

Issue History

Date Modified Username Field Change
2020-12-31 09:23 Ironman3 New Issue
2020-12-31 09:37 mav-jp Note Added: 0000025
2020-12-31 09:37 mav-jp Note Edited: 0000025
2020-12-31 09:38 Ironman3 Note Added: 0000026
2020-12-31 09:47 administrator Severity feature => minor
2020-12-31 17:28 mav-jp Note Added: 0000029
2020-12-31 17:28 mav-jp Note Edited: 0000029
2020-12-31 17:28 mav-jp Note Edited: 0000029
2020-12-31 18:34 Bad Boy Assigned To => Bad Boy
2020-12-31 18:34 Bad Boy Status new => assigned
2020-12-31 18:36 Bad Boy Status assigned => resolved
2020-12-31 18:38 Bad Boy Assigned To Bad Boy => mav-jp
2020-12-31 18:38 Bad Boy Priority normal => immediate
2020-12-31 18:38 Bad Boy Resolution open => fixed
2020-12-31 18:38 Bad Boy Target Version => BMS 4.35 U1
2021-02-22 08:30 Blu3wolf Fixed in Version => BMS 4.35 U1
2021-03-04 00:20 Blu3wolf Note Added: 0000332
2021-03-05 22:01 Blu3wolf Status resolved => closed
2021-03-05 22:01 Blu3wolf Note Added: 0000351