BMS Other Fighters Mafia (BMSOFM) Journal
-
Thanks jayb. This profile currently is using Capt Zeens graphics but I am currently working on my own graphics (hope to finish soon) that will replace them. The touch screen I am using is 22". Its not big but not small either. Helios definitely allows a creator to make an interface however they want. The limits are really just your imagination and time to get it done. Helios is a good use for interfacing with aircraft that don’t have a full 3D pit or the switch mappings are not totally flushed out but there are callbacks for , like the F-18. I have plans to create a template card that pops up on the main monitor that calculates the turns in a case I landing based on reported BRC that you the user would select, kind of like dialing the CRS or HDG bug. I see it more of a training tool but could be useful.
Current feature set of this profile
1. All F-18 switches / dials that are mapped in 3D are mapped in the profile the same way its done in BMS.
2. Currently using linknets Kneeboard updater code that exists in the Ice 4.35 profile
3. Currently using the Charts from the Ice 4.35 profile (will update as some things are not relevant to the Hornet, like checklists)
4. Implemented the use of EZWatch (EZBoards) to generated a kneeboard of the BMS Briefing then pull it into the profile for use with the Kneeboard in the profile
5. Implements theater detection (taken from linknets Ice 4.35 profile) so that the charts that are displayed are for the theater you are flying in
6. created working EIFI gauge
7. Reworked the EHSI taken from Ice 4.35 profile and made it work and look like the one in the hornet
8. Created a callsign name plate for your flight (with the help of linknet)Currently I am struggling with the switchology and names. We all know the switches really control what would be an F-16 pit but some names on panels are Hornet specific. So do I go with renaming some of the switch labels so its easier to locate the switch of do I stay with Hornet labels?
-
So after looking at the 3D pit and the BMS F18 cockpit doc is clear that some buttons are mapped in 3D but not documented like the D/L on the UFC. Does anyone have an up to date list or do i have to go through the cockpit dat file to figure it out?
Sent from my iPhone using Tapatalk
-
So after looking at the 3D pit and the BMS F18 cockpit doc is clear that some buttons are mapped in 3D but not documented like the D/L on the UFC. Does anyone have an up to date list or do i have to go through the cockpit dat file to figure it out?
Sent from my iPhone using Tapatalk
Hi, Wheelchock.
Have you checked the new 'pit diagrams in the Fighters Manual (in my signature Mediafile)? It shows almost all of the changes we made in the “Mod 2” cockpit. Also, feel free to contact me.
To answer your earlier question about whether to rename switches… I can tell you with fair assurance that the BMS Hornet will always have Viper avionics. So, IMHO, putting Viper switch labels in the Bug/Rhino pit would be great.
BTW, thank you for your efforts with the Hornet! Would you like to join the Mafia?
PS: I pm’d you -
Good Day, All,
Brother Chuckles asked if I would take a look at the K’2012 F-14 and it’s austere cockpit. There a way to put the “Mod 2” Hornet 'pit in it, inspired by a 4.33-era thread by Crazyjap. But, I’m hoping as I learn more, to do more with the actual visualization of the cockpit. But, for now, the Tomcat is… functional.
For the last few days I’ve been looking at the F-35C. It had the same jfs/parking brake/landing light hotspot issue as the Bug, and they have been fixed. But, I took a look beyond that. I did the same "Mod 2 Hornet 'pit mod and it works in the Panther, too. I should have the Fighters Manual updated in a day or 2. However, the basic F-35 'pit looks really cool, but at least without MFDE, lacks stuff like engine gauges and HSI. I’m hoping, as I learn more, that I can do things like Wheelchock is describing above.
Also, I was reading https://www.airforcemag.com/lockheed-to-retrofit-f-35s-for-suppression-destruction-of-enemy-air-defenses-role/ and that got me to wondering if there was an interest in the BMS Panther? I know we won’t have AESA and the 5’th gen stuff, but is there interest in seeing just off far we could develop it in BMS? -
Thanks jayb. This profile currently is using Capt Zeens graphics but I am currently working on my own graphics (hope to finish soon) that will replace them. The touch screen I am using is 22". Its not big but not small either. Helios definitely allows a creator to make an interface however they want. The limits are really just your imagination and time to get it done. Helios is a good use for interfacing with aircraft that don’t have a full 3D pit or the switch mappings are not totally flushed out but there are callbacks for , like the F-18. I have plans to create a template card that pops up on the main monitor that calculates the turns in a case I landing based on reported BRC that you the user would select, kind of like dialing the CRS or HDG bug. I see it more of a training tool but could be useful.
Current feature set of this profile
1. All F-18 switches / dials that are mapped in 3D are mapped in the profile the same way its done in BMS.
2. Currently using linknets Kneeboard updater code that exists in the Ice 4.35 profile
3. Currently using the Charts from the Ice 4.35 profile (will update as some things are not relevant to the Hornet, like checklists)
4. Implemented the use of EZWatch (EZBoards) to generated a kneeboard of the BMS Briefing then pull it into the profile for use with the Kneeboard in the profile
5. Implements theater detection (taken from linknets Ice 4.35 profile) so that the charts that are displayed are for the theater you are flying in
6. created working EIFI gauge
7. Reworked the EHSI taken from Ice 4.35 profile and made it work and look like the one in the hornet
8. Created a callsign name plate for your flight (with the help of linknet)Currently I am struggling with the switchology and names. We all know the switches really control what would be an F-16 pit but some names on panels are Hornet specific. So do I go with renaming some of the switch labels so its easier to locate the switch of do I stay with Hornet labels?
Please post the profile when you finish!
-
Please post the profile when you finish!
Hi, Icer, I am very happy to report that Wheelchock and Smartaxe have both joined the Mafia. So, as things are developed they should be included in Fighters Manual updates.
Speaking of updates…. The Fighter Manual has been updated to include the following-
.
VII) Installing the Mod 2 Hornet cockpit in other jets.-with thanks to Crazyjap
Step 1-Go to 4.35>Data>Theater(if different from KTO)>art>CkptArt>your jet’s folder and find the value
for the wing model. For example, the F-14D is cockpitwingsmodel 3114; . Save that value
Step 2)Copy all the files in your jet’s folder to your desktop for safe keeping, then delete them from the folder
Step 3) Copy and paste all the files from the Mod 2 1799 folder in the Mafia Files (see VI) and paste them to
your jet’s folder.
Step 4) Go into your jet’s new 3dckpt.dat file and replace the wing model value with the one saved in Step -
Here’s a “two’fer” of updates for today….
Many thanks to Brother Smartaxe for solving the Hornet’s backup gauges/compass needles modeling problem.
Replace the 2713.dds in your Korea Objects folder with the one that is now in the Mafia Files
BTW: This also fixes any jet that has the 'pit mod described in the previous entry -
Hi, Icer, I am very happy to report that Wheelchock and Smartaxe have both joined the Mafia. So, as things are developed they should be included in Fighters Manual updates.
Excellent, things should start popping now!
-
Here’s a “two’fer” of updates for today….
Many thanks to Brother Smartaxe for solving the Hornet’s backup gauges/compass needles modeling problem.
Replace the 2713.dds in your Korea Objects folder with the one that is now in the Mafia Files
BTW: This also fixes any jet that has the 'pit mod described in the previous entryTHANK YOUUUUUUUU
-
THANK YOUUUUUUUU
Hi, Seb,
Glad it’s working for you.
All,
Today I’ve tested it in the Hornet, Rhino, the Tomcat and the F-35( both have the Mod 2 'pit in my install) in the K’2012 campaign. Also the Hornet in Balkans, and the regular KTO. So, whatever campaign you like, just put it in that theater’s Korea Object folder and you’re good to go. -
Good Day, All,
Brother Smartaxe is working on a project…Fixing the modeling where some jets wheels don’t visually turn. Let us know if you see any. -
Hi, Seb,
Glad it’s working for you.
All,
Today I’ve tested it in the Hornet, Rhino, the Tomcat and the F-35( both have the Mod 2 'pit in my install) in the K’2012 campaign. Also the Hornet in Balkans, and the regular KTO. So, whatever campaign you like, just put it in that theater’s Korea Object folder and you’re good to go.the bug is better everyday
-
-
Hello fellow Bug experts. I am coming closer to my releasing my Helios profile but I can’t seem to close the canopy with the 4.35 callbacks
AFCanopyInc
AFCanopyStop
AFCanopyDecI see the Fighter Manual says it uses AFCanopyOpen and AFCanopyClose but those were replaced I believe with the ones I listed.
Even worse is that all the stock Hornets in 4.35 still use AFCanopyToggle which was removed as a callback, but obviously the canopy closes with the click of the switch so it must still be lingering in the code for backwards compatibility.
Any ideas on this one?
-
Hello fellow Bug experts. I am coming closer to my releasing my Helios profile but I can’t seem to close the canopy with the 4.35 callbacks
AFCanopyInc
AFCanopyStop
AFCanopyDecI see the Fighter Manual says it uses AFCanopyOpen and AFCanopyClose but those were replaced I believe with the ones I listed.
Even worse is that all the stock Hornets in 4.35 still use AFCanopyToggle which was removed as a callback, but obviously the canopy closes with the click of the switch so it must still be lingering in the code for backwards compatibility.
Any ideas on this one?
Hi, Compadre. Sorry for the delay, I was out riding…
I just went into my active 3dbutton.dat and the canopy listings are in fact-
AFCanopyOpen -1.12040 -1.123762 -1.598873 20 322 1
AFCanopyClose -1.12040 -1.123762 -1.598873 20 322 2.
Which is interesting as the 4.35 BMS_Full ( which is the one I use for AL, BTW) key callbacks are-
AFCanopyInc 115 0 0x10 4 0 0 1 “LEFT WALL: CANOPY - Open”
AFCanopyStop 115 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: CANOPY - Stop”
AFCanopyDec 115 0 0x11 4 0 0 1 “LEFT WALL: CANOPY - Close”
AFCanopyLockToggle 322 0 0x1F 4 0 0 1 “LEFT WALL: SPIDER - Toggle Open/Close”
AFCanopyLock 322 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: SPIDER - Lock”
AFCanopyUnlock 322 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: SPIDER - Unlock”
So, you’re right and I’m glad my canopy works! Why don’t you try putting these into your keyfile, and let us know what happens -
I recommend to use either the excel key file editor or the full callback text file to cross check callbacks. The Full key file doesn’t include all available callbacks.
Gesendet von meinem SM-G930F mit Tapatalk
-
I recommend to use either the excel key file editor or the full callback text file to cross check callbacks. The Full key file doesn’t include all available callbacks.
Gesendet von meinem SM-G930F mit Tapatalk
Thx, Oak,
I’ll have to play with my Libre Office, apparently, to get the Editor working. But, I did not see my-
AFCanopyOpen
AFCanopyClose
on the master callbacks list.
So, I don’t know help Wheelchock(#213), and my minor mystery remains. I suppose it logical that somewhere in the code is CanopyOpen/Close and Inc/Dec? I’m hoping maybe whatever keyfile he’s using has a callback error. -
Ok I have just done a bit of testing with and without the Project Bug Mods in place. the only thing that allows the Hornet canopy to open and close (in both cases) via a keyboard click is the AFCanopyUnlock and AFCanopyLock callbacks. The entries you put in the 3dbuttons.dat file are just for clicking a button in 3D pit that fires a callback. I thought it had something to do with what callbacks were accepted but clearly the 3dbuttons.dat file is just a way to interface the 3D pit with BMS.
-
Ok I have just done a bit of testing with and without the Project Bug Mods in place. the only thing that allows the Hornet canopy to open and close (in both cases) via a keyboard click is the AFCanopyUnlock and AFCanopyLock callbacks. The entries you put in the 3dbuttons.dat file are just for clicking a button in 3D pit that fires a callback. I thought it had something to do with what callbacks were accepted but clearly the 3dbuttons.dat file is just a way to interface the 3D pit with BMS.
HHHmmm- I’ve been thinking about your issue. In 4.35 the in the Viper the canopy won’t open without being unlocked, right? So, since our BMS Bug is a Viper “off shoot”, maybe what you’re seeing is normal behavior, and my profile’s open/close are unintended workarounds. If you’re still having problems, I can experiment by removing my open/close and set mine up exactly as the Viper, and see what happens.
And/or, I looked in the 4.34 BMS-Full keyfile and found-
AFCanopyToggle 322 0 0X2E 2 0 0 1 “LEFT WALL: CANOPY - Toggle Open/Close”
AFCanopyOpen 322 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: CANOPY - Open”
AFCanopyClose 322 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: CANOPY - Close”
If in fact these callbacks still work, that would explain why my canopy still works, and without the locking/unlocking steps.
Update: Just for the sake of “Hornetizing” our BMS Bug, the F-18 NATOPS says-
“2.15.1.1.1 Internal Canopy Switch. The internal canopy switch has three positions: OPEN, CLOSE
and HOLD.
OPEN Raises canopy to maximum position. If selected when canopy is locked, the canopy
unlocks, then moves 1.5 inches aft before rising. With WOW, the OPEN position is
solenoid held until the maximum up position is reached, after which it is spring
loaded to the HOLD position. The solenoid can be overridden at any time by placing the switch to HOLD. With weight off wheels, the switch must be held in the
OPEN position to open the canopy.
Objects/Grimes light placed in the area near the canopy
switch could inadvertently shift causing actuation of the
canopy switch airborne resulting in loss of canopy.
HOLD Stops the canopy at any point during the open or close cycle.
CLOSE Lowers canopy. If held after canopy reaches canopy sill, canopy moves forward 1.5
inches and then locks. Locked condition indicated by MASTER CAUTION light
and CANOPY display going out. CLOSE position is spring loaded to the HOLD
position.”
The main point being the F-18 doesn’t have a “spider” and a separate lock/unlock function. But, putting the 4.35 callbacks could be problematic if the new canopy controls and tied to locking, like the parking brake was tied to antiskid. -
These callbacks are not suppose to exist in 4.35 but I suppose they may be hanging around and will be removed in versions to come
AFCanopyToggle 322 0 0X2E 2 0 0 1 “LEFT WALL: CANOPY - Toggle Open/Close”
AFCanopyOpen 322 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: CANOPY - Open”
AFCanopyClose 322 0 0XFFFFFFFF 0 0 0 1 “LEFT WALL: CANOPY - Close”Using AFCanopyLock and AFCanopyUnlock works just fine for the Hornet. So I suppose using Lock and Unlock makes sense but not sure why they made it different than the Viper open and close for the canopy.