Hofftari

Because paid campains have scripts and stuff that might interfere with something, a clean mission you've created for the bug report purpose works best and has no unknown variables that can interfere with the bug. You clearly have no idea how software development works, so don't go all dunning-kruger and be rude because you can't follow simple directions.

There doesn't seem to be any publicly available source that explicitly specifies this, but the C-1 seems to have different guidance systems and Link16 capabilities that only the Navy employs while the other variants A/A-1/C only differ in their payload while the rest of the system is similar.

They list A, A-1, C all within the same section and then have another secion for the C-1 where only F/A-18 and F-35C are specified as the users for that one. If the F-16 only used the A-variant they would separate the A, A-1 and C as well.

This is not correct. The C-1 is the navy exclusive. The AGM-154C is used on the Block 50 Viper: https://www.navy.mil/Resources/Fact-Files/Display-FactFiles/Article/2166748/agm-154-joint-standoff-weapon-jsow/

Well you kind of did, by saying "with the HTS pod you can fire your HARM off-bore", but I digress.

You don't need HTS pod to fire off-bore. EOM POS and RUK modes both give you that ability as well.

@BIGNEWY any takeaways on this?

Time to kick it up a notch. Here's a 450 knots military overhead break, cockpit view followed by an outside view

Here is a quick track file I put together. I did some profile changes on multiple profiles, yet every time I dropped one GBU-24 all my profile settings were reset to the default 4NM cue range and -30 release angle. GBU-24 profiles.trk

I've had this issue for a while. I don't know if it's an undiscovered bug or something that I'm doing wrong. The GBU-24 can have 4 profiles with different settings, yet when I change any of the settings for that profile, as soon as I drop one GBU-24, the profile gets reset to the initial values it had, everything from release angle to cue range.

@Lord Vader where you able to reproduce this? Like I said, it works for me as well if I do free flight instant action, but when I start a singleplayer mission or go to a multiplayer server, the game freezes when I do this.

Thought that my old mission might have something that is broken, so I created a new mission from scratch on the editor and added a couple of AI planes so I could select them via the HSD. Did the same thing, selected one plane, zoomed in to EXP1 and then pressed tms right. Instant freeze. I've attached the mission that I created. hsd-fov-crash.miz

I tried it with the Free Flight instant action, and it works without issues there. But when I run my own "basic" mission on where I have just added some airplanes, tankers, awacs and other fairly basic stuff, my game freezes when I try this. I have repaired my game and it didn't help.

This occured to me at first on a multiplayer server, but I also managed to reproduce it on a singleplayer mission. Select HSD as SOI Hover over any contact and select it with TMS up Use FoV select button to zoom in on HSD Press TMS right to cycle to next contact Game freezes dcs.log

Maybe related to this, but I noticed while taxiing that whenever I turn the plane, the ailerons and horizontal stabilizers starts twitching, both going full roll deflection.

The point still stands, that the way the F-16 has been changed concerning the JDAM deployment has been with this thesis: So if I understand this correctly; currently in the game no GPS guidance can affect the JDAM until after it has had a 30 second TOF, while the .edu links above state that GPS guidance is activated 3 seconds after a drop, blending it in with the INS data, and instead after 28 seconds does it fully rely on GPS data with INS data being no factor anymore. With the Litening pod shuffling around on the F-16 in its current state, not being able to stay on one fixed point anymore, the F-16 in its current state is broken when it comes to guided munitions.

An excerpt from the source that @Sinclair_76 posted: Where does the 30 second activation come into play here @Lord Vader?

I'm sorry, but how is this "working as intended"? The JDAMs are basically broken on the F-16 now. Is this really how the F-16 should work with GPS weapons?

As it wasn't on-topic on the other thread about the TGP slew and HAD, I'll create a thread of my own instead. After the latest patch I've noticed that the TGP sometimes can't stay stationary on one coordinate (i.e even the coordinates in the top left corner of the TGP are slowly changing). I have double-checked that my slew controls are perfectly centered, and even so, I can observe this while the TGP is locked in point-track. From my observations this "drift" always happens in the same direction as the aircraft is moving, so if I am moving straight against the target, the TGP will drift further away on the ground, and if I am traveling towards the left in relation to where my TGP is pointing, the TGP will drift in the same direction. I have even tried saving markpoints with the TGP, flown around a bit and then cycled through the markpoints and making sure I'm doing Cursor Zero on the TGP, and I can observe that the TGP suddenly points way off the markpoints that I had placed. I have noticed this complaint from other players on multiplayer servers, so I'm not the only one experiencing this. Attaching a track-file to this post demonstrating this. F-16C TGP-bug 2.trk

Hi, I can share a track of this behaviour since I noticed it too and thought to save it for a bug report, but seeing as there is a topic about this I can attach it in here. From what I've noticed, the TGP drifts in some way related to the aspect between your aircraft and the markpoint/steerpoint. I.e if your nose is pointing towards the right of the steerpoint, the TGP drifts towards the right; If your nose is pointing upwards, then the TGP drifts upwards, etc. I have demonstrated that too in my saved track. It seems also like the saved markpoints suffer from this too, so if you save a markpoint, do some maneuvers and then do a CZ on your saved markpoint, the TGP suddenly points to another coordinate, sometimes 10-20 meters off from your markpoint. F-16C TGP-bug 2.trk

This is currently broken from what I can tell. If I have an AIM-120 (B or C) I can't select BORE on the SMS page for AIM-120. The OSB button for Slave/Bore doesn't toggle between these modes and only Slave is selected. I've even tried doing the training mission for AIM-120C on the F-16 and the part where it teaches you about this mode isn't possible to do anymore. I've double-checked with the stable version, and the Bore-mode is selectable on that version.