@Jackal
Noted

Btw has anybody tested AAR with the Typhoon and can report back whether the position basket/probe is correct? Ideally with screenshots if the position doesn’t fit. If so I’ll put it on my to do list.

General remarks, the FM is OFM, not AFM, as I first want to get it right and reasonably close.

I have addressed a number of topics on the fly, such as implementing the emergency arrestor hook (would need some testing apart from the visual implementation).

Weight and fuel loads are accurate now.

Gun location is fixed, matching the new 3D Model.

Chaff/flare dispenser quantity, position and loadout are correct. Two chaff dispenser at ITSPL position and two flare dispensers on inboard flaperon actuator fairings.

Air intake vary cowl movement is now implemented, animation behaviour has been implemented, but needs some validation testing.

General control surface movements and behaviour have been adjusted (airbrake, nozzles, slats, flaperons, roll coupling of foreplanes and “landing flaps” removed).

The general limiter values have been adjusted as part of the overall FM.

As long as no dedicated models of Typhoon racks and pylons are implemented I have assigned those available in the DB and created appropriate rack entries and groups. There are subsequently ITSPL, DMMEL, ALDERU, AHDERU, TEU, MFRL and Brimstone tripple launcher available. MFRL and Brimstone launcher are attached to ALDERU. Due to the lack of a proper 1000 l SFT model the TEU is a separate pylon but goes of with the tank if jettisoned. AAM jettison from FSU doesn’t work yet though and I’m not sure whether the it will be possible to only get the wing pylons and centreline station shown on the SMS page. To be done are dedicated rack entries in the DB to provide tailored weight and drag data for these. Hence no FM testing with stores yet.

Weapon loadouts have been matched with P2Eb and P3Ea standard A/C as operated by GAF and RAF respectively.

I have also adjusted the avionic options to best match the Typhoon within the given constraints. Feedback on that would be welcome as well. This also includes radar data and autopilot envelope.

In the future it’s ofcourse desirable to get everything included in the stock BMS release to permanently improve the simulation of the A/C. I have made an initial package available, we’ll see whether it will find its way into the next update.

Medium to long term a 3D cockpit would certainly be the most valueable addition though. But that needs someone with the will, time, the experience and skills.

I have deleted the link to the open beta test version of the EFTP. The modded Typhoon is now fully integrated with the OFM Theater which can downloaded from
here.

OFM development is now complete with v1.2. I’m now progressing with what I call the hybrid flight model, which attempts the development of an AFM. It might be a bit simplified though, compared to the extant AFMs for other aircraft.

Update on the general progress:
Beta 1 FM testing is thus far complete and findings are being adressed and progressively tested. Major challenge with the OFM is to tune the supersonic lift values to limit g-authorities. AoA limiters work reasonably well, not perfect though. Idle thrust and fuel flow tables needs to be reworked yet.

Vary cowl animations have been tested and refined and are now working satisfactorily. Roll data are now complete as well.

Engine nozzle animation behaviour is now properly implemented and the advanced engine dynamics have been introduced. These are preliminary and need further validation testing and refinement, but work satisfactorily for the moment.

MFD symbology colors have been matched as close as possible to the real aircraft within given constraints. These are part of the FM.dat and can be replaced with the DTC values, if required. Some testing is required to determine whether all changes are acceptable though, given that the symbology is not exactly the same in the F-16.

Other avionic settings have been tailored to best match the Typhoon. Auto throttle control activation is still being investigated as it seems not to be a simple 0 or 1 only switching.

Dedicated racks have been included in Beta 1 already, but related testing is postponed, until FM development of Beta 2 has progressed to a satisfactory level.

For Beta 2 I consider an open test, maybe using JSGVM or another suitable mod manager.

Gents,

I have created a BETA 1.1 for open testing, as BETA Flight Model development takes more time.

The changes, compared to the stock BMS 4.36 Typhoon aircraft are described within the readme file, as are the installation instructions.

NOTE: If your install is modified (database edits) this mod may cause issues. It’s extremely important to backup the files you have, as described in the readme.

Simply extract the zip to a folder of your choice, backup the files of your install, as described within the README. Then extract the install.zip file on your Falcon BMS 4.36 maindirectory. This will extract the files in the appropriate folders and overwrite those already located there.

I haven’t managed to get it working with OvGME in time, so I decided for this simpler solution.

Feel free to test the modified aircraft, its flight model, weapons and avionics settings. If you have any questions, comments or other observations let me know.

If devs of the BMS team or theater feel that this mod is good as is, or wish to include content of it, feel free to do so, giving credit to me. I can support devs, if required to support integration of the modifications, if required.

LINK DELETED

Best regards
Scorpion

Hi all,

I seek some volunteers, presumably with an EF background, to test my new WIP Flight Model for the Typhoon. Anyone who is interested can contact me here or via PM.

Testing should include general handling, maneuvering capabilities at all speeds and altitudes, kinematic performance, altitude performance, acceleration and climb performance tests, endurance and range tests of a clean aircraft.

@rookieskyworker said in GBU-53:

@canuck Hello. I also have same question and I surf the web and I see your posting.
I think it has some limitation about launching. I set GBU53’s mode from IR to Laser in editor but it doesn’t work. And I find GBU39 has visual guidance and 53 has IR guidance in editor. I think GBU 53 has no traking guidance against moving target. It just dummy I think.

