This isn’t a bug report, just a place to say in order to utilize the Tornado IDS G in BMS 4.36, I am modifying the game files to add features to the cockpit, especially the 3dButtons.dat file. Currently there is no way to adjust the IFF master knob or toggle the landing light by mouse interaction for example. Additionally things like the HSI course and heading knobs lack mouse wheel support which isn’t strictly necessary but makes it more useful.

If anyone has done similar work or has ways to get easier 3d positions or has ways to add animated switches and dials that would be appreciated.

Voice-assist programs surely count pages but don’t actually read the screen. The pages could be decluttered so as to remove the page options without skipping any pages. A page without any options would still be in the rotary but instead be blank/minimum size. If options 1, 5, and 7 were the only available then the page could be only 3 items tall. If lists and boxes can be variable height and contents it might be worthwhile for decluttering purposes.

As for having all options available at all times, it’s interesting from a realism point of view. Certainly you can say anything at any time. It would be necessary for the AI to respond in a reasonable way to “wrong” messages which were previously impossible. DCS for example simply doesn’t respond at all if you are 1mm outside of the pre-takeoff area and that’s extremely frustrating and confusing. I would certainly hope that if all-message-any-time is implemented that at least a simple reply message is used to indicate some kind of feedback.

I don’t particularly mind either way if one can gain “magical information” about the ATC system based on whether option is white/gray. ATC is necessarily simplified because the controller is not a thinking human. This could have other consequences though tactically like A-M-T which is gray/white depending on if player sensor is over valid target or not. I don’t know if any of that gray/white magic information could be considered cheating but certainly removing that information puts a bigger burden on the player to know the system inside and out.

Ah I can think that checking for wingman reply and seeing all gray is a cheating way to know he is shot down. That’s kinda lame and it would be nice not to know that info magically.

@Carbide The POV1DeviceID is the order the device as it appears in the dropdown menu inside the game, e.g. Keyboard, Joystick, Throttle, Pedals. In this case Keyboard = 1, Joystick = 2, Throttle = 3, Pedals = 4, and so on. POV1ID is which POV from that device to use. In that case the 0 is the first POV, 1 is the second POV, 2 is the third POV, and so on.

For the Warthog Joystick as second in the list (after Keyboard) and Warthog Throttle as third in the list to be assigned as POV1 and POV2 respectively you want the following:
0th POV from the 2nd device is assigned to POV1
0th POV from the 3rd device is assigned to POV2

set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0

@gryfinoxx From memory TOS calc is right. If you ignore caret and fly to make the clock right then you’ll arrive on time. By the way it’s not sufficient just to show up on TOS. You want to hit the TOSs at the scheduled groundspeed. If you do both at those together then the caret won’t jump on steer passage.

E.g. if you’re supposed to show up at 0900:00 with 480 GS and you’re on schedule to arrive on time but at 510 GS then you’re behind schedule. Fly faster or slower to “massage” your RGS to scheduled then resume matching predicted TOS. Then you’re both on time and on speed.

@jstnj LMFD: FCR/WPN, RMFD: TGP. Use FCR to initially cue TGP working left to right screen. Then when object in TGP, DMS cycle to WPN working right to left screen.

Towns have a few small buildings which are lockable. You learn which ones pretty quick.

When you get TGP roughly on target, TMS right for area and slew near it. Don’t point track it yet. Then DMS over to WPN SOI and slew to track the missile. Repeat for both stations when practiced enough to do it rapid.

Once 1 or 2 missiles are tracking, then DMS SOI back to TGP and point track the object the missiles are tracking. Click OSB BSGT for each station.

This is a great program.

In the interest in making it more convenient and automated would it be possible for EZB to run in the background and monitor the briefing.txt for changes? That way pressing PRINT would write to file and EZB would spring into action automatically, no alt-tab required.

The way DCS does it is really nice. If you have a modified file and run an update it will make a copy of your custom file and put it in a backup.001 folder. That’s saved my butt a few times. If practical having the installer check for files which are modified and making backup copies in that way would be a nice feature.

1. With the .key you mentioned it is intended that you use china hat forward/back as the digital control for antenna elevation. That means your antenna elevation is by button presses and you won’t be setting any axis for it.

3. There’s no exact need for the drivers but it’s easy to do and provides a little more natural support. It’s a DX controller which is a standard that should work without any specific software. That’s different than TARGET which is a profiler software which will require effort and is only needed if you want to use it. Install the drivers, skip TARGET unless you want to do Foxy-type programming.

@semlerpdx Yeah absolutely. Although currently what happens when you pick a number option that corresponds with a grayed out option currently?

Direct callbacks (or similar direct API) for every single radio options would be amazing. Then voice-interaction software could skip the whole middle man segment.

@billsirkill The gun only fires when it is selected which only occurs in 3 conditions:
AA master mode, GUN submode
DGFT override mode
AG master mode, STRF submode

