TobiasA

Yet we do not have velocity search or the long range modes. The radar range is not that much of an advantage since you can't engage anything above 30nm either way and we have Link 16 so if it wasn't on the radar it would be on datalink. But we don't have jamming indicators and can't use HOJ yet so I would be more than happy to trade a bit of radar range for full functionality. What is possibly wrong is the stores drag. But once you drop the tanks, high altitude speed is pretty much according to the book as long as you do not turn, because the lift coefficient is off. Saying that the F-16 is overperformance in total is not right, it is slightly better as it should in a very specific area while being a lot worse in all others.

Tbh the only areas in which it is overperforming is the fact that there are no G and Vne damage models and the radar range is slightly too high. It will perform a lot better once basic functionality and the Fm fixes are finally done.

So it's the real F-16 or the DCS F-16 as it will be one day, and I hooked all of them. I'm an honest man.

The real F-16, the DCS F-16 as it is now or the DCS F-16 is it is expected to be?

I don't find it anymore, but various numbers exist and without CFT's it is difficult to ever achieve this value.

Yes, however I looked in the german one at first. I don't have chucks guide for the F-16.

I stand corrected: JDAM's don't exist in the GERMAN manual. Picked that one by accident. They do exist in the english one, the translation is just not there yet (WIP). Thanks!

JDAM's don't exist in the manual.

Another test, and I lased each target before I dropped, and it resulted in a solid 4 out of 4 hit strike. I closely watched the impact positions and they were spot-on. Also, I noticed that the TGP in fact updates the position, and until this morning, I did not know that the TGP actually uses the laser as a range finder to update the position. It makes perfect sense. I was already asking myself how the TGP gets the position, so I tried to be as steep as possible when dropping to minimize angular errors. Of course it does not matter on LGB's since you lase either way. A point track on the BMP is perfectly fine, no need to go for the wheels. Would be cool if JDAM's would exist in the manual, however, this is WIP and I understand that the feature comes first and the documentation second. For me, the issue is solved as of now thanks to Frederf, however @greenmamba created the thread and could mark it either as solved or write back if the problem still exists. Thanks!

So that means that the issue is that there was no laser rangefinding used? That would actually make sense. What I meant with comparison to the GBU-12: If the TGP would point to the wrong point on the ground due to looking "through the BMP" my LGBs would miss by the same amount because as I circle around the target, I would see the lateral offset effectively lasing the wrong spot if I do not correct manually. I will try if lasing the target solves the problem. Thanks for the advice and for actually watching the track!

Again, this is the point track jumping on the BMP. And it is not 38ft away unless the BMP is 40 ft high. And this does never happen with GBU 12. You didn't even watch the track.

Well I looked on top of the BMP in steep angle so how am I supposed to look behind it? TGP image on pickle: That's on his turret, not 38ft behind him so it is not the issue here.

Would have to check numerous manuals, it also differs between blocks. Don't have one right at the moment, sorry. I think it is stated in the HAF manuals.

Besides the other tips: Map the keypad of your keyboard with a modifier to the ICP. Mine is CTRL + keypad numbers and enter, I am pretty fast now. I have no idea if this is preset, but it is very helpful.

So I was finally able to reproduce it with a track.... You mean like this: Was the first JDAM out of a Salvo, and it did hit long so it failed to destroy the vehicle. It then misses by 38ft and before the vehicle moves: LGB's are fine, I rarely miss something with LGB's so it's not me and my TGP. @greenmamba @bradboom Is that your issue as well? @BN or 9L: Hope that helps, if I'm doing something wrong let me know. Attached the mission as well, it is pretty simple although I should try it with static targets since everybody moves when the first JDAM strikes. It doesn't matter in this track though because it is the first JDAM that fails, the other three are pretty much on spot (if they had not moved, they would have hit). Tacview-20210619-145017-DCS-AG_training.zip.acmi F-16_JDAM_hit_long.trk AG_training.miz

F-16_autopilot_crosswind.trk This is a track with a simple autopilot engagement during crosswind. The autopilot does not compensate for crosswind, and I think this is wrong since the vertical axis depends on the FPM but the horizontal does not, instead it points the nose to where the waypoint is. The tadpole does not show to the waypoint but to a point somewhere else which is affected by wind, which is wrong, and then the autopilot follows the wrong tadpole.

It seems to happen when you aim high on a vehicle, I guess. Always go for the wheels. Edit: I found my mistake which caused the TGP to drop lock- the GBU-12 were in CCIP mode which then moved the TGP when I switched to them. Correct behaviour. I can not reproduce the issue of JDAM's falling short or long in PRE, however, the ground units move away after the first unit gets hit and you must aim for the wheels. Track is attached, breakfast time is over. If you can reproduce the issue, please post another track since I am not really sure about my results. Tacview-20210618-091018-DCS-AG_training.zip.acmi F-16_JDAM_miss.trk

