J20Stronk

Just Battery. You can start the plane if you connect ground power when the bug occurs.

Here's the lua files. Necessary changes are in: (materials.lua) lines: 68, 180, 217 (MFCDs_defs.lua) line: 75 (UP_L1_HSD.lua) lines: 89 - 107 Ignore the other changes. JFMAPFIX.zip PS: adjust the opacity of MFCD_IND_BLACK in materials.lua (line 68) to get the map brightness just right. I found 210 to be good enough for both day and night.

Maybe, or maybe not. The F-18's HSD map is also a bit too bright at times. I actually managed to "fix" this issue by adding a black box over the map render. It darkens the map and doesn't affect the Symbology or Icons, so the map usable both in day and night.

Actually, it allows you to change the RWR ID of an emitter to whatever you want. For example, you can change the SA-10's ID from "10T", to "BB" like on a western RWR, etc. This is just a thing for those that like to mod their modules a bit (like me). This may not actually possible on the real plane, I assume.

Something got messed up in the last patch that basically undid all of the FM tweaks for landing behavior. The plane no longer holds the nose high on its own, there is an absurdly sharp pitch moment when you raise the gear after takeoff and it also has negative ground effect when low over the runway, kind of like the bug the F-18 had a while back. I have yet to experience the landing breaking on me like you described, but I also have my grievances with it too, such as it being too bouncy when doing take off or landing rolls; it can make the nose pitch as high/low as +/-2°, which feels like something broke on the plane when it happens.

Yeah, this happens because the zoom level isn't stored and applied when you switch between Wide and Narrow FOV. Ironically the TGP, despite being the most used, is probably the least finished of the sensors and a lot of its functions appear to be simplified or not working properly: Entering Area and Point Track mode feels very simple and "arcadey", it behaves almost exactly like the FC3 Su-25T's Shkval. Manual lasing doesn't make any sense and is performed by pressing a nebulous input that isn't on the HOTAS or the MFD. And the pod lacks a masking effect and clumsily reorients itself when the target passes the lateral axis. It hasn't received many updates since the module released, but I think Deka are prioritizing it now.

I could be wrong, but the 2 circular slots also hold cartridges? At least, when you use the PAF Black Spiders livery, they have the same color as the other cartridges.

Dang, now I really want a J-7G/PG. A Fishbed at its core but it fixes some niceties of the late 21Bis, reintroducing maneuverability as a major design component and incorporating modern tech like a HUD, INS, TACAN and HMD/S.

Did you flip the Zeroizer Switch to OFF before you repaired? If not, you wiped WMMC from the plane, making it unusable.

Today's patch just brought Stable up to OB's version number. Nothing new was added or changed in the OB branch, or DCS in general.

That sounds like an bug or oversight where the game checks the IAS of the air moving on the aircraft, rather than displacement of position to determine if you are moving or not.

The J-7 and its variants are an offshoot of the even older MiG-21-F13, which is the first production model of the Fishbed and is not at all like the MiG-21bis. The J-7, depending on the version has entirely different avionics, armaments, instruments, engine and flight characteristics. (Especially if it's the newer ones with the canted wings) Almost nothing from the 21bis can be used on a potential J-7 since they are just so different in design. Yes, they're relatives; very distant relatives.

Sounds like it keeps lasing and burns itself out, even though the plane says it's not firing.

The AKG is still using a basic CM scheme and FM. It should be using the SLAM(-ER) scheme which would allow it to do a terminal maneuver, but DIS had issues implementing it. Don't know when or if they'll try again.

In the latest patch (OB DCS 2.7.10.18996), the ground effect model appears to be reversed, where instead of providing a cushion of lift it instead sinks the aircraft into the ground. This causes a very noticeable pitch-down moment when landing or taking off. Here's a .trk of me landing very light, <1000lbs of fuel and 2x PL-5. You can see when I reach a radar altitude of 20ft, the aircraft wants to sink the nose downwards and I have to counter it with more backstick pressure (Check the Control Overlay on the bottom left). You can also see the FCS trying to counter it by deflecting the elevators to a considerable degree in F2 view. JF17ReverseGroundEffectBUG.trk This same issue plagued the F-18 for months, and made landing it very rough.

Remember to have the crew chief remove the inlet covers an ladder (F8 radio menu), otherwise you will end up like that British F-35 in the Mediterranean Sea. Jokes aside, the startup sequence is still the same if it's the first start of the mission. But if you shutdown the engine and need to start it up again (after refuel, repair, etc.), you need to start with a cold crank instead of the JFS. To do a cold-crank start: 1. Starter Pump, Eng Control > On Throttle > Uncaged and Idle 2. Engine Start switch > Aft (ENG) 3. Push and hold the Ground Start button for ~5 sec. Ensure START lights up on the upper right Advisory Panel. RPM will climb to ~20% without JFS. 4. Once RPM is steady 20%-21% wait for RPM to drop back to 0%. Then, Engine Start switch > Center (START) 5. Hold Ground Start for another 5 sec until RPM and T4 begin climbing. Monitor RPM and T4 until nominal. Again, cold-crank starts should only be done if you shut down the engine and need it back up and running shortly after. Just use normal starts in most cases.

Optimal landing speed is 145-150 Kts at 9°-10° AoA. You'll only get these when you are sufficiently light so, land without stores and less than 1100lbs of fuel. You can land it a bit heavier, but not so heavy that your approach on-AoA speed is above 170kts, since that's when tires start to give and possibly burst. And like razo+r mentioned: this is not a carrier plane, you must flare and kill off your V-rate before touchdown so the gear doesn't get damaged.

That's what I said. no WMD7 = No tracking on BRMs. Clearly that's not correct. And I imagine BRMs wouldn't need a SPI to fire seeing as they're just the Type-90 rockets with a laser seeker.

Whenever the pod is masked while in point track, the SPI resets back to the Steerpoint. Dunno if that is correct behavior in the real one, but it'd be pretty odd if it is since area track doesn't do that. Also it remains ground stabilized in "INR" when that happens, so it still technically knows where it should be pointing - that leads me to believe that the SPI reset-on-mask behavior is a bug. On the rockets themselves, I don't see why the BRMs require a SPI to be near the target area. I assumed they would just be dumb fire with the only launch restrictions being roll and G limits. And it also seems like a WMD-7 MUST be loaded even if it's not lasing, else they just won't track, so that needs to be looked at.

They accidentally put the CM-400AKG scheme on the 802s

HST 1/2/4 is contact history, L/H control the speed gate. L will let you see slower targets, but may reduce radar range and/or performance. I assume it would also increase the amount of false contacts, but I don't think that is modeled yet.

The Radar FPM indicator in general is very buggy and reacts identically to the HUD FPM, which leads to errors like this. If there is wind, the FPM will shift to the side to match the HUD, but not the horizon. Any bank angle besides wings level will be incorrectly displayed on the Radar page, often below the horizon even if it's a slight climb. Wind can make this effect worse.

I take it TGT Size isn't actually implemented yet and this is just a weird bug? Or maybe ED shadow updated the scheme to try and incorporate TGT Size setting?

I'd rather ED improve the Specials menu and allow a bigger screen / more options.