Missile override is notably not one of the modes where the gun is selected. Shooting an AIM-120 (the only missile currently in the medium-range category) depends on all sorts of pre-conditions for launch.

Oh that’s a very nice tool. Does it also load the 3d model? Finding the intersection of the mouse cursor LOS with the 3D model would be excellent. You’d basically just click where you wanted a switch and get the coords. That’s better than my guess and check method.

This isn’t a bug report, just a place to say in order to utilize the Tornado IDS G in BMS 4.36, I am modifying the game files to add features to the cockpit, especially the 3dButtons.dat file. Currently there is no way to adjust the IFF master knob or toggle the landing light by mouse interaction for example. Additionally things like the HSI course and heading knobs lack mouse wheel support which isn’t strictly necessary but makes it more useful.

If anyone has done similar work or has ways to get easier 3d positions or has ways to add animated switches and dials that would be appreciated.

@Carbide The POV1DeviceID is the order the device as it appears in the dropdown menu inside the game, e.g. Keyboard, Joystick, Throttle, Pedals. In this case Keyboard = 1, Joystick = 2, Throttle = 3, Pedals = 4, and so on. POV1ID is which POV from that device to use. In that case the 0 is the first POV, 1 is the second POV, 2 is the third POV, and so on.

For the Warthog Joystick as second in the list (after Keyboard) and Warthog Throttle as third in the list to be assigned as POV1 and POV2 respectively you want the following:
0th POV from the 2nd device is assigned to POV1
0th POV from the 3rd device is assigned to POV2

set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0

@regev said in AGM-65G problem : only lock structure and ignore vehicles:

@Raptor said in AGM-65G problem : only lock structure and ignore vehicles:

Have you boresighted the missiles first?

i was in vis mode. how can i do this ?

You boresight against SPI if not using TGP so just get the TD box over the same target as the missile best you can (visual by HUD, with FCR, etc.) and select BSGT.

Centroid track struggles against small angular size targets. You’ll be able to track large objects farther than small objects at the same FOV setting.

I have no idea. Here are my config files (2). When I delete the POV lines from the standard file the POV behavior changes.
https://www.dropbox.com/s/7qtfjk3nqfodo08/Falcon BMS User.zip?dl=0

I don’t know your system exactly but I thought like the device is outputting four axes of information: accelerator, brake, clutch, combined-accelerator-brake. Since DX devices can output 8 axes why would the developer make you pick which mode of operation? Just do both at the same time and bind whichever is needed and not the one which is not needed.

But then I realized they have a mode switch because lots of simple games you can’t pick your axes from a list. You can only press and the game auto-detect. This would make having both independent and combined working at the same time confused. I saw a video of the G25 windows control panel and you have to pick between combined or independent mode.

Saved for finishing later

@MaxWaldorf
I’m not trying to have an emotional event with you. I am telling you my Falcon BMS User.cfg looks like this

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// User can place here his or her specific configurations lines that will superseed the main ones located in the Falcon BMS.cfg file //
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

set g_nNumOfPOVs 2

set g_nPOV1DeviceID 2

set g_nPOV1ID 0

set g_nPOV2DeviceID 3

set g_nPOV2ID 0

@Kolbe-49th said in Falcon BMS.cfg changes:

First, of course you can change anything you want in the Falcon BMS.cfg. But like before, you might lose your personal settings with an update. Hence we advice to store your settings in the User file.

Regarding the problem you describe, as far as I know there are no differences between the files other than priority.

I’m telling you that if you put the lines for 2 POV hats in the user file it doesn’t work. Maybe it’s because those lines don’t exist in the falconbms.cfg file at all. But if the point of the user file to not have to touch the standard config file, doesn’t work for missing entries.

To have 3 independent outputs you need 3 independent inputs. You only have 2 so what you want is fundamentally impossible.
If you want not to have brake with pedals then set the brakes to keyboard.
There is no left brake axis. There is only brake which acts as left brake if there is a non-keyboard setting on right brake or acts as both brakes if keyboard setting on right.
The blue bars show the input. The reverse checkbox changes the output. The checkbox will not affect the input display.

What I would do if I wanted full independent operation of the devices is write a vjoy script which makes accelerator/clutch the rudders when the center pedal is not pressed. Then as the center pedal is pressed the brakes would apply proportionate to the application of accelerator/clutch. So rudder input would be pure L/R pedal, left brake would be L+C pedal, right brake would be C+R pedal. It would be weird but usable.

More simply one could live with single brake axis and have either clutch/accelerator be rudder with brake as brake or brake/accelerator be rudder with clutch brake.

@Bad-Boy said in Falcon BMS.cfg changes:

Don’t modify the Falcon BMS.cfg any more. Always add your new/modified lines into the Falcon BMS User.cfg file

I added:
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0

to falcon bms user.cfg and it doesn’t work. It does work on falcon bms.cfg though. Is it expected that some options don’t work in the user/server files?