View Issue Details

IDProjectCategoryView StatusLast Update
0000206Falcon BMS Known BugsUnknownpublic2021-08-31 13:13
Reportersuhkoi69 Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformPCOSWindowsOS VersionWindows 10
Product VersionBMS 4.35 U2 
Summary0000206: weather issue : visibility changes after saving TE
DescriptionI noticed something strange about the fmap loading : if the fmap is loaded and saved directly from the TE mission (not from TE builder or editing), the visibility is correct
but if I decide to leave the mission and reload the same TE from Tactical engagement menu; the visibility will have changed

Steps To Reproducehere you can see the video I did
https://youtu.be/7-GKuCDodRM
TagsNo tags attached.
Theatre of OperationsKTO

Activities

suhkoi69

suhkoi69

2021-08-30 18:12

reporter  

21100.fmap (389,916 bytes)
transit2.iff (10,272 bytes)
transit2.ini (9,692 bytes)
transit2.tac (19,561 bytes)
transit2.twx (788 bytes)
transit2.fmap (389,916 bytes)
transit2.frc (938 bytes)
transit2.his (42 bytes)
suhkoi69

suhkoi69

2021-08-30 18:33

reporter   ~0000655

[update 1]
if the fmap is created from Weather commander -> it works fine
I guess the issue comes from FMAP generated with F4Wx; I tried to read and save from Weather commander -> visibility issue

probably something is changed when FMAP is saved from the "setup weather" in BMS...
suhkoi69

suhkoi69

2021-08-31 13:13

reporter   ~0000656

today, I tested in MP
Ric joined the MP TE and first, we noticed we didn't have the same weather visibility ( 7km for me vs 20km for Ric)
Once I load the FMAP ( the 21100.fmap I provided) , we didn't still have the same visibility ( 0 km vs 2 km ) - next step, I saved the TE and I reloaded this TE with normally the 21100.fmap

once again, we noticed the same issue: we didn't have the same weather visibility ; however, the values are exactly as previously ( 7km for the hoster and 20km )

we tested the case where we switched the host of the TE: same problem; however, the values are still the same for the host

we could also notice a little discrepancy of visibility between the hoster and logger when the F4wx FMAP is loaded ...so in my opinion, there is already something wrong about the fmap reading and perhaps this point is at the issue origin when the user decides to save: probably, the TE_NAME.fmap doesn't match the FMAP coming from F4Wx

Issue History

Date Modified Username Field Change
2021-08-30 18:12 suhkoi69 New Issue
2021-08-30 18:12 suhkoi69 File Added: 21100.fmap
2021-08-30 18:12 suhkoi69 File Added: transit2.iff
2021-08-30 18:12 suhkoi69 File Added: transit2.ini
2021-08-30 18:12 suhkoi69 File Added: transit2.tac
2021-08-30 18:12 suhkoi69 File Added: transit2.twx
2021-08-30 18:12 suhkoi69 File Added: transit2.fmap
2021-08-30 18:12 suhkoi69 File Added: transit2.frc
2021-08-30 18:12 suhkoi69 File Added: transit2.his
2021-08-30 18:33 suhkoi69 Note Added: 0000655
2021-08-31 13:13 suhkoi69 Note Added: 0000656