Foogle

The Liaoning can be adequately represented with a skin on the SC Kuznetsov https://www.digitalcombatsimulator.com/en/files/3314805/. Gimme a Type 075, Type 22, Type 37-II, and/or a C 14. Edit: Sorry for the necro, I guess I never looked at this thread :x

What's the footprint; will i need new mounting plates? If it's a new footprint, does Monstertech et al have the dimensions so we can get proper mounts on release?

When you lock a FTT it becomes the SPI, but if you move it out of the limits of the radar, the SPI will snap to the waypoint on the UFCP. The radar SPI will not save in WP 40, nor is there any way I have found to recover the target coordinates; this must be wrong, as any large maneuver will wipe your target point and force you to restart from the beginning.

The L-39 does the same thing, it doesn't need to be advanced to go to idle during firing. You are massively overestimating the equipment required for setting the engine to idle.

I don't mean to be rude, but you actually need to read my post. The aircraft systems automatically reduce engine power during the firing sequence, whether or not it actually ingests the exhaust.

Just like in the Mirage 2000 & L-39ZA the engine is set to idle automatically during firing by the aircraft systems. The engine is not slowing down because of rocket exhaust ingestion, it's being pre-emptively slowed to prevent flameout /if/ rocket exhaust ingestion occurs. There is no digital or smart controls on either of those aircraft/engines, so FADEC isnt required.

How are we supposed to make a skin for an aircraft that hasn't been delivered? Unless you have some mockups; I think we're going to have to wait until we get some pictures.

I distinctly remember a GCI/Ground datalink being on 198, perhaps @uboats can shed some light on it. Edit: disregard, uboats clarified that it was a dev holdover.

Yeah that's already modelled on channel 198 if I recall correctly.

Myanmar and Nigeria don't have AWACS aircraft, they don't need a Chinese datalink.

Because the Pakistani air force uses western equipment. China does not use the JF-17, it's an export only fighter. So it makes sense that the aircraft would dovetail with the existing framework of the PAF; that means Link 16 compatibility, and not whatever DL the Chinese use.

The KJ-2000 uses the redfor datalink scheme, and is not compatible with the JF-17.

Viewport adjustment is broken; You've bricked my simpit for MP. Excellent work .

Just a guess, but, the indicator may be an off the shelf part, so the maximum on the gauge is not the maximum of the system, because it's not purpose built for the aircraft.

Nope, it's an ED problem that has existed for years and nothing has been done.

Sorry, but I can't see that as being true, mainly because it prevents you from using the DLZ on the second target, and switching only one of the sensors is quite confusing. It's also odd that the radar would care which target is HPT and which is SPT, given that it can guide two missiles at two targets at the same, unless the secondary target is tracked worse, but I don't see any indication of that. Any thoughts @uboats?

That doesn't fix it, it simply causes both the HUD and radar to switch bugged/boxed targets, the mismatch still exists. Ie HUD would go from blue to red, and mfd would go from red to blue, they would still be tracking different targets.

Cant seem to get a track to generate, but here's a screenshot, the right target is bugged on the radar page, but not on the HUD, whereas the left target is the secondary track on the radar page, but is boxed on the HUD.

You'd get a tone at long range that disappears if the target was first in AB then went Mil power or lower, the second one would need a track/amci file to diagnose. I honestly haven't seen anything odd with them, and we've been flying 80s missions with the Thunder as a stand in for the F-20, so I've shot my fair share of PL-5s in the past month.

Were you head on? Or rear aspect? The PL-5 has limited front aspect performance.

In DTT if you fire only one missile, the HUD and radar page are mismatched, the HUD moves to the next target but the radar page does not. Pressing target switch (s2 left) causes both to switch targets, but they are still mismatched. Will post track and video when I get home from work.

I hope so, I've had more tail strikes in the past week than I'd like to admit.

Good eye Paging @uboats!

In all available data, and videos of simulators, the altitude is displayed to the foot, no rounding. So what we have is accurate.

Has this been fixed? Or even looked at?