Yes, kind of. It is paired with a tendency of the TGP to drop lock when switching between JDAMs and LGBs which I need to investigate a little more. I need a track for this, but I noticed it in a multiplayer mission so I need to recreate it and see what happens.

What do you have mapped as speedbrake command? I have two buttons mapped (to be exact, the same button but shifted), on to FWD and one to AFT/Extend (Momentarily). When I have the gear out, the boards go back to 43 degree unless I command fully open, then they extend fully as long as I hold the button or weight is on the nose wheel.

A recommended read is "The Hunter Killers" also by Dan Hampton which covers the development of the wild weasels if you are interested in the topic.

The TGP was in area or point track when he went to VIS. AFAIK this behavior is correct. Since the TGP is tracking something it doesn't get slewed to the SPI. Just wondering- did my previous comment get deleted (if yes, why) or did I forget to actually press "send"?

Yes I tried that but couldn't figure out how to edit presets and I found the other editor easier so I switched over to the one I posted the screenshot of. Because to be honest the ingame editor drove me nuts, I just wanted to hack in the settings in and those sliders are... meh. I really like DICE and automatic restore and stuff, but I could not get used to the ingame editor. I mean even editing the lua file as such is twice as fast as that slider magic which basically is scaled like "take it all or leave it" and my mouse isn't sensitive enough for the "clicky clicky" in the DCS menu. I see you are the editor of both, is there a chance I can use DICE and edit the programs with the DCS CMS Editor? Because that would be perfect. Thanks a lot for the awesome work with those, I am so happy I don't need to copy all that stuff around with a batch file or stuff.

There is none. There is a maximum takeoff weight of 42300 lbs which is the maximum takeoff and landing weight.

I did a formation takeoff with an F5 in the Viggen, me being in the Viggen. The F5 had to carry drop tanks and I had to throttle back to 80% to not overtake it... LOL I don't have the F5. I think it is a beautiful plane, but I can't fly so many planes. I know the F-16 by heart, can fly the Viggen quite well but don't know all the systems, am a mediocre helicopter pilot who is waiting for the Apache, have the Tomcat which I don't fly often since I'm lacking a human partner at the moment (but I love it) and fly MiG-29 / Su-25T which aren't that complicated. I feel like I can't learn so many planes and bought maps instead. Looking towards the AV-8B or the Mirage, but I fear my head explodes if I do since I still don't really master the Viggen and haven't learned the Tomcat in every detail yet. It would have a bad taste buying another plane when I still have 2 other to master and then buy the Apache. The key in the F-16 is to be easy on the throttle and know when to go full burner and when to keep it at an easy speed of Mach 0.8. It's like the Viggen- raw power if you want it, the sound barrier is a miracle, but if you do, the fuel flow is insane. I still want to see the fuel pump of the 129 engine before I die. Well as for the programs... So all programs have a Salvo interval of 3 seconds, and the burst interval is usually 0.75. Unless I am defending against IR missiles, then flares have 0.5. The panic program is a mix, with 4x2 chaff and flares in rapid sequences. All programs run about the same time with chaffs and flares. I have not yet found out if flares in a higher interval in the missiles end-game have a higher chance for success, but even in the Su-25T i use a similar "program" but pressing insert / delete keys and it works quite well. Pop three of a kind, wait a few seconds, pop another three. However, in the FC3 planes I tend to panic out in endgame especially in the Su-25T where kinetic defense of a missile is as possible as a wheelchair entering earth orbit and just blast away all I've got. It's a rule-of-the-thumb thing, but it conserves countermeasures while still spanning the most critical seconds during a popup or when going through the vertical during entering a kinetic defense (I always chaff / flare on my way during the Split-S if things get really tight). I usually have program 4 preselected, in dogfights you can go #2 prior of the merge and use the panic button for any ARH or SARH launches if someone should have run out of heaters. So 1 + 2 are missile defense, 3 and 4 are preemptive and the panic button is a smaller sequence that gives you time to select the correct program. If you still live. CMDS_ALE47.lua I am still thankful for AAA using tracer ammo, because tracers work both ways.

True, but it is the case on many aircraft and not a bad habit to have. It is mainly due to the ground effect nowadays, but I find overall handling easier with the boards out. If you have the boards out, it is easier to maintain AOA on a light aircraft that doesn't brake well otherwise.