Frederf

My understanding is that there are three levels of reporting on a sector channel. During the reception cycle the incomming signal charges a memory device like a capacitor. The discharge of the built up charge comes as a series of flashes and beeps. Low signal is a single flash like flash-off-off. Medium signal is flash-flash-off. High signal is flash-flash-flash. The time slots for the three events are just about long enough that if three flashes are shown then the next three flashes from the next cycle are a continuation of the same pattern. The cycles are of fixed interval but their contents vary. Again my impression is that flashes/beeps are a way of indicating different magnitudes of total signal collected over the reception window, not raw information about when or how you were swept. The average frequency of flashes would change as second or third flashes would not happen for low or medium signal sums.

Normally the '\' communication device will pick the last selected COM1 or COM2 as picked by the COM/IFF hat on the throttle. However before either radio is selected for the first time there is no last used and the '\' communication device will use both radios simultaneously which is physically impossible. This is a minor issue by itself. If one radio is being transmitted on (e.g. COM1 to ATC) and a second message is sent by the other radio (e.g. COM2) both will occur simultaneously and the first radio message will never end making further radio messages impossible. Possible solutions are to: Prevent '\' device in the air Initialize '\' device to the #1 radio Blocking or interrupting logic such that two radios cannot transmit simultaneously F16 Radio simultaneous stuck.trk

From the first track at the 3:30 mark: By releasing slew the handoff starts And the handoff fails (as expected considering the alignment) and stays in this failed state for the rest of the flight. I don't know why the parallax is so high here. When I take over the track and slew both slaved together way off axis the alignment remains very good.

I have had two AIM-9s fire on a single button press and other oddities. For example I was looking at something else and caught a wild double AIM-9 launch behavior (happens after the 4 minute mark). F-16 double AIM-9.trk

I'm looking. First thing I notice is that TGP is TV and missile is IIR which should not work as the image comparison step in the correlation may struggle or fail with the different images. The image comparison step doesn't seem to be modeled in DCS. Also I believe the MBC should automatically handle missile FOV and polarity as needed to match TGP. The second pass was going to fail because the missile was in break lock mode ever since the failed attempt on the first pass. One of the significant issues is that slewing TGP in point track mode will cause an attempted handoff simply by releasing the cursor switch. I think this is not correct behavior and reliably messes up missile attacks. I believe the correct behavior is that the system won't attempt another handoff unless TMS forward is pressed and released even if the TGP is in point track mode throughout. The big thing that Bignewy did differently than you is that after firing the first missile he took the TGP out of point track mode before slewing to the next target. This meant that when he ceased slewing no handoff was attempted until TMS forward was pressed then released. Tracks are repeated instructions into the sim that the sim is interpreting as if they are the first time. In theory tracks are deterministic since the instructions and simulation should be the same. If the simulation is different code and/or if the instructions have some inaccuracies in reproduction then the same recipe will bake a different cake. The longer the track the more small differences will diverge the results. Here's an example track showing the different behavior if point track is used while slewing with handoff enabled. Handoff point area track.trk

While there is an "equally responsible" option as set in the editor, this is inflexible. Being able to change your ignore/prompt/accept state for both control requests and join requests would be a lot of new usability even with the existing mouse-driven UI interaction. E.g. one could set one as request join: prompt and request control: ignore on the ground and then change mid mission to request join: ignore and request control: accept or other combinations. The only features I might suggest in addition would be a password that the first user can set for join requests and a prompt which does not interrupt control and times out after a few seconds without interaction. This prompt could be at the edge of screen or even audio-only.

EGI (or Doppler) should Kalman filter those velocities down quite a bit. An INS update with weight on wheels I think might zero velocity update. A pure INS machine will have velocity errors naturally. Perhaps the methods of updating those velocity corrections (EGI, Doppler, manual updates) are yet to be implemented.

It's important to make sure the radar antenna brackets the altitude of the target and you have the smallest practical scan pattern (A's and B's). RWS should perform better than TWS for initial detection. There is also two regimes of radial velocity the radar doesn't perform well at: zero radial and radial equal to the ground oncoming. There are filters associated with these Doppler frequencies.

That's an issue currently with how DCS is handling LAU-88. It's stepping through every missile and not stations like it's supposed to so you get weird results. With two missiles (LAU-117 on 3, LAU-117 on 7) this issue doesn't happen. I've never seen a case where missile will track manually but won't handoff automatically unless there was a logic issue.

Those targets look about 55nm away. Depending on what they are they just plain aren't detectable by the radar under those conditions. You should see most targets for sure at 30-40nm.

That's how PDLT works for the most part which appears to be coming in one of next few updates.

SRS bug. It won't start at 100% with SRS uninstalled. Jiggling the master volume (any change) will resynchronize. I tell people '/' key is for shouting out the window. It's not a radio so it won't work except canopy open, engine off, etc. like shouting would work. Easy comms had done a lot of harm to the understanding of how radio communications is supposed to work. Of course it's necessary to have an "in person voice" option for talking but simply not bringing up the menu and the not clear title at the top of the menu has caused so much confusion.

