BMS Other Fighters Mafia (BMSOFM) Journal
-
Good Day, Soldano and Icer. I find myself wondering if this label issue can be “fixed”, or more accurately “worked around” by a method like what what we did with the hotspot issue. As I written elsewhere, I don’t have the Dev access or the programming skills to really solve these issues. That’s why I’ve been asking for the file locations for the secondary gauges and kneeboards, be it dds or dat issues.
Meanwhile, Oakdesign wrote in another thread-:"So apart of the F-16 models only the Mirage Models seem to have the new kneepads. All other flyable Models such as the F-18 still use the previous 1988.dds & 8019.dds Textures.From the technical manual
For now, the old single page DDS textures 1988.dds & 8019.dds are still available for compatibility reasons, e.g.
they are used by 3rd party pilot models. Please note that this can change in the future.
so I’m not a 3DDB guy but from that part it seems to me that having the new keyboards on other aircraft is not only a thing of dat file editing but requires changes to the Pilotmodel as well
I replaced
line 51 in 1799/3dckpit.dat
from
cockpitlegsmodel 2045;
to
cockpitlegsmodel 2015;
And have the kneepads picking up the new dds files.
I could flip through the pages by usig the callbacks I have bound to my HOTAS. So for mouseclicks you might will have to add the correct locations to 3dbuttons.dat thse are ones that are in the F-16 blocks//KneePads
SimLeftKneePadInc -1.039195 0.336720 -1.225200 40 115 1 w
SimLeftKneePadDec -1.039195 0.336720 -1.225200 40 115 2 w
SimLeftKneePadInc -0.690350 0.400980 -1.288300 130 115 1 w
SimLeftKneePadDec -0.690350 0.400980 -1.288300 130 115 2 w
SimRightKneePadInc -0.930800 -0.644880 -1.253330 40 115 1 w
SimRightKneePadDec -0.930800 -0.644880 -1.253330 40 115 2 w
SimRightKneePadInc -0.657620 -0.412880 -1.322300 130 115 1 w
SimRightKneePadDec -0.657620 -0.412880 -1.322300 130 115 2 w "
So, hopefully this will sort out the kneeboard issue, even if you have to cycle them via keyboard and/or HOTAS. "
More on this later… -
Refering to post 159, I just had an interesting first test.
After doing Oakdesign’s switch to 2015, I went in’sim and the kneeboards did work via both the HOTAS and keyboard settings I had entered via AL(no hotspots). Oak, I’m wondering if you had the same issues I did, though…
Firstly, the pilot’s body looked about 9 ft tall (best way to describe it) … Secondly, the jet caught fire then blew up mid-checklist, and engine readings stayed normal. Perhaps coincidental…?
Anyway, I then looked into the 4.34 and 4.35 3dckpit.dat’s. Both 4.34 and.35 Hornets had 2405. Is that what you meant, Oak? I also saw that the 2015 value is what’s in what in the 4.34 and 35 Viper CM-50(which is what I use as a reference).
So, we’re definitely making progress on the kneeboards, we just need to do some tweaking.
Find myself wondering if there’s a way to “tell” WDP to look for for the 2405 leg model , hopefully om addition to 2015?
Or, we know that in 4.34 WDP looked at 2 dds’s, which were updated with each mission saved. In 4.35, in the Hornet, WDP is looking at airport list for left and Korea IFR map for right. Could we “tell” WDP to look for whatever dds’s are the current l/r data cards? I know we wouldn’t get the cool 4.35 multiple board layout, but at least they’d work. -
Update: Kneeboard problem solved…
go to 4.35>data>art>ckptart>1799>3dckpit and find cockpitlegmodel. Change the 2405 to 1913, and save. The hotspots don’t work, so I used AL to set both keyboard and HOTAS commands for testing, and both work. -
That kneeboards parent 1913 is used for Mirages family , don’t know how well is going to “sit” in Bugs pit… you’ll see.
You could copy kneeboard hotspots from relevant Mirage pit 3dbuttons, which uses 1913 parent. … to Bugs 3dbuttons, should work OK…
but if they don’t try to use hotspots debug and tweak them position.Cheers
-
That kneeboards parent 1913 is used for Mirages family , don’t know how well is going to “sit” in Bugs pit… you’ll see.
You could copy kneeboard hotspots from relevant Mirage pit 3dbuttons, which uses 1913 parent. … to Bugs 3dbuttons, should work OK…
but if they don’t try to use hotspots debug and tweak them position.Cheers
Hi, W_F.
Your, and Oakdesigns’s, Mirage tip was spot on. The Viper leg model was too big for the Bug 'pit, but 1913 leg model is almost perfect. Plus, it gives the hotspot data possibility you mention. This is very helpful as I haven’t figured out how to obtain switch positional data. I can set up to see where hotspots are, but not the other data. So, right now I can work with known switch locations
More later on your Mirage hotspot idea… -
Update: Kneeboard problem solved…
go to 4.35>data>art>ckptart>1799>3dckpit and find cockpitlegmodel. Change the 2405 to 1913, and save. .Update: With thanks White_Fang and Oakdesign, here is the Hornet kneeboard fix.
Step 1)as above
Step 2) 4.35>data>art>ckptart>1799> 3dbutton.dat and add
//KneePads
SimRightKneePadInc -0.775250 -0.511368 -1.811727 100 115 1 w
SimRightKneePadDec -0.775250 -0.511368 -1.811727 100 115 2 w
SimLeftKneePadInc -0.714940 0.481883 -1.731376 100 115 1 w
SimLeftKneePadDec -0.714940 0.481883 -1.731376 100 115 2 wThis gives a hotspot in the center of each kneeboard, and they do cycle in’pit.
This also gives possible options for other jets. If you put either 2015(from the Viper) or 1913 for leg model into your 3dckpit (whichever leg model look’s best for you). Then. put in either the Viper’s or Mirage’s hotspot data. -
Good Day, All,
Attached is the BMS Fighters Manual for your consideration. Critique is welcome -
I want to know if this proyect includes improvements for EF-18. I fly the EF-18 in Falcon BMS because I’m from Spain and I have found many mistakes in the cockpit.
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
-
I want to know if this proyect includes improvements for EF-18. I fly the EF-18 in Falcon BMS because I’m from Spain and I have found many mistakes in the cockpit.
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
Hi, Dardo,
The short answer to your question is -yes. What specific issues are you having? In Section One I tried to generalize things that could help even jets the Mafia hasn’t looked at, in terms of hotspots and such. And, thinking about your specific jet, I suspect you could just "plug in " our Hornet 1799 3dbutton.dat. Just save your existing file, and if it doesn’t work ,no harm done, you can put the original back. The file is attached
All,
One thing that’s not been mentioned in this thread is that Project Bug is for people who don’t know about LODEditor and such , by such people(at least in my case ). Anyone with such knowledge and the time and desire would be really welcome! -
Good Day, All,
Attached is the BMS Fighters Manual for your consideration. Critique is welcomeThanks!!!
-
Good Day, All,
The “news of the day” is that the Manual has been submitted to the Devs.
I find myself wondering which way to go next. So, I thought I’d ask the Group for “requests”. My top 3 personal choices at the moment are Rhino,and/or Harrier, and/or A-10. -
My request would be more improvements of the Rhino. An improvement of the F-14 would also be desired.
-
EF-18 has problems with the TGP because looks as masking all time. It is necessary edit the TGP coordinates.
EF-18 IFF doesn’t work in 4.35. It can be fixed as follow:
#–---------------------------------------------------IFF
#-----------------------------------------------------
avionicsIFFTransponderSettings 63
avionicsIFFInterrogatorSettings 15
avionicsIFFBackupM1M3 1Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
-
IMHO the Rhino (super hornet)
-
My request would be more improvements of the Rhino. An improvement of the F-14 would also be desired.
Chuckles and jayb, Rhino it is.
Chuckles, your statement about the F-14got me to thinking about the F-35 in K’12. I love that the Panther is in there, but the 'pit is pretty rough, hence the following question… Back in the 4.33 days for awhile I was flying with a Viper pit in the Hornet, purely because of cockpit functionality. IF it could be done , what does the Group think about putting a Hornet cockpit in the Tomcat( perhaps an upgraded Horent -F 'pit) and Horent C 'pit in the Panther?
Dardo, good job on getting the IFF working. When I get a chance I’ll take s look at the EF TGP. Just to confirm, you have the config TGP set to 2, for external TGP?
All , in another thread it was asked what the best way to implement the cockpit data. I found it a lot easier to simply replace all the 3dbutton data .Last night I got around to setting up Balkans, plus I had previously done the following with Korea 2012,so it has been tested… I moved the entire 4.35…ckptart>1799 folder to my Desktop for safe keeping and then copy/pasted the entire “Mod 2” 1799 from Korea. It works fine. So, once you get one upgraded 1799, it’s easy to move from theater to theater.
And, BTW, if anyone would like to pm me an email address, I’d be happy to send you the 1799. UPDATE: Now in the Medafile link in my signature. -
Chuckles and jayb, Rhino it is.
Chuckles, your statement about the F-14got me to thinking about the F-35 in K’12. I love that the Panther is in there, but the 'pit is pretty rough, hence the following question… Back in the 4.33 days for awhile I was flying with a Viper pit in the Hornet, purely because of cockpit functionality. IF it could be done , what does the Group think about putting a Hornet cockpit in the Tomcat( perhaps an upgraded Horent -F 'pit) and Horent C 'pit in the Panther?
Dardo, good job on getting the IFF working. When I get a chance I’ll take s look at the EF TGP. Just to confirm, you have the config TGP set to 2, for external TGP?
All , in another thread it was asked what the best way to implement the cockpit data. I found it a lot easier to simply replace all the 3dbutton data .Last night I got around to setting up Balkans, plus I had previously done the following with Korea 2012,so it has been tested… I moved the entire 4.35…ckptart>1799 folder to my Desktop for safe keeping and then copy/pasted the entire “Mod 2” 1799 from Korea. It works fine. So, once you get one upgraded 1799, it’s easy to move from theater to theater.
And, BTW, if anyone would like to pm me an email address, I’d be happy to send you the 1799.Hi drtbkj, thank you for your attention. Currently, EF-18 has type 2 TGP (external), but it is bad positioned and it is masked. If you change it and put TGP as internal and you don’t select TGP in your loadout, you can use it without problems.
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
-
Hi drtbkj, … If you change it and put TGP as internal and you don’t select TGP in your loadout, you can use it without problems.
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
Hi, Dardo,
I’m going to try this trick. Sounds interesting -
Drtbjk:
All of my theatres, Korea 2012, Kuriles, Somalia, Panama, have MyKinge’s partially finished F-14 pit included. I think what you did with the F/A-18 pit would be work great for the F-14. It would give the pit the final functionality it needs to be fully Usable in BMS.
As for the Rhino, the F/A-18E/F use an LCD display for DED. I am very interested how you are going to emulate such equipment?
-
Hi, Dardo,
I’m going to try this trick. Sounds interestingMasked TGP was also a failure of BMS 4.34. It was fixed with an update repositioning the coordinates of the TGP.
Another problem of the EF-18 is that it doesn’t have HMS in BMS 4.35 now. In RL, spanish EF-18s have the Scorpion Helmet as HMS as you can check in this video.Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
-
Here’s an update of what I’ve done tonight…
First, I discovered how to tell which numbered ckpitart folder is for your jet. The 3dbutton files aren’t all labeled, but the 3dckpit files are .
So,
1798= F-18B
1799=F-18C
1890=F-18A
1409=F-18D
1958=F-18E
1959=F-18F
2017=F-18AU
1083=F-18+ ACRS
864= F-15E
Now, Chuckles and Dardo, let’s move on to your jets…
F-18E- my cockpit is now set to Mod 2. -Step 1-in the 1958 folder 3dckpit file, change the cockpitlegmodel value to 1913, and Step2- replace the 3dbutton.dat with our Mod 2 file. Tested in 'pit. Chuckles, I’m unclear what you mean about the DED. The Rhino uses the same model as the Bug, and both work
EF-18- I added a squadron so I could get in 'pit. It has the same 'pit as the Bug except the Fuel and engine panels are not electronic. So, our procedure would be the same except I would recommend putting the Fuel knob values from the original EF 3dbutton, and deleting the ones from the Mod 2,as the fuel knob IS a knob and not the Bug’s "push button.
Actually, without trial and error, I would recommend using the Alternate Launcher to set a switch and/or keyboard for Engine feed off/norm. I used mine on my HOTAS and did start the EF. In terms of hotspot, you may try
SimIncFuelSwitch -2.22376 0.547978 -1.756868 20 115 1
SimDecFuelSwitch -2.22376 0.547978 -1.756868 20 115 2
Not tested.
Dardo, I tested your internal TGP setting trick in the Bug and it didn’t work, still masked. When I get a chance I’ll test it in the EF. The fact that it was also an issue in 4.34 gives me pause. That means it’s an LOD=type issue, as you’re suggesting. I’ll also look into HMS and see if I can find anything.
F-14D-Chuckles,I added a squadron of those, too, and tried to get in 'pit. I say tried as on 2 occasions I CTD’d as soon as I spawned in 'pit. Also, looking in both the 4.34 and .35 CkptArt, the Tomcat doesn’t have 3dbutton files! Does the Tomcat even have hotspots? For that matter, can you even get in’pit?So, the Turkey is still very much a WIP. I’m seriously considering using the 14D as a testbed for the “put a Hornet 'pit in there” concept,