search

HeliosVirtualCockpit / Helios

Helios Distribution
https://github.com/HeliosVirtualCockpit/Helios/wiki
GNU General Public License v3.0
201 stars 33 forks source link

Missing data in RWR under Falcon BMS #404

Closed ertiyu closed 3 years ago

ertiyu commented 3 years ago

On 4.35 the RWR present in the "Falcon Simulator" tab does not display all the contacts. Here is a video.

https://youtu.be/XeNNS2gB8q0

Todd1215 commented 3 years ago

is this just in 4.35 or does it also miss contacts in 4.34?

This Falcon specific gauge seems pointless now that you can get the RWR extracted straight from BMS as a texture. If I fix this all I'm going to do is rip out the code and replace it with the RWR texture for backwards compatibility with older profiles.

ertiyu commented 3 years ago

Indeed I did not use it before, but since the extractions do not work correctly in 4.35 it is very practical.

Todd1215 commented 3 years ago

Can you use the BMS SharedMemoryRecorder by viper tools location herehttps://github.com/lightningviper/lightningstools/tree/master/releases/End%20User%20Applications/Falcon%20BMS%20Shared%20Memory%20Recorder/for%20Falcon%20BMS%204.34

Using the tool above record a session that duplicates that scenario you showed in the video and post the shared memory recording here so I can use it to troubleshoot

ertiyu commented 3 years ago

Here is a recording of the shared memory,

save.zip

I also added two screenshots from the software that came with Falcon BMS. One capture was made with version 4.35 and the other with version 4.34. Both give the same values.

Data 4_35 Data 4_34

It's easy to do the test if you want to just run a "Rolling Fire" campaign

Todd1215 commented 3 years ago

Due to BMS updates since the gauge was created (pre BMS version 4.32 I believe there have been RWR symbols added since then (will have to doublecheck that). The gauge only models the RWR in the block 50/52. Keeping this gauge up to date with BMS code is probably not what we want to be spending our time on. Helios already captures the RWR texture from BMS. So in my opinion no need to reinvent the wheel here.

Todd1215 commented 3 years ago

I just checked the RadarSymbol enum against what is in lightningviper tools ThreatSymbols enum and they are the same, so unless lightningviper tools is missing symbols then we have a complete list.

ertiyu commented 3 years ago

MFDE understands all the symbols, see the screenshot MFDE 4_35