Thanks for this well written update. I really appreciate the work put into BMS. Have a safe and blessed holiday.

I was just wondering and dreaming about the possibility of having the three line crew airmen during a ramp start. Could you imagine how neat it would be to wait for hand signals to pull the EPU pin, chocks, and to cycle the control surfaces and Airbrakes. I realize that this could hit Frame rates while it is running, but maybe once leaving the parking spot, the airmen would disappear and hopefully the FR would increase.
FSDreamTeam has done this with the PMDG737 program, and it adds to the immersion of that sim.
Thanks to ALL THE BMS TEAM!

@maxwaldorf
Thank You Sir.
I re-read the tutorial page i referred to in my last post. Would help to read it carefully-DUH!
The updates install is done. the last steps referred to a new install with all the updates at the same time.

@airtex2019

Thanks again Airtex. SALUTE!

TO MAX and QUASI,
SUCCESS with the torrent install. The only additional step i had to do is pay for the WINRAR use. My demo version expired.
Torrent was fast.
Thanks again

@lcriscola

I just flew a successful camp mission with the MAV-L model. I now see how to get the laser to fire with the auto-lase set to 40sec on the DED. I am using aTM cougar with the 2 stage trigger.
at IP , set the target WP and go AG mode. TMS up to lock target area. Rt/MFD has TGP on and active. LT/MFD switch to SMS and power up the Mavs. Then switch to WPN page. Verify WPN code matches Laser DED code. TGP as SOI. verify my target by zooming in as needed. Trig-1 to manually laser range target, while monitoring the WPN page. When in range, in keyhole, and see a solid box on the WPN page, then pickle the Mav AND pressing the trig-2 detent is now firing the laser and I see the flashing L in the HUD. Turn away and deploy CH/FL as needed,keeping the laser and TGP in view. Now I am getting hits.
Hope to repeat this on future sorties.

@Icer
Thanks Ice, I will check it out.

@jayb
Thank You Jayb and Quasi_Steller.
Quasi…you were correct. When I initially installed 4.36, I must have copied the setup.zip to the Falcon BMS Setup folder, my error! What I should have done was just run the setup.zip from my Download file.

I fixed my problem by running the FalconBMS 4.36.1_inc.exe again. But this time setting the path to C:\FalconBMS 4.36 Setup\Falcon BMS 4.36 Setup.

This saved me alot of time. THANKS AGAIN!

@Fish44
I checked that post out. I had no problems with 4.36 when it came out. The issue with unable to unlock the laser code, that came up in the U1. It still does not work in U3. I just keep using the 1688 code.

But thanks for your response.

@MaxWaldorf
Hello MaxWaldorf.

I just read this post. I tried changing the code on the WPN page in a camp mission in vers U3 with the AGM65-L.
Still does not work.
For me not a big issue, I just use the 1688 default code.
Fly safe!

I was just wondering and dreaming about the possibility of having the three line crew airmen during a ramp start. Could you imagine how neat it would be to wait for hand signals to pull the EPU pin, chocks, and to cycle the control surfaces and Airbrakes. I realize that this could hit Frame rates while it is running, but maybe once leaving the parking spot, the airmen would disappear and hopefully the FR would increase.
FSDreamTeam has done this with the PMDG737 program, and it adds to the immersion of that sim.
Thanks to ALL THE BMS TEAM!

@Yassy
Thank You Yassy for all you have done with this profile.
I just started using the TR5, and your profile is much better than the Smoothen profile that comes with the software.
Huffer out

@OPPOTATO
I have the same issue. When you move the GPI over the L, I also cannot get the U to appear with a TMS-up. This was not a problem with the 4.36 base install, but showed up with the U1 update.
If I desire to use Mav-L for a mission, I have been just leaving the default 1688 code when checking the Loadout page, and leave 1688 on the DED page in the viper.

@Jackal
Thanks Jackal.
I just tested the AAR TE mission #4-D in current U1 update.
With the fully loaded F16 with weapons, I was able to contact the tanker by tuning Comm1 to 348.62
With the F16 with no weapons, manually tune 294.72 works with the tanker.

This will help other pilots if they see this issue.

Huffer out

@jayb
Thanks Jayb. Glad I am not the only one.

Has anyone seen this happen. I wanted to practice AAR last night and was unable to contact the tanker on UHF 13. Tried two times with both F16 flights in this AAR TE. Same issue.
When I go to the briefing page before entering the cockpit, I notice that the Tanker frequency is not there, like it usually should be.
Not sure what changed or how to add this tanker frequency.

Yesterday I had to do a complete reinstall of BMS 4.36 and U1. Something went wrong with the program, but now all seems to be working OK. I just still cant practice AAR.

I dont see anyone with this issue in previous posts.

Thanks for any thoughts.

PROBLEM SOLVED!
I forgot a important step since I did a complete reinstall.
The FalconBMS.cfg needed a change: setg_ExportRTTTextures = 1
Sorry to bother anyone.
Now the BMS program is running correctly, with the cubesim displays.

How or why a file became corrupted in BMS is up to the PC Gods!

Good night all!

Has anyone seen this problem? For the last 6 weeks I have been using BMS 4.36 successfully with two CubeSim dispalys for the RT and LT MFD.
Today something changed with the BMS program. My Mfds would show a blank screen when viewd in 3d cockpit and same with the cubesims. If i clicked the OSB on the screen that coresponded with the "blank’, I could see the data come back.
If I start a new mission in a campaign, and get to the point were I load the DTE on the Rt MFD, once loaded the same BLANK screens would pop up.
Something apparently became corrupted in the BMS files.
I uninstalled the entire BMS 4.36 from the Setup.exe.
I reinstalled Falcon BMS with the U1 update.
I started BMS to check if the MFDs were working correctly in the 3D cockpit, and they are back to normal.
Exit BMS.
I then opened the RTT client in the Tools folder and set up the parameters for the two CubeSim displays just like I did before.
I then ran the RTTclient.exe, and I get the large orange X on the two displays. Sounds like everything is working, however when I am running BMS, the Cubesim displays are just black, but the MFDs in the 3Dcockpit are looking normal. For some reason the data is not going to the displays.
I double checked my RTTclient.ini and it should be working.
I do have the two lines set for: USE_MFDLEFT = 1
USE_MFDRIGHT = 1

Any thoughts out there on this situation?
Thanks for any advice.