Frederf

To get a consistent diamond shape the straight and swirl pattern legs have to cross at a consistent angle. If you know the min and max diameters and the diamond angle the swirl shape becomes exactly known. The drawing above doesn't look like it could produce a large range of intersection positions. Depending on which pattern is fixed determines if the diamonds slide radially or not. If the swirl pattern is the moving pattern the the intersections do not change clock position. I was using MiG-21 sight and the animations in the MkII video as a guide and those curve. I wouldn't put too much stock in the blue illustration above. It doesn't demand up on the page is up on the sight.

You just send both type ingress along with a target types. It doesn't matter which order. But it only seems to work with engage order. Go-to or recon tasks are straight to point only. It's not possible to send typed points from Shkval directly to AI over DL. This is because the type buttons are for selecting memory points. If you pick type (without any of that type in memory), recipient then AI will receive nothing. To send point to AI from Shkval or PVI directly you must use untyped messages. Just don't pick any of the four types and the point can be used for engage/recon/go-to. Obviously this limits what is possible as untyped points don't allow "engage by type" or the ingress function. For that they need to be typed points from memory. Ka50 DL attack.trk

7.5g full, 9g empty I believe. They burn a lot of fuel fast in AA practice. If they have 7000 departing tanker, maybe 6000 in the practice area, at 80,000lb/h and a 3k bingo you have like 135 seconds training before you have to AAR again?

Because to "train like you fight" you have to either kiss off 2x370 tanks every training engagement or suffer dogfighting for a split second without any external at all. Center line simulates jettisoning 2x370 at the merge without the expense.

I've not seen any combat USAF load that didn't have 370s. There is one photo floating around w/ centerline + 6 live AMRAAM but it's mythically rare. Center line is nice for AA training sorties, enough fuel to practice a bit and you can fly it like a clean airplane with the center empty.

You aren't supposed to use ingress points as destinations. They are designed to be optional middle points en route to a destination. The idea is you give an AI a target point and optionally an ingress point as well. They will fly to the target point directly if no ingress point is given or to target via the ingress point if ingress is given.

The diamonds of lights are produced by moving and rotating metal shutters. The rotation of the individual diamonds and their placement about the circumference of the circle is a consequence of the mechanism. It is a repeatable behavior, for every particular diameter setting the rotation of the diamonds as well as their placement about the circle will be the same every time. By changing the diameter of the formation the diamonds will follow a curved path and they themselves will twist in orientation. A diamond will be at the 12 o'clock position at one diameter and a gap at 12 o'clock for a different diameter. Observe at 4:50 in the video above how increasing the diameter causes the diamonds to spiral outward along a clockwise path and the diamonds themselves rotate clockwise. Due to the spiral path at no time are the diamonds oriented such that their points point toward the center. https://youtu.be/ea2IB48lOuo?t=288

It could have been in early development. The real airplane always has the behavior of showing a delay cue and visual designation pipper if the realtime solution leaves the HUD.

Real airplane always has it and DCS has as well far back as I can remember. If you want "simple release" as in direct control of weapon release then there's always manual mode but you won't have CCIP or CCRP aiming assistance in manual.

Yeah it's real. 3xCBU-87s don't fit either AFAIK. Maximum is slant-two for GBU-12 and the larger CBUs. The full TER of three is limited to MK82s and maybe? the smallest CBUs (Rockeye). The only 12-weapon loads I see are MK82 and MK82 AIR. It's not just if they fit. If you've ever put your hand out the window of a car at 80 mph you know the wind force is strong. Now think about 580 mph. Even a half ton bomb can get blown around unpredictably with small aerodynamic features. Every loadout has to go through specific carriage and separation testing. It can't wiggle in a bad way or produce undue stresses or come off dangerously. Remember that GBU-12 has big pop out fins too. Passing the flight test isn't guaranteed just because a similar or even larger store passed. And lastly they don't test loadouts they don't plan on using because it's expensive and time consuming to run these tests. It takes dozens of hours with very specialized test squadron time. A particular loadout might be fine physically but it hasn't been tested. If it hasn't been tested specifically then it doesn't get in the approved list. Why would anyone test 6x anything on the inner pylons? For MK82 it's because it was possibly needed for delivering entire sticks of 12 unguided bombs at once. This would have been a test done very early in history, possibly on F-16A. By the time smart or precision weapons are added the need to carry a huge number of them is reduced. Not only would carrying 12 GBU-12s require 12 passes worth of fuel, you'd have at most the centerline external tank and loads of drag. No one felt like a $250,000 test was worth it.

Disabled all scripts and still got the crash: dcs.log

It's because the the laser fires on first stage of the trigger, not second stage. Naturally in real life squeezing the trigger all the way also fires the laser. Because my joystick trigger does both buttons when applying the trigger fully I don't notice this effect. Anyway, it should be logged as a bug so here's a track of the laser failing to fire when only second stage trigger is used. F16 Laser second stage.trk

TMS right (FCR SOI) and OSB 10 should do the same thing. That's the workable procedure to get TGP pointed at SPI.

