Hofftari

Ah, I wasn't aware of the exact function of that hatch, but in any case, the hatch is still stuck in open position. And I have no mods installed.

When cold starting the Viper, there is a hatch that is usually opened when you fire the gun and only when you fire the gun, but this is both open from a cold start (like all the other hatches), but this one will stay opened until you activate Dogfight-mode with master arm on (it doesn't close if master arm is off and you switch to DF-mode or if you switch to DF-mode with master arm while weight-on-wheels). After getting up in the air and doing this procedure of going DF-mode with master arm on, the hatch will behave correctly, but never before that. I have attached a track where I demonstrate this, both on the ground and after takeoff. F-16 spent shell hatch bug.trk

Hey, I am curious about this configuration of the GBU-24. Currently we have the GBU-24A/B which is a BLU-109 2000lbs penetrator bomb with the GBU-24 guidance units attached to it. There is also the GBU-24/B version which has the regular MK-84 warhead instead of the penetrator. Is this something planned for the future?

For AAR DCS doesn't care if you open the refuel hatch 5 seconds or 5 minutes prior to starting the refuelling process no matter your external tank configuration. It will fill it up to your maximum capacity no matter what.

Yes, that's why I suggested an "extra cold" feature for all aircrafts so both more casual players and more serious ones have a good time.

You do realise this is still a virtual game/simulator and not a real airplane?

Or maybe add a new state > "Extra cold" , where all switches that you listed are in the off position. Same goes for the A-10 for example. Generators, boost pumps etc are all turned on in a cold A-10.

Minor thing, but my eyes caught this as the glass was reflecting some light. The cover glass is cut short a bit before the middle of the trim gauge.

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?