@Blu3wolf:

Your impression is incorrect. The F-16 flight computer limits AoA and roll rate so that the aircraft does not depart from controlled flight. It does this based on a simple two position switch, the STORES CONFIG switch. In CAT I, you get less strict limiters than in CAT III.

Neither CAT I nor CAT III will prevent you from over-Ging the aircraft or stores carried. They can protect you from getting into an out of control situation though. To prevent over G, you need to pay close attention to the force you apply to the stick.

I had heard that the hornet has a more sophisticated stores management system with regards to flight control limiting, but I do not know any details about it. Its possible that what you describe does exist on the F/A-18 - but it does not on the F-16.

EDIT: Sniped by l3!

…the Hornet FCS won’t “save” you from over-G either, but it does do a far more sophisticated job of trying, IMO. I have a feeling the Hornet does a far better job of knowing how much the jet weighs than a Viper does, and it’s control laws are totally different so AOA is less a factor than is in the Viper case. In fact, I’m not sure it factors at all…

@Gear5:

TE mission, carrier tkoff.
no cockpit glass……errr, canopy.

What, you don’t like that feeling of freedom you get with the wind in your hair?

😉

From what I can tell, it is not possible to assign an axis to the nozzle angle - only individual buttons.

@condor:

i think “nope” means this is user specific…

Okay I will try to make a video of it.

I know nothing about torrents.
Read chapter 3 in the BMS manual for install instructions. Online Manual here(sorry….english speak ;))

No, not really illogical. This effect is correct only when jet is not moving … at high speed, render is wrong anyway, and cost FPS.

250 is the BMS’s choice.

Feel free to change it on you own .cfg

I’m happy enough with the excellent work giving us a decent flyable GR4. My only suggestion is purely visual. When loading 4-8 bombs on the fuselage rails they all disappear. 2 show fine on the forward body rail pos but adding any more makes them all invisible.

Thanks all of you for the usefull replies

@Red:

Did you try reducing the shaders as the BMS manual suggest (quest for FPW chapter?)

We know 4.33 with displays on (especially TGP, WPN and FLIR) have a huge impact. But in your case mate. 48 fps is not a huge impact
It’s huge for you because you focus on the FPS display
Disable it and come back to tell us that the simulation is choppy at 48 FPS??

Some of us suffer from FPS as low as 15-20 in such situations and that IS choppy. So I rather thing you’re on the safe side of the fence 🙂

Choppy it is even at 48 fps, check this vid https://www.dropbox.com/s/imx5v5hry468650/Falcon%20BMS_2015_11_17_15_42_19_453.avi?dl=0
The vid shows the latest driver and this is allready an improvement over my initial start. I’m gonna try a R9 380, perhaps that is a better choice on a pcie 2.0 system

Hello
The toggle empty cockpit shell work with F16 and not with F18. Do you have a solution ?

@Alligin:

As per the tittle.

I cant get the mini stick on the X65F to move the radar cursor. The mini stick does not show as an axis.😕

Any ideas or would anyone share their X65F profile?

Thanks Alligin

For the x65f you have to create a new advanced command.
Enter the keystroke this will create 4 boxes. shft, arrow, shft, arrow.
select the 2 last boxes and click “cut”
and “paste” those in the release box and then click “OK”. Done…

I shot a couple POS (EOM) HARMs at some steerpoints. I shot one showing 3:00 PTOF and 2:00 PTOF. Threat type was set other than the threat so it would not do anything but plow into the ground at the steerpoint. HARMs were fired ~20,000 level with zero relative bearing and the FPM in the middle of the upper and lower tick marks.

Notes:
“3 minute” HARM 05:58:04 impacted 06:00:12, 1:46 TOF.
“2 minute” HARM 05:59:46 impacted 06:01:23, 1:38 TOF.

Post launch countdown TUI (EOM or PB) was not a simple timer but adjusted not smoothly and not 1-second per second. TUI also reached 0:00 to coincide with actual impact.

Missiles destructed 160s (not 200s per 4.32) after launch.

To a large degree it feels like things have been scaled by the max TOF duration. The “3:20 (200s)” PTOF seems to correspond to almost exactly 2:40 (160s) actual TOF at least at max range. 160/200ths is 4/5ths or 80%. 80% of 2 minutes is 1:36. Notice the initial 2:00 test ended up 1:38 TOF. 80% 3:00 is 2:24. I ran the “3 minute” test again and got 2:11 which isn’t too far from 2:24. I recommend reducing all shown TOFs to 80% value as best guess for now.

Thanks, but I have never changed the seting.
I checked the .cfg file but set g_bMouseButton4TogglesClickablePit was set to 0, so right clicking must pan the view but it doesn’t.

I found another thread which might be talking about same problem.
https://www.benchmarksims.org/forum/showthread.php?23682-Mouselook-does-not-want-work!&highlight=click+pan
Maybe I have to uninstall some freetrack like programs if I want to use mouse panning…

I’m also having sometimes trouble with syncing the throttle in game. At that point I can slowly move up my throttle to full AB and moving. But
when I bring it back down, it starts firing up the engine…
appears to be happening only during TAXI (both before and after flight). In flight it seems to be just fine.
I too use Dunc_DX which uses the paddle for breaking.

Any suggestions? Is this a known problem?

I googled around quite a bit with negative results; So I recently installed Falcon 4.0 and BMS 4.33. Game was great, amazing performance, great immersion with the pilots body in the Israeli theater. The problem: When launching the game and setting up a mission, I click the “Fly now” button. Instead of the splash screen with the F-16 and the loading bar appearing, my screen turns off, the graphics cards turn off, and the computer turns off. I have windows 7 64 but, two Titan x’s in sli. I deleted the drivers and reinstalled them, no results. What do I need to do?

@Smokin:

I am having a similar issue. Using a CH throttle I am able to start and shutdown the F-16 just fine, as always, by mouseclicking the lever on the throttle. However, that does not work with the F-18 (for me). The little switch in the group of five avionics switches several inches forward of the throttle is listed as the idle-cutoff. But that seems to do nothing. I have Alt- listed as my Throttle Idle callback. But that also does not work to start either the F-16 or the F-18. Again, not a problem in the Viper because the mouse-click works fine. Using the Idle setting in the Config, does allow me to start the F-18 but with that option selected I am unable to shutdown either plane.

F/A-18 Ramp Start video for BMS 4.33 here: https://www.benchmarksims.org/forum/showthread.php?23587-Hornet-Ramp-start-Video&p=339859&viewfull=1#post339859

FYI. 🆒

Well, then as written before it’s impossible in the game as of now.

You are the Man Blu3wolf, it works. I have been spending hours in my cockpit config for it and it was right there 🙂

Thanks!

Thank you everyone. You guys are the best!

Have a look at the BMS Manual page 12.