Yeah. You should see an "L" to the right of the "ARM" on the HUD plus another on the 5 o'clock position of the TGP format. Pulling the gun trigger to half or full action will fire the laser and "L" will blink. Track for demonstration: F16 Laser.trk

Real jet uses whatever number you tell it either DTC load or punch in UFC. It's typical practice to use ground elevation.

The F-16 will put the target box in mid air if you tell the airplane that ELEV is something other than ground elevation. Currently if your flight plan is at 30,000' then DCS will set your ELEV value to 30,000' and not ground level. However if you move the TD box with any sensor (HUD/FCR/TGP) it will snap to the ground. If you CZ the TD box will return to the top of the imaginary mountain.

The sim has some wrong behavior which is making understanding a little more difficult. F-16 is built with a single line-of-sight concept. By design whatever sensor is selected is the master sensor and every other sensor should immediately* stop tracking and be slaved to it. In your example by slewing and/or locking the radar the TGP should already be slaved to the FCR LOS. Sensors looking in different directions is not allowed. Earlier F-16s followed this concept based entirely on SOI: changing SOI would cause the non-SOI sensors to immediately break track and slave. FCR SOI causes TGP slave and TGP SOI causes FCR slave. *In later F-16s there was a small exception made: TGP (and only TGP) keeps tracking if another sensor becomes SOI until some input is made (slew or track) on the other sensor. Your step of pressing OSB 10 to get the TGP to slave is not behavior in the real airplane. A real pilot would not be trying to change sighting point because there would be no need plus it wouldn't actually do anything. But I will explain how DCS has an effect by sort of changing sighting point shortly. Normally sighting points are some distance displaced from the steerpoint or target. I'm going to use OAPs as example because they are less complicated than IP/RP. Unfortunately the sim doesn't have OAPs in yet so you'll just have to follow along with my description. Say you're trying to bomb a bridge but for some reason it's not expected to show up on radar, made of stealth concrete or something. But intel says there's a radar significant tower east 3000'. So you program in an OAP 3000' east of target and select it in the sighting point rotary. Your target is still the bridge but your sensors (FCR, HUD symbol, TGP) are going to be pointed at the tower during the attack. In this way your weapon aiming point is offset from your sensor(s) point. Look B, kill A. So the mission is going on and for some reason you change your mind. You don't want to use the OAP and tower to define target location. You want to target the bridge directly. So you change the sighting point from OAP to TGT, as in where your sensors are pointing will be the target location. Look A, kill A. This change of sighting point could cause your sensor cursors to jump by 3000' by mistake. If your master sensor was tracking, changing sighting point would cause a 3000' slew shift. To prevent this the designers have made it so all sighting point changes cause all sensors to break track. By pressing OSB 10 (or TMS right unless TGP SOI or AGM-65 selected) you're commanding a sighting point change. Really there is only a list of one item (TGT) in the rotary. Changing from TGT to TGT shouldn't count as a change so no sensors should be commanded to do anything. But DCS considers TGT to TGT a change so the sensor break track command is happening anyway. But as we read before the TGP should have already been slaved because you were using the radar. By rapidly pressing OSB10/TMS right you can approximate what the airplane should be doing as each press causes the TGP to slave to FCR LOS. In reality this process is continuous and doesn't require any pilot input.

You should be able to change EO submode with enable or the WPN OSB. But cycling AG weapons is always OSB 6 on SMS. Two different AGM types are just as different as MK82 and CBU.

You used to be able to do that many patches ago but it was changed. You can't do it anymore.

You can't but don't worry. Even when you have an alternate point cycling the point doesn't change the label properly. It's TGT not TGP though meaning target. In most situations the steerpoint and target are the same. It should just say TGT in attack mode and STP in NAV mode. But they have the same practical effect. The only time sighting point isn't STP/TGT is IP/RP in VIP/VRP or OAPs when using those. Sighting point modeling is early days so expect lots of WIP and weird stuff.

It can happen to battle damage. Bad trigger timing can cause it too but not sure about in DCS.

The dividing line looks like status 62 which is when "RDY" first comes up. If you switch NAV at 63 and RDY is not up then you get a flag on the HSI distant readout.

Ah sorry, the ones digit knob does not show a green circular arrow even when working correctly. The tens/hundreds knob does. That's because the ones digit knob also has a mouse click function and so gets the dot-with-up-down-arrows green icon instead. This also applies to the two ILS knobs, mouse wheel controls the knob and mouse left/right controls the ring. Being a combined function the green dot-with-up-down-arrow icon is used. For three of the four knobs the only way to change it via mouse is with mouse wheel. The tens/hundreds TACAN knob can be left clicked and dragged as well.

Removed mods and crash persists. Note that attached track does not go through the complete process of producing the crash. The reviewer must take control at the end and press OSB 10 to cause the crash. Replicated with any mods removed and attached log: dcs.log I have run a slow repair and still get the crash.

I don't believe the real airplane's propeller goes to 80 degrees in any case because no P-47 has a feathering propeller.