BMS Other Fighters Mafia (BMSOFM) Journal
-
<p>@drtbkj Thanks for the info! If you don’t mind, I would like to combined your checklist into the F-18 checklist to bring it up to a…“community standard”. <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f60a.png?v=opoh9i0f0lo” alt=“” class=“not-responsive emoji emoji-android emoji–blush” /> <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=opoh9i0f0lo” alt=“” class=“not-responsive emoji emoji-android emoji–+1” /> </p>
-
<p>@JollyFE Here’s one I did based off of the one that was posted. I made it easier to read and more like the checklists you find in the BMS manuals for the Viper. Get it from this dropbox <a href=“https://www.dropbox.com/s/e53re8uds8yp3t8/BMS 4.35 F-18 Checklist.pages.pdf?dl=0” target=“_blank”>link</a> </p>
-
<p>@JollyFE It would be great if you could “pretty it up”. When I wrote this I was trying to combine a checklist with notes.<br /></p>
-
<p>@drtbkj see my post with the link. I prettied it up. </p>
-
<p>@Todd1215 Thanks Todd! Nice format job on this. <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=dsk3o53jm16” alt=“” class=“not-responsive emoji emoji-android emoji–+1” /> </p>
-
<blockquote>@drtbkj see my post with the link. I prettied it up. </blockquote><p><br />Todd ( and Jolly), thanks for this! Todd, with your permission I’ll put it in the Mafia Files, and convert to png to kneeboards. Before I do so, I noticed 2 things…<br />1) Before Engine Start Item 15- It’s correct as written. However, I tweaked the cockpit files further after I wrote this. With the 3dbutton.dat now in the Files JFS 2 is now on the <em>right </em>mouse button. It doesn’t change how the jet starts, but the engine crank switch moves right instead of left, simulating the RL right engine starting first. Could we change this to “Engine crank right” and “JFS2 (right mouse button)”?<br />2) In Taxi, Item 9, Launch Bar is spelled wrong .</p>
-
<p>@drtbkj still working on it. I decided to fix a few more things before I give it up.<br /></p>
-
This post is deleted! -
<blockquote>@Todd1215 Ok fixed and converted to png<br />Link <a href=“https://imgur.com/a/Z8MuGrw” target=“_blank”>HERE</a><br /><br /><br /><br /></blockquote><p><br /><br />Hi, Todd. I’m only getting the first page in .png. If you’d like to send the pdf for the checklist I’ll take care of it. Also, just to confirm-are you ok with this being included in the Mafia Files?</p>
-
<p>@drtbkj Ok here is the link to the PDF in dropbox. Also my intention was also to allow this to be used in the Mafia Files. I’d give you the source but I created in on a Mac using the Pages app.<br />Dropbox <a href=“https://www.dropbox.com/s/s7z628i59p4iu33/BMS 4.35 F-18 Checklist.pdf?dl=0” target=“_blank”>Link</a></p>
-
<p>I skipped BMS forums for a while… but this thread is hard-warmingly good :)</p>
-
<p>Great, Job, Todd! They are now in the Mediafile Mafia Files. I’m going to be afk for a couple of days, but the .png’s will be in by the end of the week. <br />Hi, AS, and I’m very glad you’re enjoying the thread!</p>
-
Good Day, All, and welcome to the Wonderful World of 4.36! I’mjust getting past the initial setup, but I am very happy to confirm that the hotspots are correct in the F-18C . Thanks to the Dev’s for including that! I’ve only checked out the Legacy, so if anyone’s jet of choice isn’t right let us know here.
-
@drtbkj All F-18C versions and later “should” have the F-18C cockpit. (F-18 A/B & Aussie F-18’s have A model cockpits). But definitely report if you have any other type of cockpit!
-
Thanks, Jolly,
All, Tonight I’m working on loading the new laser Mav on the Hornet , but did spot check some cockpit files in Art. The CF-188 and EF-18 does not have that file.
The good news is that as there were no LOD changes to the other jets, the procedure listed in the Fighters Manual ( in the Mafia Files) will still work.
One Further note- In reading the Naval Ops Manual it seems the F-14 comes with a Viper cockpit. If you should desire a Hornet pit for Launch Bar and other things, the procedure to do that is also in the Fighters’Manual -
Good Day, All. This morning’s update is about the Laser Mav. The 4.36 base install’s Hornet doesn’t have it in Loadout. The good news is that it’s easy to fix. I’ll be posting a How-to here later today.
-
Look forward to your How-to posts drtbkj! Shall we input them into the Naval Ops manual, “Change 1”.
-
Ok, here’s a mid-day report…
- We are currently 4.36 compatibility testing the acdata files and skins we had developed in 4.35. We’ll let you all know ASAP
- Jolly and All, we have the laser Mavs on the Hornet in KTO and Balkans. Here is the procedure for your jet-of choice, using the Hornet as an example…
a)On the main launcher page, go to Editor/weapons and Squadron Stores tabs/scroll down the list to your jet and click on it.
b) a Squadron Stores Editor page will appear. The F-18C is SSD 26 in my install, for example. Click on “show weapons not carried” then scroll down that list to Index 699 (Mav E). Double click on it and adjust the count. I generally use 200.
c) Repeat Step C with Index 718 ( Mav L), then Save
d) Now go to Weapons and hardpoints tabs. Scroll through the list and find each hardpoint on your jet that will carry a Mav. On the Hornet it will be" F-18C 2/8" and" F-18C 3/7"( Two separate entries) . For each entry click on it to go to a Hardpoint Data Editor page.
e) The HDE page will show the weapons assigned to that hardpoint. Scroll down to a “No Weapon” entry and click on it. You get a Select Weapon page, scroll down to Index 699, click on it, and adjust count ( weapons/hardpoint) . Try “one” for now. Repeat with Index 718
f) Save. That completes the Editor part of the process, and you can close it out
g) In your File Explorer go to 4.36/data/terrdata/Theater Definition/theater.lst. Open that with notepad. You want to make sure that “TerrData\TheaterDefinition\Korea KTO.tdf” is on top of the list, not TVT. Save changes, if any, and close
h) If you don’t already have it, get Mission Commander 5.19.667. Open it, go to your squadron , and click “Resupply”. Do the appropriate “applies” and “saves” and you are done. Now you can load the Mavs in Loadout .
In our current testing we have loaded the Mav E in both KTO and Balkans, and are testing functionality
-
@drtbkj Is it me or has the F-18C FM been changed in 4.36? Asking you since you’re probably the most knowledgeable about it.
Did some dogfights with it and it seems to almost stall/give warning for a stall/the TO/LDG warning light quite more easily compared to 4.35 with the Acdata files from your gitlab.
Should I add the respective Mafia files to 4.36 too or is it just my impression?
Edit: Oops, didn’t notice your latest post as I had the topic open for quite some time without reloading.
-
@unkindled said in BMS Other Fighters Mafia (BMSOFM) Journal:
@drtbkj Is it me or has the F-18C FM been changed in 4.36? Asking you since you’re probably the most knowledgeable about it.
Did some dogfights with it and it seems to almost stall/give warning for a stall/the TO/LDG warning light quite more easily compared to 4.35 with the Acdata files from your gitlab.
Should I add the respective Mafia files to 4.36 too or is it just my impression?
Edit: Oops, didn’t notice your latest post as I had the topic open for quite some time without reloading.
Hi, Unkindled. Yes, hold off a bit before you start loading acdata and such. Tonight we’re busy trying to figure out the laser Mav. I do plan to dogfight the Legacy . We also tested simply plugging our 4.35 acdata and it caused a ctd. We think we have that fixed, and I will let you know.