J20Stronk

AFAIK Course Lines only show up in APR Landing modes, TACAN navigation and between Waypoints 1-29, which are use for navigation. Two of these can't be edited. In the case of APR approach vectors they are generated when the DTC loads airfield info. Course lines between Waypoints are just that; they just link with each other. TACAN course can be edited, but that only gets you to the broadcasting station. In the example you gave, you could set up and use OAPs. these can be edited in the UFCP using the corresponding button to access the OAP page. In there you set the offset angle, distance, and altitude (both in feet).

The real MMS switch is a 3-position switch, just like the Dogfight switch on the F-16C. Right now it behaves as if it were 3 separate buttons, however. I would like the keybinds to reflect this behavior since it doesn't make sense to push NAV while already in NAV mode. (doing so just resets the MFD pages to what they were set to last when you switched to other Master Modes. Kinda like S1 Depress - Page Reset.) Likewise during a cold start, I would imagine the plane would display the default MFD pages of the currently selected Master Mode (most likely NAV). Instead, it displays "empty" MFD pages and No Master mode on the HUD.

There's some AA modes currently missing: VS-STT SPOT WIDE-ACQ Possibly SLAVE(to sensor/TGP) and EXP, but at least I know the ones above are missing for sure.

I feel like Deka should just add these user skins as official parts of the module, and touch them up later when their modelers have more time. Heatblur did something similar with the F-14. There's a lot of really good skins out there that unfortunately not everyone will see, including your PLAAF white and fictional JASDF Kerbo, as well as the other PAF squadron skins. We've been stuck with the same 4 skins since launch, we need more variety.

That's the engine dying due to fuel starvation. It's something all engines suffer when pulling 0G or negative Gs, except for direct fuel injection ones like the DB-605 on the BF-109. Not surprised the F-16 doesn't have it modeled tbh. There's alot of systems missing in it or modeled barebones.

There doesn't appear to be a way to slave the radar to other sensors, at least not yet. I imagine the NOR button on the RDR page may have something to do with that. The A-A modes intro video Deka posted before release mentioned that the NOR button affects antenna stabilization. ATM, the NOR button is non-functional therefore I don't know what it actually does, but it might be a way to slave the radar to the TGP and other sensors.

In the next update, Mission designers will be able to restrict loadout based on what they believe is realistic and fitting to their mission / Air Force's SOP. Could you please unlock the ability to mount smoky rockets and missiles and 2x medium bombs on the inner stations, and let the MEs handle the restrictions themselves? So long as they can physically mount them there, of course. Rockets and GDJ-II19 appear to be fine, but I'm not sure if the SD-10's PF-12 rails or PL-5/C-701 P-9 rails can be mounted there.

You mean INS on the AAP? That button requires a 4-second hold to turn it off. It is like that on the real one to prevent accidental deactivation.

Not sure if it's a bug or if I'm doing something wrong, but for some reason the INS will not fully align. This is in NORM alignment, LAT/LONG were confirmed on the DED, aircraft was stationary, GPS was on, Unrestricted SATNAV in options on, etc. Yet after 8.5 minutes, the system will never reach a quality state of 6. As a result my TGP and other sensors and weapons become misaligned and do not correlate properly with each other. .trk below of a basic startup with the phenomena. F16NORMINSALIGNBUG.trk

I imagine it'd show up on the PFL (pilot fault list), accessible via the UFC.

That still doesn't answer anything; what is the, "cheat"? I've been flying and modding the JF-17 practically all the time since it released, and I never found exploits that would be considered, "cheating". (whatever that means in a Flight Simulator.) Obvious things like loadout tampering don't pass IC as they should, and there is even another layer of protection at a plugin-level that prevents you from firing weapons in MP if you do somehow manage to get a custom loadout in.

TV was removed as the real missile only has an IR seeker

