BMS Other Fighters Mafia (BMSOFM) Journal
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj … Yo brother.
Been checking those SuperBug AFM and they’re not quite working out for me.
I couldn’t T/O till 300!!! kts from paved runway, “glued to ground” effect.So, I reverted to bms org afm but leaving (bit corrected, edited) dat only .
Then it kinda works , … but speed is limited… with clean aircraft can’t break hardly past M1.05 … in shallow dive , afterburner… so… yeah. … with F18c, bms ver, did M1.15 , level flight 25kft , clean config., ext cnt 480 tank.Also in current F18E model , nw launch bar does not move (up/dn) , it is working, per test , but not animated as in F18C.
(but , caveat, sometimes is not working… but that was special case… T/O from one airport , some A2G , some AAR … then land on “Roosevelt” , quick refuel , tried to takeoff again … no-go , bar just didn’t want to hookup, … some deep BMS bug I guess)
Do you have some updated files for SuperBug?
Hi, White, here are the test results, for your dining and dancing pleasure. I made a TE in the OFMKTO theater with takeoff from Roosevelt . F-18E with 4AAM and 480 centerline drop. Climbed at 25k, then doing a 5 deq. dive in 'burner, then 2 landings( fuel was 14,700) and takeoffs from ground base…
The results were- Our launch bar not only worked, but is animated( I thought we had fixed that) . Hook up to the catapult, no issues. Finally, in the dive I maxed out at 1.16( see below). Ground landing performance felt good. I did half flaps on first TO, full on the second. Take off trim was set each time. It did feel perhaps a little sticky but I was able to rotate at 200 kt. We’ll look into that. Brother Eddie , however, tested in Nordic and couldn’t rotate to > 300 kts.
Conclusion: Compadre, whatever theater you’re flying in does not have the current files. I have put the current dats in the Mafia Files https://www.mediafire.com/folder/aj94t9ldo5ikz/1958(f18e.+Install+Pack+ver+7.6.21). Try them, but there are model changes involved here, too. Try acdatas and let us know what you think.
Regarding the 480 drop tank-I did not test with the 330 tank, but I did notice in loadout that the 480 limits both g-limit and max. mach( to M 1.2) . Per loadout, the 330 has M 1.6 That makes sense to me, as the 480 is meant as a ferry tank. Try the 330 and see what that does. -
@drtbkj Ha… you might be to something there., not moving launch-bar could be theater model “problem”.
This was all in Balkans.
–nope, tested it, same model F18E in kto and balkans, maybe you use different model in that “ofmkto” - btw link not working for theaterWhen I start mission from carrier, all is fine , even not animated Lbar hookup’s.
But as I’ve said, that one case when it didn’t want to hookup, that was a special case.
I started mission from different airport , landed on Roosevelt, quick-refuel, tried to T/O again , then it just didn’t want to hookup anymore, on any cat1-4.
That looks to me something with the “ato? code” ,… not dat’s or afm so …You could be damn right for centerline tank also… hehe. 330 vs 480… you know how it is … every drop of fuel … these days LOL
Cheers will report!! out.
edited
– Figured it out. It was the F-18E.dat… “maxlaunchbarangle” …
I used OLD dats in your post , few above… those are from 4.35 and edited by Ronin? … They dont play nicely with 4.36.1 … so You might want to remove them .Those dats in mediafire, seems ok, current., albeit, engine set to 0 ??? makes no sense (but is also set for F-18C by BMS default, so it seems that 404/414 engines are not quite good in database, need rework)
… typeAC should be 10 , that is F-18E ,… but again, who knows what’s missing
typeAC = 9 is F18C … see in acdataBut yeah, without FMM (flight model manager) , dev tool , it is all hacking the shite of
Cheers
-nope… F18E launch bar not animated even in original KTO … with/out your dat/afm … seems F18E/F model thingy (F18C Lbar working “everywhere”)
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj Ha… you might be to something there., not moving launch-bar could be theater model “problem”.
This was all in Balkans.
–nope, tested it, same model F18E in kto and balkans, maybe you use different model in that “ofmkto” - btw link not working for theaterWhen I start mission from carrier, all is fine , even not animated Lbar hookup’s.
But as I’ve said, that one case when it didn’t want to hookup, that was a special case.
I started mission from different airport , landed on Roosevelt, quick-refuel, tried to T/O again , then it just didn’t want to hookup anymore, on any cat1-4.
That looks to me something with the “ato? code” ,… not dat’s or afm so …You could be damn right for centerline tank also… hehe. 330 vs 480… you know how it is … every drop of fuel … these days LOL
Cheers will report!! out.
edited
– Figured it out. It was the F-18E.dat… “maxlaunchbarangle” …
I used OLD dats in your post , few above… those are from 4.35 and edited by Ronin? … They dont play nicely with 4.36.1 … so You might want to remove them .Those dats in mediafire, seems ok, current., albeit, engine set to 0 ??? makes no sense (but is also set for F-18C by BMS default, so it seems that 404/414 engines are not quite good in database, need rework)
… typeAC should be 10 , that is F-18E ,… but again, who knows what’s missing
typeAC = 9 is F18C … see in acdataBut yeah, without FMM (flight model manager) , dev tool , it is all hacking the shite of
Cheers
-nope… F18E launch bar not animated even in original KTO … with/out your dat/afm … seems F18E/F model thingy (F18C Lbar working “everywhere”)
Hi, White. First , let me say that we know the Rhino is a WIP. Right now we’re just trying to make it the most flyable/fun with file tweaks.
Secondly, I’m not surprised that stock KTO and Balkans don’t have the latest models and such. Some of this was developed either as 4.36 came out, or too late to include it. And, or course, our BMS Dev’s and the Balkans Gang have the choice whether to use our Stuff or not. Let me just say that we have tremendous respect for both groups, and they know we are happy to share with them. Also,there are possible ways to add the Rhino ,or other jet model, to Balkans. Heck, even an “OFMBalkans” is possible.
Thirdly, we plan to put OFMKTO 1.4 today or tomorrow, so I’ll fix the link then.
Now, to your specifics… If you look at the post here from 19 days ago we did some F-18E testing. It was kind of a toss up between engine type 0 and 4. In the days after that post we did some more testing and found engine type 0 felt better with the flat spin issue. Ac type 9 is confirmed ,though. The files in OFM, and what I copied to the “1958” folder in the Files, are the current Files. It has ac=9, engine=0. If you want to try engine=4, let us know what you think, but don’t forget the spin testing .
To be honest, Compadre, I zapped those files into “1958” for your sake for testing. Our focus at the moment is completing OFMKTO 1.4 , then housekeeping in the Mafia Files. There may in fact be even more changes. Brother Eddie at this moment is testing vapor data for the Rhinos/Growler , which will be in 1.4 , as well. -
@drtbkj
That’s Great news m8!!! Hardly wait for 1.4. Thanks for all the fish!!I was never aware that there was an updated model, so there my confusion… you’re saying that it works … I can’t see it nowhere
Thanks for files, btw, yes , I’ve experienced flat spins before, especially after hard-pullup + paddle (fcs over-gain) … but also… I’ve almost done a perfect “Cobra” with F18E. (I’ll revert to saying plane type, rather then nickname, avoid confusion… bug/superbug)
But after speed depletion it always ended in a flat stall and spin to the right, (Top Gun style)…, but easy fix there, brakes out , nose down … piece of cake … just need some altitude , eh
I am checking engine types… we’ll see … but I don’t think that Team removed/set F18C engine to =0 , without reason… that’s what I meant saying engtype =6,7,8 are NOT used anymore… since BMS 4.33. or so… was not without reason, eh?
- Engine types 1-5 are NOT related to F18’s anyhow… those are F4’s, F15’s, F16’s … etc.
What you might take look at are:
6 = GE404-400
7 = GE404-402
8 = GE414-400
With you latest afm/dat F18E looks more flyable…but then again , these are more reverted to stock ones … that are NOT using advfm (aeropt AdvancedTEF , aeropt LefIncludedinCL ) … so back to square one … almost stock model with stm
…but again … is flyable.Ok… I’ll play around some more … but until OFMKTO hardly to see any improvement “polishing” the stock model, eh… right.
Thanks again m8, and the Mafia of course . see you later then in 1.4!!
Cheers
- Engine types 1-5 are NOT related to F18’s anyhow… those are F4’s, F15’s, F16’s … etc.
-
@white_fang s you may have seen, OFMKTO is out , now. Enjoy!.
I’m going to test engine 8. in the F18E, and you tell us what you find. Since this IS a WIP, people like you testing is very valuableAll, Here’s a general update: With OFMKTO 1.4 out we’re thinking we have time for other projects. Today we are testing the Fifth Generation Cockpit. This is where we want to make the stock F-22 pit fully functional and use it in the F-35,etc. The thing we’re working on is “freeing” the center and bottom osb’s to do what we want them to. Things like IFF controls, etc. In Metalhead’s pit made way-back-when, those osb’s mirror what the left and right mfd’s do.
Thanks to Brother Musurca’s Hotspot Visualizer, we can see which osb’s match what is in the 3dbutt.da files.
Finally, I’ve done some “housekeeping” in the Mediafire Mafia Files. The new f-18E acdata/afm are now in the 4.35-36 acdata folder as well as “1958”. And, if you want to experiment with the Fifth Gen Pit, there are now in the 4.35-36 Cockpit folder, there are subfolders for both the F-35C with 5G pit,and the Hornet pit
Update: Success! Brother Eddie figured out the OSB issue. We now have a ramp-start-capable 5Gen pit. There is still work to do, but now we can make progress. Thanks again to Metalhead for giving BMS this pit and Brother Musurca for the Visualizer. -
Good Day, All. With OFMKTO 1.4 out we have time to do other things, and we made a lot of progress yesterday with the F-35 and the 5G Pit. When working with a cockpit the baseline goal is ramp starting the jet without the keyboard. We’re a lot closer to that today then yesterday. We, or rather Brother Eddie, figured out the OSB issue with the center MFD’s. That gives us something to work with with things like IIF functionality, which is fixed. There is more to do. TCN functionality is something to be figured out. We did some work with the gunpod and that seemed to cause an issue with AG master mode. We think we’ve made progress with that.
-
@drtbkj What is giving you hard time with TCN ?
IF “Tacan backup” … just use old style type backup in dat (=0) , not new mfd one , since you already have old-style tacan backup in center mfd …- only, AA/TR are reversed on mfd mnemonics (display) , right click on AA/TR button will always activate TR mode , even it displays AA-tacan on mfd
Or something other ?
Cheers
btw, Thanks for update… will “power-up” this week!!
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj What is giving you hard time with TCN ?
IF “Tacan backup” … just use old style type backup in dat (=0) , not new mfd one , since you already have old-style tacan backup in center mfd …- only, AA/TR are reversed on mfd mnemonics (display) , right click on AA/TR button will always activate TR mode , even it displays AA-tacan on mfd
Or something other ?
Cheers
btw, Thanks for update… will “power-up” this week!!
Hi, White (or is it Fang ) Anyway, TCN was not so much a problem, it was more about getting used to that pit’s version of the HSI.
We did some more testing today, working out those pesky bugs. We had a problem incorporating the gun pod. It caused problems going into AG Mode-fixed. We got the flaps and takeoff trim to work. We did some flight model work, though there’s more to do. Carrier landing speed is too high. And, we are currently trying to get the autothrottle to work. -
@drtbkj hhhmmm… ATC worked for me in those late “special” dat/afm you provided. - in both cases , cruise and aoa mode. - probably hasATC=1 in dat and NasaModel=2 in afm.
Yes. carrier trap speed has always been too great … ~160-170kts … much too great… 150kts approaching stall. - even with Full-flaps.
But that is all - “unfinished model” … so, need to fix/hack this thing.
Hack “fix” for relative-flaps speed around 120 … works for AI … but not for “player”.That model need to be worked from bottom - up. - but, you know it,.
btw… mostly “Fang” … sometimes white , sometimes red …
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj hhhmmm… ATC worked for me in those late “special” dat/afm you provided. - in both cases , cruise and aoa mode. - probably hasATC=1 in dat and NasaModel=2 in afm.
Yes. carrier trap speed has always been too great … ~160-170kts … much too great… 150kts approaching stall. - even with Full-flaps.
But that is all - “unfinished model” … so, need to fix/hack this thing.
Hack “fix” for relative-flaps speed around 120 … works for AI … but not for “player”.That model need to be worked from bottom - up. - but, you know it,.
btw… mostly “Fang” … sometimes white , sometimes red …
Hi, Fang( definately much cooler ) Fang and Wolf, good team. Anyway, HHmm, yourself. My F-35C atc isn’t working even with has atc-1 and NASA-2. Doing more testing today. Are you perhaps talking about the F-18E?
I’m seeing the same thing in F-35C landing speed. Big testing item today. We had seen the same issue previously in the F-18E, and maybe you’re still seeing it?. Another test item .
As for the TCN- I noticed yesterday that the number display(upper left corner) which at first I thought was the heading selected is in fact a TCN distance reading . So, yes, the TCN is functional, and not the issue. What is is a lack of “indicators” The viper has the switches to tell if you’re in ATT hold,ALT hold , HDG,STEER, and ATT. On the Hornet that’s all on the HSI. It’s the same with a NAV/NAV ILS/TCN/TCN ILS indication. The current 5G has the left autopilot switch on the left console, and it works. The right “switch” is on the UFC, but it only gives off and ALT hold.(possible bad callback?) . That is an issue is this pit, as several callbacks have changes since it was built Also, without a MFDE display extraction(which I have) there doesn’t seem to be any way to see which mode you’re in, besides seeing the change on the HSI display… Anyway, If there’s another way to get these indicators-cool. I’m just suggesting the Hornet -style HSI ( if doable) because that’s all built in already. We’re working on that, too -
Good Day, All. Here’s a bit of an update…
Since my last post we’ve been doing more F-35 flight testing then cockpit testing, with some positive results. We have it flying fairly well, although it’s carrier approach speed is about 30 knots too high. WIP
Fang, this will interest you. We also did some F-18E testing, and got an unpleasant surprise. It’s back to flat spinning-badly. Somehow the testing/setup we did in 4.36.0 did not carry over to U1. The jet still flies fine in U0. So, we’re working on that, too.
The 35C flight testing did give a lot of opportunity for acclimation to the 5G cockpit. It no longer feels weird to fly with it. It still has it’s limitations, largely the aforementioned “indicator” and lack of fuel/fuel flow gauges issue. But, it can be flown and fought without the keyboard, albeit with some help from HOTAS and MFDE extraction. Our goal remains to make it as good as we can for those who do not have such tools. The next step will be installing current callback hotspots on things like parking brake ,landing lights, etc. . -
@drtbkj
Hi, I was always talking about F18E … saw F35 only on pics. - but from what you describe, same problem - standard (stock) model… need tunnel testing/ graphs, etc. - I don’t know how do that. - maybe devs Good Will one day…And you really need FMM - to makes things right - join beta BMS, talk to devs.
For F18E autopilot, … sounds like bad callbacks, check buttons file… in original (BMS) pit callbacks are ok…, 2 autopilot buttons are on the HSI , and both of them are “cycle” (mode/func) buttons.
I don’t remember actually using them , since I have auto-pilot mode button on hotas , and function (ATT/ALT) I have on SHIFT+A … I somewhat have ZERO mouse cockpit usage , only on ramp-start - and all those essential callbacks works. only ones missing : ANTI-ICE , IFF (dont know where is it) - since I know the keyboard , no problem.
But those are a bit trivial (easy fix) , major problem is afm. - lot of try’n’error…
Cheers
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj
Hi, I was always talking about F18E … saw F35 only on pics. - but from what you describe, same problem - standard (stock) model… need tunnel testing/ graphs, etc. - I don’t know how do that. - maybe devs Good Will one day…And you really need FMM - to makes things right - join beta BMS, talk to devs.
For F18E autopilot, … sounds like bad callbacks, check buttons file… in original (BMS) pit callbacks are ok…, 2 autopilot buttons are on the HSI , and both of them are “cycle” (mode/func) buttons.
I don’t remember actually using them , since I have auto-pilot mode button on hotas , and function (ATT/ALT) I have on SHIFT+A … I somewhat have ZERO mouse cockpit usage , only on ramp-start - and all those essential callbacks works. only ones missing : ANTI-ICE , IFF (dont know where is it) - since I know the keyboard , no problem.
But those are a bit trivial (easy fix) , major problem is afm. - lot of try’n’error…
Cheers
Hi, Fang. I have lots of news…
Today we plan to release an OFMKTO 1.4 Hotfix today . It has a set of acdatas for the F-18D-G, and the F-35. We have the F-18EFG not spinning and landing at a reasonable speed. The F-35 is better but stills lands a little hot on the carrier. However, even at my stick and rudder skill level I did many successful passes.
So, they are working better, but you are right. This process of FM management is not complete. We’ll keep working on that.
Assuming I can get it to work, the Hotfix will also have a WIP set of corrected hotspots for the 5G Pit. Again, you are right that systems’ control can be done with keyboard . Or, I personally can fly and fight The F-35 without keyboard, thanks to my HOTAS and MFDE extraction. But, not all BMS member’s have those capabilities. Our goal is to use the keyboard as little as possible.UPDATE: The OFMKTO 1.4 Hotfix is out. https://www.mediafire.com/file/zrxurgqg9ug15uk/OFMKTO_hotfix_update_1.41.exe/file
-
Good day, All. Today’s update is about Theaters, and their development, at least from the Mafia standpoint. Exclusive of OFMKTO, we don’t really consider ourselves as Theater Developers. However, we are happy to help those that do. In the process of this, we get feedback with bugs and issues. Most are like " (I) noticed the avionics panel switches not right too. I don’t know if I should even mention these things, I am not bitching or complaining, just letting you guys know .If I’m coming across as a jerk, not meant to be .Just my little bit to help but if its more of a pain, please let me know. Love these theaters !" We welcome such feedback, so we can make it better.
Some , however, seem to wonder why something is released that is “unfinished”. Their F-5 doesn’t take off, or whatever the issue is. Well, the reason for that is what this post is about.
As you are probably aware, Theaters, file-wise, are separate entities. That’s a lot of files and a lot of data that has to be replicated and debugged . Over and over. And when you are helping with multiple theaters, it takes a LOT of time.
Our main goal, when we help with a Theater, is literally to help keep them alive as the BMS updates come and go. We catch the bugs we can , and fix the rest later, balanced against real life time restraints. If we took the time to totally debug every jet in every theater, all these Theaters you enjoy would not be here. At least, not as quickly as they get released.
So, “keep the cards and letters coming”, when you find a bug. We just want you to understand the how this all works. -
Hi, there. Here’s a bonus update for today.
Work continues on the Fifth Gen Pit. Today we added the functionality to the OSB’s around the center MFD, added kneeboards, fixed the APU(would turn on but not off), landing lights, and the parking brake -
@drtbkj Hi mate , forgot to tell ya , few days before , … you have a bug in update 1.4.exe .
When updating “Theater” tdf/tga files… it puts them in wrong dir … missing “Theater Definition” in path.
You know, files should be in “\Add-On OFMKTO\TerrData\TheaterDefinition” but update puts them in “\Add-On OFMKTO\TerrData” … so NO “TheaterDefinition” in path.
Just fyi.
Cheers
Also… file “CP_SCF.LST” , - that file should go somewhere in “…\Art” dir , but is in your “…\Sim” dir … I guess no problem/no effect , just “an orphan”
…and also , in “art/ckpitart” … pits 8926 , 1495 , 2009 , have models files inside there, … not a problem - no effect , just surplus … since models are … where they are
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj Hi mate , forgot to tell ya , few days before , … you have a bug in update 1.4.exe .
When updating “Theater” tdf/tga files… it puts them in wrong dir … missing “Theater Definition” in path.
You know, files should be in “\Add-On OFMKTO\TerrData\TheaterDefinition” but update puts them in “\Add-On OFMKTO\TerrData” … so NO “TheaterDefinition” in path.
Just fyi.
Cheers
Also… file “CP_SCF.LST” , - that file should go somewhere in “…\Art” dir , but is in your “…\Sim” dir … I guess no problem/no effect , just “an orphan”
Thanks, Fang, though strange as TDF and TGA are in Theater Def. in my install.
So, if anyone is having issues with OFMKTO , check and see if a 2kb OFMKTO.TDF and a 222 OFMKTO.TGA are “hanging out” in Terrdata. If so move them one more step to Theater Definition -
@drtbkj You have from previous version =1.4 , check theater tdf file is version 1.4.1 inside.
Even pic (theater - tga) have version 1.4.1 on “BMS MAFIA” pic,But other then that is not different. … all paths are OK … nothing changed then ver number. — So again - No effect if those files are wrongly (not) updated …
Cheers
-
@white_fang said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj You have from previous version =1.4 , check theater tdf file is version 1.4.1 inside.
Even pic (theater - tga) have version 1.4.1 on “BMS MAFIA” pic,But other then that is not different. … all paths are OK … nothing changed then ver number. — So again - No effect if those files are wrongly (not) updated …
Cheers
Thanks, Fang. I posted it over on the OFMKTO thread just to play it safe. It’s a bit strange as part of the new ver. testing process is for me to install it from the Mediafire link just like you do, precisely to catch this type of thing!
-
Good Day, All.
Here’s an update regarding the Mafia Files, and their ongoing evolution. I took a good look at them today and realized that it was time for some reorganization.
So, if you go to https://www.mediafire.com/folder/s8rh0djrr3j3n/BMS+4.35-4.36+Data+Files you’ll find a renamed 4.35-36 Data Files folder. In there you find the files organized by jet. One stop shopping .
Each jet’s folder will have the OFM’s latest flight model(acdata) and cockpit(Art) files. Some may have extras such as DDS files, like the 1799 folder. Some of the folders will have numbers in their name. That seemed a handy way to let you know the jet’s Art folder uses a number and not a name. But, they will also have name labels, such as 1799(F-18C). You should remove the label before you install them.
As of this post the jets with the new format are-F-18C/E, F-14Aggressor/A/B/D, AV8, EF-18M,F-35 B/C, and the Tornado. And, this list will continue to grow. There are also some misc. files such as the 3dbutt.dat for the Mirage.
The individual data files are the “latest and greatest”, literally pulled from my working OFMKTO Theater install. As such, they should work in any of the Chuckles/OFM Theater family, and may work in your theater-of-choice. That is dependent on the plane model the Theater Dev chooses to use and the current version of the Theater. So, as always, it is recommended you back up the original files before you replace them.