You should take the LJDAM as an example (GBU-54). It’s not just the normal guidance, but also the pointers. Haven’t played BMS for a while and haven’t moded it since a while either. Might be that GBU-53 already works like the LJDAM, check the settings on the SMS page.

@danaos75 & @Logic

thank you. I’ll give it a try for 4.36 setup, might make things easier.

@drtbkj

yes tried and verified all this already. No problems when flying the Hornet. Hence the thought about the flaps relationship, due to the approach and cruise modes on the Hornet. I’ll do some additional verification tests with TEF implemented in the FM, just to see whether there is a relationship or not. Found no related entry in the afm.dat either.

@JLSPENCER02-0

LE 6.23 is still usable with workarounds. You need to extract the DB with theb3ddb_builder first. Then open the HDR file of the original F4 install. Then select open file, browse to the LOD in the extracted DB and open it. It might be necessatry to first increase permissible NOD size before you can open some LODs. If you have changed something, you need to repack the DB with the 3ddb_builder. You can find the 3ddb_builder and its manual in the TOOLS subfolder of BMS.

<p>In reality EF2000 isn’t using any dual, tripple racks as of now, apart from the Brimstone tripple launched. A new twin rack is envisioned for side by side carrying of typically two 500 lb class munitions or alternatively carriage of three Brimstone or SPEAR 3.<br /><br />P.S.: The loadout options in BMS for the EF2000 have always been wrong as for most flavours of the sim. I have corrected this several times with my previous EFTP series, but it has never been carried forward, like other changes, with exception for OF 4.6 and FF5 (partially).</p>

@qawa

If there is any chance for a new Typhoon cockpit, I can at least provide some support for its functional design tailored for BMS 4.36.

The F-15E shots look pretty nice. Though I value functionality over looks. Both is premium

@white_fang

Curious, I thought the “glued to ground effect” was limited to non-afm A/C and that it had been fixed with U1. Haven’t tested U1 yet though.

As it was said it is a code thing which has something to do with tilting, I could imagine it has something to do with the wheel strut movement (shock absorbers). It might be worth to try by setting all values in the dat file to “0”, have thought about it weeks ago already, but didn’t mind to test it, as it was said to be a code thing to be fixed with U1.

@Obi1 said in LodEditor:

@Scorpion82 emmmh, “HDR from the original F4 install”? Any pre 4.36 BMS version HDR this works for? Or do you mean the original microprose F4 version? Asking because I can’t seem to get LodEditor working after creating a database LOD/HDR from extracted parents with 3ddb_builder. Always getting this #3Array error afterwards

I mean the original Falcon 4.0 that you should have installed for the validation check of BMS. It supposedly works with 4.33 as well, but haven’t tested it myself.

@Snake122

You are talking about different symbology, rather than different colors only?

@JLSPENCER02-0

LE 6.23 is still usable with workarounds. You need to extract the DB with theb3ddb_builder first. Then open the HDR file of the original F4 install. Then select open file, browse to the LOD in the extracted DB and open it. It might be necessatry to first increase permissible NOD size before you can open some LODs. If you have changed something, you need to repack the DB with the 3ddb_builder. You can find the 3ddb_builder and its manual in the TOOLS subfolder of BMS.

@Radium
So in this case we lean back and relax

@ccc1tw
if that’s the case and we want to have weapons in weapon bays that add no drag, then the only solution is to work with dedicated rack entries, in the bmsrack.dat and dedicated rack entries. I could fo this, if there is an interest for this. But would recommend that first the aircraft are named that are required to receive this.

@ccc1tw said in Chengdu J-20:

just my 2c,

if you untick visible for weapon bay items… once [Bomb Bays code] activiates, you won’t see weapon models.

then you have to tick visible again.

You mean, that you can’t see the weapons in the weapon bays, when they are opened?

@TOPOLO said in Chengdu J-20:

@edrasom Clean, the BMS J-20 should be able to reach M2.5 @47,000ft
As AA missiles are in bays, they should not add drag, unfortunately, even if the weapons-in-bay feature is working for F-22, it does not for J-20 (and I’ve tried many things, but never find a way to solve this issue)

The solution to this problem is simple, you need to untick the “visible” box for the weapon bays in the VCD (index number 423 for the J-20). Simply untick the visible boxes for the slots 3-8 and you get the weapon bays working as in the F-22. In the weapon loadout screen it’s evident by the “+/-” triangle symbols, rather than the circles and you’ll notice that the drag index will no longer count up, if you add weapons to the bays.

@TOPOLO
I’ll provide more specific feedback when I’m at the PC. when pulling fully back at the stick the aircraft pitch up, then bounced down, unloading and the process repeated if you kept the stick fully back. This occured somewhere between 300-500 kts at least. I encountered similiar issues during Typhoon development especially at supersonic speeds. I figured that the “artificial” AoA limiting (no lift from AoA X onwards) caused the aircraft to briefly exceed that AoA limit, if it was below the actual CAT AoA and due to the lack of lift it was pitching down rapidly for that reason. This was what I experienced with the J-20 at the subsonic speeds. As said, I need to test again to test the specifics. Will report back as soon as practicable.