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.

It does mean “precision guided munition” even in the HAD context. It’s “PGM-quality.” It’s possible for position quality to be inferior to PGM5 in which case no label is shown.

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.

I did my own test and it does jump on my end. It was just another thing. I see what you’re talking about. Anyway, I only get the behavior from your video if I switch to mark while the cursors are off the map like that.

It’s due to how altitude is calculated. When the TGP is slaved to a point it just aims at it any height. When TGP starts to slew it has its own internal idea of what the terrain under LOS is. If your steerpoint ELEV isn’t exactly the terrain elevation you’ll see this jump.

Clearly a bug. Maybe the waypoint up command on the DEST page got confused with the next steerpoint command in programming. The inc/dec switch should change the value the arrows are next to, not the active steerpoint unless on the STPT or CNI home page with the arrows next to the value representing the active steerpoint. Entering the destination value digitally avoids this behavior.

The same sort of behavior happens on the LIST-MISC-9 WPT page where inc/dec changes the steerpoint active as if it was on the CNI page. I’m guessing because that WPT page is a static nonfunctional page.

From what I’ve read it should not be possible to SEQ the markpoint rotary to FCR until in a ground mapping mode. In your video you set GM before ICP Mark but the cursors are outside of the 60 degree PPI zone when FCR mark is sequenced to. This creates a bug where the FCR is beyond limits and then FCR mark is entered and it doesn’t know how to resume normal behavior. Simply changing MM and back doesn’t inhibit the radar this way. If you have the cursor in the PPI zone when selecting FCR mark you don’t get this. But there is buggy behavior while turning and occasionally providing cursor inputs in FCR mark mode. The cursors jump and jump more the more turning has been done since the last cursor input.

I just noticed this forum software does not allow underlined text… hilarious.

Anyway, if you put FCR GM, turn around so cursors are outside the PPI region, and then set MARK FCR mode you will get this behavior. A quick flip into MO/DGFT override and back will fix it. I think I’ve had this behavior in not mark mode too where GM FCR gets confused and stops updating.

Even when FCR GM is canning in FCR MARK you get these sizeable cursor jumps on minimum slew input after changing heading by a bit.

Looks like. CCRP doesn’t even have a pipper.

@jayb said in Ripple bombing ccrp vs ccip:

@airtex2019

This is how it has been and according to the training manual still is: CCRP is first bomb of a ripple (“bomb stick”), while CCIP is the middle of the stick.

That is not correct behavior in relation to the real airplane.

Everything (CCRP, DTOS, LADD, CCIP) is always middle of bomb pattern equals middle of aimpoint. Half of the bomb pattern will land before aimpoint and half after regardless of 1 or 2 or 3 or …12. The only time you have to worry about the length of bomb pattern is in manual (MAN) mode.

The ballistic calculation is the same. With CCIP because it’s showing you the projected impact point the longer the bomb pattern the farther the CCIP pipper will be. With CCRP countdown is to first release so larger patterns will reach 0:00 sooner all else the same. You can make two profiles PROF1 and PROF2 which are the same except that one is 1 bomb and the other is a larger pattern. Then get on approach to a target, use the freeze command to halt the airplane in the sky, then switch between the PROF1/PROF2 profiles to what what change happens to the calculations.

But does shift-___ go backwards through the pages? I’m just saying look at the original key file and find all the places “Q” (0x10) is used for AWACS menu:
RadioAWACSCommand -1 0 0x10 0 0 0 -0 “RADIO: AWACS Menu”
RadioMessageSend -1 0 0x10 0 0XFFFFFFFF 0 -2 “Radio-send message AWACS”
RadioMessageSend -1 0 0x10 1 0XFFFFFFFF 0 -2 “Radio-send message AWACS”
OTWRadioMenuStep -1 0 0x10 0 0x10 1 -2 “Radio-next menu AWACS”
OTWRadioMenuStep -1 0 0x10 0 0x10 0 -2 “Radio-next menu AWACS”
OTWRadioMenuStepBack -1 0 0x10 1 0x10 1 -2 “Radio-previous menu AWACS”
OTWRadioMenuStepBack -1 0 0x10 1 0x10 0 -2 “Radio-previous menu AWACS”

If I was going to change “Q” key for AWACS menu I would change it not in one place but in 7.

Seems odd. What sensor is selected for marking?

You’d have to open the .key file in Notepad and edit. It might be slightly delicate because the radio menus have lots of .key file entries for next page, previous page, sending stuff. But with care and liberal use of backups you can migrate it to another key. What key do you want to reassign it to?