Let's try to recap the changes you might encounter converting to OF/AF whatever to BMS - speaking of homebuilt cockpit:
Bear with me, it's been years I haven't flown OF and sometime I may forget new stuff, so for the moment, let me declare this post WIP.
I'll update this with correction, addition in the coming days
1. The structure of the shared memory has not quite changed to assure that previous third party applications remains compatible.
2. Old unused shared bits have been renamed and re used as new functionalites. (The list is explained in the document below)
The new (renamed) functionnalities are:
EQUIP HOT caution light. Failure to use airsource will overheat the avionics & shut the FCR off... amongst other things.
OBOGS system
FLCS ABDC branches implemented but considered as a single unit and not 4 different ones
FLCS bit implemented with RUN and FAIL light. The FLCS bit switch should be a two position magnetic switch
DBU Warning light
3. Internal Display extraction.BMS can externalize it's own displays: MFDS, RWR, HUD, DED, PFD.
BMS must run in windows mode and that is not possible to use over the network.
Each window can be resized and can be displayed with or without border (included the main BMS windows)
To have F4 run in full screen with windows mode, just unselect the borders from the main screen in the display extraction applet and set BMS to run at native display resolution in the graphic control menu of the UI.
MFDE still should work (but not yet to extract the MFDs if I recall correctly, MFDE needed an update for that to work again, and I lost track of the updates there so I may be wrong.
I personnaly use MFDE to extract all instruments (AOA, VVI, EHSI, ADI, Mach, Altitude & TTD) so both ways work along fine.
4. LOTS of new full states and toggles callbacksSee file below for details.
Your biggest problem will be the key file.
The two default key file coming with the BMS install do not (if I remember right) have all the latest callbacks implemented. Especially for pitbuilders.
So you will have to track them down and add them all to your own keyfile.
It is unfortunately clear that none of the default key file will suit the needs of pitbuilders. But we know that and we can make our own (after all we build pits, that's much harder than to create a key file) The document below explains how to do it.
Many of us pitbuilders use our own key file. I created mine on the initial work of Jody and spread it amongst a few of you already. It's still available at the end of this post and you will also find a list of ALL BMS 4.32 callbacks. The ones in red are not to be used, the ones in green are new ones. The list is sorted panel by panel, so that should be useful to this crowd.
Final comment, for those lazy ones of you, my own key file is also included in that package. that's the one I use nowadays in my pit and is features all newest BMS4.0 callbacks. That being said, lots of toggles are left out and views and comms callbacks are kept to a minimum.
Of course this RD-pit.key file can me modified heavily according to your tastes.
5. Fully DX capable stick files. two layers DX possible, etc etc
6. More analogue axis supportIt is now MUCH MUCH better to implement knobs with regular pots instead of rotaries using keystrokes. The response is much more fluid and in some aspects such as the HUD brightness, quite irremplaceable IMHO
The following controls can be mapped to pots
COMM1, COMM2, Threat and Sidewinder, Intercom Volume knob. Please note, all volume pots should be logarithmic
HUD and HMCS brightness
YAW, PITCH & ROLL Manual trims
Some needs ON/OFF buttons at the beginning of the course (CCW) that one is programmed with the ON/OFF callback. the relevant pots are HUD brightness, HMCS brightness; COMM1 & COMM2
When using pots for those controls, with NO ON/OFF button, the pots will implement their current position in the game. that means that if you quit the game with an Offset yawtrim pot, the yaw trim will still be offset on the next mission: PREFLIGHT ramp checks gents !!
7. Throttle cutoff codeNo need for the idle detent anymore. Use the real cutoff point on your pits. Works much better than this stupid keystroke. I think this was already part of OF.
Here's a copy of a BMS article for pitbuilders:
http://www.candyparty.com/ST/Download/Checklists/BMS/Document/bms_cockpitbuilders.pdfHere's the callback spreadsheet, cockpitbuilder keyfile and documenation and my own stick file for the Cougar.
http://www.candyparty.com/ST/Download/Checklists/BMS/Document/F4_BMS4_RD.zip