Ice’s Falcon BMS Profile Updated for BMS 4.37
-
Mr. Ice - This is FREAKING AWESOME !!! Words can not fully communicate how much I love this…totally solves all the “issues” I had with Falcon BMS and makes flying a zillion times more intuitive and fantastic. Much closer to flying the actual jet. If you are ever in Missouri USA I’ll buy you a steak dinner ! THANK YOU !
F-Bear
-
-
@FBear My rhetorical question for you is, Why didn’t you know about this before?!?! This has been around for years!!
-
@linknet I am having the problem again with the kneeboards updating. It looks like it is that same problem as last time where the KneeBoardsUpdate.exe is hardcoded to the 4.36 directory. Is it easy to provide a quick update to that exe? If not as a workaround I can just run an older version of WDP that is pointed to 4.36 to update the kneeboards so Helios can pull it from the 4.36 directory.
-
@zeek said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@linknet I am having the problem again with the kneeboards updating. It looks like it is that same problem as last time where the KneeBoardsUpdate.exe is hardcoded to the 4.36 directory. Is it easy to provide a quick update to that exe? If not as a workaround I can just run an older version of WDP that is pointed to 4.36 to update the kneeboards so Helios can pull it from the 4.36 directory.
In the latest 4.36-05 version of the profile the kneeboard updater path isn’t hard coded, the profile passes the most recent BMS path as a parameter to the updater. I’ve just tested the 4.36-05 version of the profile with BMS Falcon 4.37 and the kneeboard update is working fine. If you’re running this latest version of the profile and it still isn’t working just let me know.
-
-
@linknet - thanks, I see it now in the revision history. Guess I should have updated. Will do it with the 4.36 directory for now until the next version is released and then update.
-
@linknet - just getting back into BMS with the 4.37 release after some time away, updated my simple profile to point to 4.37, adjusted monitors, and all is error free. Issue is the MFDs do not display on my 2 Lilliput monitors. The other gauges I have on there are fine (Fuel Flow, RPM, Fuel, Compass, VVI) but no MFDs. For a quick fix I figured set them as hidden, then enable RTT, and RTT auto start/stop. Went into RTTClient.ini, set the positions where I wanted the MFDs, all good. Start my profile, I see RTT start but no video. I go and look at the RTTClient.ini and now it shows as "Created by Helios, both MFDs are set to “0”, and no coordinates, with a note not to edit it…
I can, once I disable RTT in the Helios profile, simply run RRClient64.exe using my original (I saved it) RTTClient.ini and it works perfectly, would rather have Helios run the show. What did I miss/mess up?
-
@Icer I’m sure you must have set this but just asking to make sure:
Add “set g_bExportRTTTextures 1” to the “Falcon BMS User.cfg” file
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@Icer I’m sure you must have set this but just asking to make sure:
Add “set g_bExportRTTTextures 1” to the “Falcon BMS User.cfg” file
Yes, and again RTT running on it’s own using my edited RTTClient.ini displays the MFDs fine, it’s just that if I set the profile to use it, it will start/stop RTT as expected, but it does not display anything and the RTTClient.ini Helios creates does not have the MFDs enabled…
-
@Icer So neither the Helios MFDs nor the Helios created RTTs display on the Liiliput monitors. Have you got the same scale factor set for these and your main display?
-
@linknet In Display Properties yes, 100%. Normally when I would run the Profile (with BMS off) a black box would appear on each Lilliput, now no box… RTT (standalone) I get the gold framed box with X’s…
-
@Icer I’m afraid I haven’t any more suggestions apart from the basic ones I already put forward. Perhaps @Wheelchock might be able to help since he was the one who created most of those sections of Helios.
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@Icer I’m afraid I haven’t any more suggestions apart from the basic ones I already put forward. Perhaps @Wheelchock might be able to help since he was the one who created most of those sections of Helios.
Would be great as I would rather just run Helios by itself again. It’s odd that Helios creates an RTTClient.ini that has no settings… I may try and drop the RTT MFDs in the Editor into the spots, maybe that is the step i’m missing… but at some point I would rather not run RTT at all, as I di in 4.34 and up.
EDIT: User Error as far as the RTT display goes. You need to use the “Falcon RTT Viewports\Falcon RTT MFDLEFT ONTOP and Falcon RTT MFDRIGHT ONTOP” and place them on your monitor. Been quite a while, forgot how it works… Starts RTT , displays properly, stops when you exit.
-
@linknet : is it possible to get the briefing onto the knee pads in-profile without WDP?
-
@BVT_9 Try EZBoards - it replaces the 7982.dds file so that you can view the briefing on the cockpit kneeboards.
I could possibly look into having the profile do that, it already generates the briefing kneeboards so would just need to convert to dds.
-
Quick question - will this profile work on a non-touch screen? I just want to try it out visually with an old 22" screen I have before investing
-
@wazza69 Works with a mouse just fine.
-
@linknet Hi how do I link bms to the new key file? I dont understand how to do it and the manual does not explain it. No buttons are working in the profile. Thanks
-
@maverick007 The “Setup Guide” for the profile explains it. I’m hoping to release a new version of the profile for BMS 4.37 with more relevant instructions. Just waiting for the next Helios release.
-
Hi. After 2 days of working I finally made all the buttuns react. The problem was in the alternate launcher. When I start via the standard lanucher and then in the settings i point to the Ices key file then everything works like butter.
I did not have success with forcing this via the alternate launcher as it keeps forcing BMS to use BMS auto key file. Maybe renabe the ices key file to auto key file as well???
There are some mistakes in the guide in names of some of the exe components in helios process manager. I had to correct the names…Otherwise it works even in 4.37. Great job, mate!