TobiasA

That's true!

The bad thing is that you can't feel G forces in a simulation so it is harder to keep the limits...

There is still room for improvement but a few patches ago you could not see anything at all so I appreciate the direction in which we are heading.

Thank you for that!

The FLCS in the F-16 does NOT prevent over-G, it limits AOA to prevent departure. CAT III is anything outside of a pure A-A loadout, so as soon as you carry A/G ammunition or a tank it is a CAT III.

The pitch override does give more elevator deflection in the NEGATIVE direction so you can get out of a deep stall. You would gain nothing but a probable departure from controlled flight.

I agree that my assumptions about a sign error just canceled out the map stretch error, it looks like the compass is showing true north instead of the magnetic north at least on parts of the map. If I set it to 0 near Vaziano I am going true NSEW, with a rotation of the map stretch error.

Yes, but the heading tape should only be off by the amount of the "map stretch error" and not by the magnetic deviation. Which means it should display 082 or something like that. Because the heading tape (and the heading indication of other planes and the HSI as well) is corrected for magnetic deviation via the MAGV page (or other input devices in other planes).

As an addition: I know the issue of converting spherical map data to a flat map, I was part of a terrain development team on another sim before it had three letters. That is not the issue here, the issue is that I am more accurate without magnetic correction than with it in man cases. And even with spherical errors, the north does match in the middle of the map. Sorry if I used a wrong approach to it.

I am talking about the heading tape after the magnetic correction being 15 degrees off.

I do agree that the Tacview globe and the flat DCS map do differ, but it is a little too small to explain a 14 degree error.

It is exactly the same in the middle of the map. The ruler is about 4-5° off in the main area, that is probably due to the conversion flat - round. Also, on the edge of the map, you will always have a slight deviation due to that. The north "opens up" so to say, so lets just fly north in the middle of the map. The start heading is 000, and it will also show TRK 360 on the "TacView globe" in the middle of the map. As soon as you correct your course to go north, you go about 7° off. In the middle of the map, I go north if I enter a magnetic deviation of exactly 0.

Hi, the FPM already shows the wind compensated flightpath. The tadpole should point at the steerpoint. See the video at 10:59. You can clearly see the crosswind component, but the tadpole is on the steerpoint, FPM, tadpole and steerpoint align and you are flying towards the steerpoint. If you recreate this in DCS, it looks different. Video: DCS: I think you can see what I mean- where the tadpole is in the HUD video and where it is in DCS. Apart from that, it is a pretty close representation, and the amount of work that has gone into that is outstanding. Thanks a lot!

Well yes but not 14 degrees.

Edit: Well, it even seems to be checkable by using the ruler in the F10 map vs. the cockpit indications. Then, the magnetic compass will show the heading on the map (the one of the ruler). I think (just a wild guess) that the sign of the magnetic deviation is the other way around. Because when I enter a magnetic deviation of W06.8 instead of E06.8 I'll head straight east when flying 090.

On the caucasus map, the heading tape and HSI are off by about 14-16°. On the marianas, you fly straight east or west (90 or 270°) and the latitude does not change. In the caucasus, you fly the same course, but the latitude does change and TacView shows that you fly or heading of about 14 degrees more. Radials on the HSI are also affected. Wind is not so much an issue in the free flight missions in which I tested the behavior. We noticed when someone in our squad invited us for a navigation training and l got a bit curious as to why I flew about 15 degrees off the desired radial. You have to fly heading ~75 in the caucasus to go east. It also does not happen in Syria. It is however related to the theater, I think, since the error is about the same in the Viggen... Feel free to move it. Tracks and TacViews included, the TacView in the Viggen was the usual "spawning with heading 0, then turn to 090" and you can see the initial heading is already off. It is just easier to see in the F-16 when you look at the INS page. heading_tape_caucasus.trk heading_tape_caucasus.acmi heading_tape_marianas.acmi heading_tape_marianas.trk caucasus_test_Viggen.zip.acmi

This happens when you fly through strong crosswind- or the INS is faulty. I'll assume the INS is alright. You might center the pitch ladder at any time by selecting DRIFT C/O underneath the ICP (that switch below the "numpad", underneath the "0 M/SEL" button). This will cut off the wind part of the FPM. However this is not so wise if you intent to use CCRP bombing. But for general navigation it will work fine.

Well I personally pick up units (warm things) faster now. The pod we currently have does not excel in terms of picture quality either way, I think the sniper pod might have a better quality. But at least it is IR now.

Just a thread to appreciate the work on the TGP. For the first time, the F-16 is a capable night striker. You can actually find units on the TGP. Might not be perfect and requires a little manual adjustment on the gain, but that is a big step forward from the pitch black image we had before. You can see ground details, you can see cars on the road, you can see the heat from several systems spreading on the ground in bright sunshine, you can even see the heat from a fire:It is now IR and not just a filter on top of a TV image. And I even didn't read anything in the patch notes. Did I miss this some updates before? This means you can now fly AG sorties at night. It is awesome! Thanks to the team!

Well, this is a game after all so tactics may differ from real life. I had one guy blasting in on a two Gepards at 1000k in the F-16. I know the Gepard, he wouldn't have survived IRL but it is perfectly fine in DCS if the units are not that skilled. It is as realisitic as you make it.

Problem solved. Thanks a lot!

Thanks! I got a RWR indication and launch warning. Indications on both the RWR and the HAD, the HARM did hit. Somehow my text in the previous message got dropped when I inserted the picture, I added that again now. Thanks a lot! Tacview-20211121-102051-DCS-SAM test.zip.acmi

Edit: I have no clue what happened here, my text is gone so I am rewriting it and hope it stays this time. The HTS does not detect the Roland ADS. Even if you add it in the threat table (which I did), it does not show up in the HAD: This picture was taken about a second before it fired on me- I locked the Roland in HAS but the HTS stays empty. It won't ever detect the system. If I have to add the threat code manually to the HTS, feel free to move this out of the bug section. I have to add that the HTS is awesome, and its implementation is better than I expected- bugs may be there, but those are gonna be fixed. Thanks a lot for that! HTS_Roland.trk SAM test.miz

He nowhere mentioned the range of the 16, and did not mention which radar version he referred to in the 16 (just that it is the 68, not which version of it)- and which version of the hornet. ED has at least one SME having flown both the 16 and the 18- which is also the author of the article that you linked- so I would expect that ED uses that source. Radar and stuff is highly classified though. The F-15 radar range discussion would belong into the F-15 subforum. I think the F-15 is underperforming currently.

And this is based on which technical evidence? The problem here is probably the F-15's radar underperforming, the detection range of the F-16 matches what is publically available about the AN/APG-68 V5.