Frederf

SOI selection has changed some months ago. Coolie down selects helmet SOI.

The letters N E S W are printed on the 2 6 4 8 keys respectively. So entering N 12°34.567' is done as 2 1 2 3 4 5 6 7 ENTR.

Thank you I skimmed the video before but didn't see that. My picture was a hasty Photoshop but funny how similar it was to the actual thing. I hope it's applied to more than just fuzes.

I think ultimately there is so much configuration to many different types of store that it's not efficient to make specific solutions for specific cases. A general purpose "configurator" for stores possibly as a separate dialog will open the door to lots of adjustments. ECM pods might have different settings and modules, fuel tanks can have different contents and fill levels, bombs have fuzes, racks may have different weapons at different places on that rack, rocket pods might have different rockets in different zones, etc.

If the lights are flashing then something went wrong. That's usually due to engaging auto-hover below 4m and/or (can't remember exact) before the Doppler system is ready. A fast start up puts ground power on first so you can get the K-041 system warming up as early as possible.

Use the autopilot.

Start SRS on its own without DCS running and don't connect to any server. Change the input device and then close SRS. Open SRS and the input device should be the same as when the program was closed.

Label next to OSB10 on the FCR format shows "STP" instead of the correct "TGT" on FCR format when no TGP is carried. "TGT" label should be used in all preplanned AG modes instead of "STP" and labels for FCR and TGP format should always match. Aircraft without TGP Situation in which STP should be displayed: NAV, ACAL, FIX, AG MAN, SJ/EJ* Situation in which STP should not be displayed: AG VIP/VRP, NAV VIP/VRP**, CCRP, LADD, EO PRE, EO BORE, DTOS, CCIP, STRF^ Aircraft with TGP Situation in which STP should be displayed: NAV, ACAL, FIX, AG MAN, SJ/EJ* Situation in which STP should not be displayed: AG VIP/VRP, NAV VIP/VRP**, CCRP, LADD, EO PRE, EO BORE, DTOS, CCIP, STRF^ Correct Cannot Observe Not Correct Unknown *Unable to change FCR to GM type mode in JETT **Unable to select VIP/VRP in NAV master mode ^Documentation says that sighting rotary should be blank in AG visual modes which is the case in AGR but unsure if it should also be blank if the pilot changes the FCR to GM type as well. In DCS in AG visual attack modes and FCR shows a label it is "STP" or "TGT" depending on if TGP is loaded and not blank. F16 Sighting Point Label STP without TGP.trk

It used to be that way but I just tried and the A10C2 ED defined payloads come back. I'm guessing they're all that way now.

This is a normal behavior in how the calibration is implemented. I will draw a picture.

The sighting point label, what you call "TGT" button, should have a label of STP or TGT depending on if in navigation or attack mode respectively. The label can be other things but let's keep it simple. On the FCR and TGP format at OSB10 the sighting label should always be the same between the two. I see that without TGP the labels are STP in NAV and STP in AG while with TGP they are STP/STP in NAV and TGT/TGT in AG. The highlight in red is a bug but it doesn't matter what label is displayed. The same thing is happening regardless. I don't get this behavior. You can see where SPI is moving by looking at HSD cross symbol. In general there is no need to press TMS forward with the radar. Are you using laser-guided bomb perhaps? TMS right is the same thing as pressing OSB10 (if HUD/FCR SOI). This shouldn't be needed (bug) but when radar is SPI-source and TGP isn't following SPI this will "remind" TGP to look at SPI like it should.

I don't see any access to the TEMPO() command in the TARGET GUI except for "view script" and manually editing it. I must give all recommendations to learning how to write .tmc script in the TARGET Script Editor. It's not that complex to learn and can do so much more than the GUI.

Both X and Y pulse coding can do DME.

The sighting point option is displayed on the FCR and TGP formats at if memory serves at OSB 10. Depending on the situation the sighting point label can be STP TGT OA1 OA2 IP RP or blank. Due to a bug sometimes the LOS of the sensors get unsychronized and cycling through sighting points "kicks" the sensors back into sync. Often the list of points is only TGT, a list of length 1, but changing from TGT to TGT can have this effect. Usually TMS right is the HOTAS shortcut to cycle sighting points. One can see that with FCR GM and TGP both up that slewing radar the TGP doesn't follow (it should) and TMS right presses will drag the TGP to the radar SPI momentarily. This is a workaround.

Looks normal. For that load it should have been an afterburner takeoff and rotation is less than 200 knots but those things aside that's normal. Demo track: Kobuleti, 30.51 +23C, 5m/s 118to, 2000m 7 109, turb 0.3 F16 xwind takeoff.trk

There are three attributes in the A-10: default, waypoint, and flight plan waypoint. Default determines what attributes are for the next created. A waypoint's attributes can be different in a flight plan as not. E.g. MSNO02 can be three ways: when not in flight plan, a different way when used the first time in a flight plan, and a third way if used again in the same flight plan. Here's a track demonstrating the independence of the attribute settings. P.S. flight plan is not limited to TO-TO or anything. A10C2 Attributes.trk

You don't have to designate the radar. The SPI is the radar cursor location just by slewing over it. Designating it for the diamond shouldn't make SPI go to steer though.

The calibration is perfect. At shorter ranges the fact that the missile and TGP are laterally displaced causes noticeable parallax. This will be most noticeable at the short ranges on the ground.

I look by eye. But most of the time my first try is pretty close in terms of timing. If you really want to "git gud" then the drill would be to set up the airplane in the approach situation (so opening time is consistent) then try opening to what you want checking visually after each attempt. After some practice you'll be hitting your desired state blind.

Makes the bomb explode or deploys the high drag device if that can be considered a fuze. A detonation fuze in the tail allows other equipment to be installed in the front such as a ballistic cap, proximity detonator, laser guidance kit. A tail fuze may have less chance of failing when impacting certain surfaces. When used in combination with a nose detonation fuze a tail fuze may be set to a different configuration for flexibility in timing selection or simply to reduce the chance that both fuzes fail preventing the bomb from detonating.

It's one of the first things I tested and I found that tracks generated invisibly in RWS were immediately available as tracks in TWS when switched. In the first track the radar actually lost complete contact with the targets so there was no track in the background to be shown. The only thing that looked wrong is that TWS bugged the target on redetection practically immediately instead of showing a contact and then developing it into a track. But I don't know if the user was mashing TMS forward or something unusual at that moment or not.

The three bands seems to be reserved simply to visually differentiate the BLU-111/110/117 warheads from their Mk-82/83/84 equivalents. As far as I can tell It can also be taken to mean the use of PBXN-109 instead of Comp H6 as all the USN BLU-100 series bombs have the more insensitive filler.

Ah sorry, but the F-5 thing is also real so it makes a bad testing platform.

That's actually a bug with the F-5 RWR, not the MiG-21 radar. With the F-5 RWR when the "S" button is pressed on the RWR control panel one hears search warnings but no lock warnings. When the "S" button is not pressed you hear lock warnings but no search warnings.

Not that I know of. The push on the knob is to access the rare inflight alignment heading adjustment. Maybe it's a feature added later? AP roll channel just does heading bug, bank hold or direct to INS.