Check that you have Historical Units disabled in the ME. (it's the clock icon on the bottom panel.)

This is intended behavior. The RDR will retain which targets are the HPT/SPT tracks while the HUD switches focus to the SPT. This is so the pilot and radar knows which target is their HPT at all times even after they fire on them. Also since the radar will always be scanning the HPT, you wouldn't want it to slew to a different target as it's guiding a missile.

Here's the several types of FP points used by the Thunder, and their F10 names so you can create them in game. (Note, F10 names are case sensitive.) Point 00: INS Initial Point. Used for INS alignment. Points 01-30: Navigation Waypoints (F10: WPT1 - WPT30) Used for navigation. Course lines are drawn between points on the HSD when any one of the 30 points are selected. Points 31-35: Route Points (F10: RP1 - RP5) Used by the C-802AK and CM-802AKG missiles. The missiles will use them as steerpoints and fly towards them before reaching the target. They will either fly the Route Points in ascending order or fly to a specific point and then turn to target depending how you set up the weapon. Points 36-39: Pre-Planned Points (F10: PP1 - PP4) Used by IAMs (cruise missiles, GPS bombs, etc.) to attack pre-planned targets. Point 40: SPI Point reserved for the SPI. You can select this point to display the last location of the SPI on the HUD and HSD. Points 41-49: Markpoints You can create Overfly(OFLY) and Designation(DSGT) markpoints using the MRK UFCP button. Points 50-59: Airfields Reserved points for nearby airfields. Points 50-58 are preloaded to the DTC before the mission, they cannot be edited. The airfields are loaded based on their proximity to the Navigation Waypoints set in the Mission Editor. Point 59 can be fully edited. Its coordinates are set in the DST page and approach parameters in the APR page.

That changelog hasn't been updated since the last patch was released. In fact, both the FCS AP roll and FLIR WH/BH levels were fixed before last patch dropped, but didn't make it into the build in time.

Could we expect an adjustment to the throttle response times in tomorrow's patch? At least something that makes AAR and landing less painful.

I'm gonna hijack this thread a bit to also mention that the Impact Angle (not Impact Azimuth) appears to be nonfunctional on the LS-6. They always seem to impact with a 10° dive. Likewise, the GB-6 HE does not have an Impact Angle setting, and retains the OPEN HT setting from the Cluster and SFW variants.

Basically parroting my post in the main discussion thread - that throttle curve has got to go. No way does the real Klimov have such crappy spool times. No way does it take upwards of 7 to 8 seconds to spool the engine by 5% RPM. That's the kind of spool rates you'd see on like, first gen jet engines from WWII. Not a modernized, improved engine from the 70s-90s.

The only thing bothering me is the absurdly slow spool rate of the RD-93. Is it really this slow on the real plane? It takes roughly 6-7 seconds to go from 72% RPM to 80%. And the smaller the RPM change increment, the slower the spool rate. Basically, there appears to be some really bad RPM Smoothing Curve similar to Mouse Acceleration in FPS video games. Smaller increments like 75% -> 80% have a spool rate of ~1%/sec, while 75% -> 95% has a spool rate of ~5%/sec. (Which is still really slow) This RPM curve makes it really difficult to land and AAR, or pick up speed after a dive bombing maneuver. Again, I don't know if this is correct for the DEEC to apply a really slow curve to the throttle, but I doubt anyone would use an engine that has such sluggish throttle response times. It should also be noted, the MiG-29s RD-33 spools much faster at about 8%/s to 12%/s, and it doesn't seem to have that anoying curve affecting the small throttle increments.

And now it fixed itself again... I don't even know what is with this bug... I tried disabling stuff in device_init. The last one I disabled was the SMS, then it magically fixed itself. Re-enabled it, and the bug didn't come back. I assume the SMS is the culprit, but I don't know for sure.

They accidentally broke it and didn't manage to get it in by the time last patch dropped. Already fixed internally.

Still not fixed as of OB 2.7.0.5659

Most likely the Liaoning and other PLAN assets, possibly an AI J-15.

Not a bug. When using Navigation Steerpoints (WPT 01-30) the Course Vector will point from steerpoint to steerpoint. You can see this in your screenshot, how the red line is parallel to the course line drawn between steerpoints. Likewise, the Heading on the top left indicates the heading you should fly to be on course with the flight plan. Using other steerpoints; RP, PP, MKP and SPI will have the Course Vector point directly to it.