I find IR changing drastically when looking at different azimuths to be quite odd. If surfaces were highly reflective (ocean, glass, etc.) then I'd understand but most of terrain is specular. Looking east or north shouldn't be in general like night and day difference.

Standoff only has meaning when the question is answered, "stand off from what?" Strafe with 20mm cannon is standoff if the threat can only throw rocks back. Maverick is standoff against a tank but not an SA-5. Every weapon is and is not standoff depending on what it is pitted against. HARM: This is a complicated weapon and I don't think DCS is modeling it adequately. When sent against a position destination and the radar is emitting everything goes smoothly. Other messier conditions it's not so good. The proper hands on controls could make it easier to use. JDAM: I have found that the edge of the envelope can cause poor behavior and it is sensitive to TLE but that's not a weapon issue but a platform one. Damage-wise it's a Mk 82 so nothing specifically about the guidance is affecting that. From the heart of the envelope with good targeting the dispersion is as I expect. Maverick: The missile itself works quite well and has for years. The DCS F-16 has had lots of usability issues that make getting the darn thing tracking and off the rail way more of a pain than it otherwise needs be. I know opinion of the image quality of the IIR video is low but I think it's close to accurate to reality in some situations. JSOW: Another complicated weapon that's missing a few features. Notice the CTRL page is inaccessible. BLU-97 is under performing in DCS I think we all agree. I find the guidance logic to be decent for most situations and the warload is what it is. Anyway here is a selection of each of the above weapons employed 4 weapons against 4 targets to good effect. While improvements can be made the weapons can achieve good effects at least in ideal conditions. F-16 4xHARM Preplanned.trk F-16 4xJDAM BTR Preplanned.trk F-16 4xMav Preplanned.trk F-16 4xJSOW Preplanned.trk

There's a terrain database in this airplane that would get an elevation from a 2D position. That's why the 3 options for height data on the FCR page are BARO/RAD ALT/PR, PR stands for passive ranging or elevation data from database file. As stated, this variant doesn't have the ability to mark the HSD directly. One could make marks on the FCR while looking at the HSD ghost AG cursor and that would provide approximately this ability.

I believe this has been reported previously here:

I can't see in the video where this statement was made. What weapon was it make in reference to? It shouldn't be true of the gun for obvious reasons. AIM-9 might have an issue if it's not allowed to uncage and self-track before launch. AIM-120 does get midcourse radar help but at short ranges the missile onboard radar should make that help basically irrelevant.

From my memory of the Saitek/MadCatz/Logitech programming software the modes defaulted to "fallback" behavior which causes the child modes to inherit actions from the parent mode unless specifically different. There's a drop down selection at the top of each mode column (up to 6 columns if there are 3 modes, shifted+unshifted). That should let you pick which is the parent mode to fallback to. In short, it'll be fine and if you don't like it you can remove it without harm. If you're really worried make a backup copy of your profile file. I recommend selecting the column view from the "views" button at the top. Unless you're not talking about using the software profiler and just DCS itself then adding the mode buttons as modifiers will cause any actions not with that modifier to be ignored. You can go through and also bind those combinations to those old actions again so it works as ButtonX, ButtonX+ModifierA, ButtonX+ModifierB.

I don't know if it helps to visualize but I tried

F-18 (stored) is also 90 seconds. In reality these are maximum times for latitudes less than 70.

Should be: Throttle (Left) - OFF/IDLE Throttle (Right) - OFF/IDLE Those are defined in the \joystick\default.lua actions file for the F-5E so they should work for a generic joystick. If those aren't visible or available commands there might be an overriding device-specific .lua. My understanding of the Super Taurus throttle is that after a certain firmware update the 1 & 2 buttons are held when at the OFF position. These should be held down while the left and right handles are in the OFF position and should be bound to the actions named above.

I don't know if the DCS GBU-38s have any variable fuzing. It might depend on the dropping platform. In any case, the terminal effects of bombs on armored vehicles in DCS is an oft-discussed topic. I don't have detailed knowledge as to the realism except to know I don't know. For "fun" here is a video of a bunch of guys that received the same warhead quite close to their position without casualties. I don't know the distance and obviously there is a lot of hard, rocky planet helping them but it's close. https://www.youtube.com/watch?v=BSzBCgbicbA

There are three sight select switches in the AH-64: Pilot collective Gunner collective TEDAC All three work for me except only the up position works on the pilot collective because right (TADS) has no function in reality (pilot can't TADS), FCR is not implemented at all yet, and LINK does nothing because there's no FCR to link to or from. It is not required to take control of the flight axes to use these buttons. Only cyclic X, Y, collective, power levers, and rudder are one-at-a-time permission based. Brakes, search light, buttons, axes for your cockpit (volumes, brightness) are always enabled. Here's a track pressing SS right then SS up in order for pilot collective, copilot collective, and TEDAC.AH64 right then up SS pilot copilot tedac.trk

1. The stored alignment assumes your mission initialization position/heading for a faster alignment. It cannot be reasonably used if aligning after moving from initial position. One uses the stored knob position instead of norm and don't edit or confirm L/L on DED. 2. Yes, 90s instead of 480s assuming quality 10.

DTC, almost everything that can be set up in cockpit through UFC/MFDs can be prepared.