@suhkoi69 I will have to study this more and correlate the grib2 data with Meteoblue. Currently busy on other stuff so I will file an Issue to keep track of it. If you have the grib2 data for me than I will save these images and do some research as to why the data doesn’t match for cloud base. Other stuff seems ok.

@CriticalMass
Hello. I am seeing the same error in Mideast128 Theater as in your post and for the same reason (missing spaces before/after x in Primary flight). I checked VG discord but could not find your workaround. Can you please post the workaround or send a link to the discord entry or PM me?

Late edit: I figured out the workaround myself:

Enter scenario, Select pilot, save DTC. Call up Briefing, and click on Print button (upper right).

AltTab to the …\Falcon BMS 4.37\User\Briefings folder, and edit “briefing.txt” file using a text editor (I use TextPad) - Edit line 21:

Package Elements:[add a single Space here] x[add a single Space here] = Primary Flight

Then save briefing.txt

Return to BMS

RunEZBoards.bat and it should run properly.

Thanks in advance,
@Logic and @SpbGoro for info.
Regards,

@Tumbler31 said in [F4RADAR] Lightweight standalone radar application:

So depending on ground and airborne stations and Mk1 eyeball.

So if my F-16´s I am supporting are already within 30NM, have radar and visual ID of Mig 29… I should have that too I would guess?

So, actual it it what is is and not changeable, right?

I suspect that the cells with black color are over 9000ft

Unfortunately, BMS team isn’t maintaining those tools so not much we can do until the author replaies back to you.

Cheers

@suhkoi69 Even if we had the value, Tacview does not support it currently. I will add to our list to experiment with indicated altitude to see if we can support it in the future. Thanks for the suggestion.

@oakdesign
I don’t know if “Lightning” is a member of the BMS Dev Team but I especially hope that its library will be updated when BMS 4.38 is released. It offers a huge source of information on the structure of BMS in any case.

Thank you for clarifying the “starting point”, I understand much better now.
I really didn’t know that .tac contained different files. Glad to hear all this from you.

I appreciate that his code is in C#, because for me, C++ is a little more complex to understand.