Ogata_Rina

Please check with your team members and SMEs. Certainly this isn't normal for normal airplanes.

Near at the end it just enters a violent oscillation that I have to kick rudder again to exit it. And it's not documented on haf cj50 flight characteristics, so guess it's incorrect?

Fuel is at about 2500lbs one cheek station loaded TGP, other pylons are empty. This can be induced by kicking rudder left and right at a specific frequency, looks like the damping coefficient is far off. Track: yawf16.trk

Thanks! Not meant to do that but 18 radar issue has been really frustrating after this long time. Hoping for good news.

Easiest way to test: 1. Set up any target, preferably hot, acquire STT lock. 2. Keep your target NOT at your radar centerline, preferably about 45 degrees offset left or right 3. Roll, fast, make sure you're not in transonic region where the roll rate is limited (around .7 to .8 mach works the best) 4. Radar contact goes into MEM mode. After 8 seconds, the default age out time for STT, target breaks lock. I know you guys dont bother testing yourself so here's a track: fa18breaklock.trk

Ground is way to bright in this situation

as titled MSP page to check over G and other FCS failure?

EM diagram is available for viper and tomcat; for viper in that greek f16 block 50's supplement you can find em diagram for almost all configs you can think of. The funny thing is in tomcat's natops performance supplement EM diagram is readily available, but the hornet's natops performance supplement (either ABCD or EF) does not mention em diagram at all. Yes from the viper manual it's a tremendous power monster as seen not only from PS=0 curve, but confirmed from numerous real viper pilots, like mover, or the people who fought against vipers; why we dcs players are so obsessed with it, is there is no available em diagram for hornet to validate. There are people who compares public available f16 and f14 em diagrams line by line, and report to developers where it's underpowered, overpowered, etc. For f18, there isn't such available data, and therefore there has been such a huge controversy on hornet fm. Yes I know we have this... but 1. it's painful to read 2. still does not mention sustained turn rate https://drive.google.com/file/d/1B37AYW5VAuQo6Uc61GCrhocxV0keHeNM/view?usp=sharing

Condition: turn on countermeasures, set man 1, master arm on, dispense (whatever program you have), master arm safe, dispense track: test yourself

At 5:10 you can see the TDC box "scrolls" from 80miles to 40 miles.

Video and full track is attached Video: https://drive.google.com/file/d/1eSUJ68PMZhCwVf5V3slsi4Ggm1Zrz3sE/view?usp=sharing track: https://drive.google.com/file/d/13U_C1g-2oEGsBaHpROHxaW7dOiXwIRr4/view?usp=sharing Server: growling sidewinder 10700k+RTX3080+Rift S I record the video from track, so because of the delay it shows that missile is off the rail after switching to 9X. I can 100% confirm that is indeed an amraam not a 9X. Thanks.

AI now seems to start evade (like notch and dive or go cold) as aim54 approach 20-15nm. TWS launch, target size normal, radar contact all the way. Tacview attached. https://drive.google.com/file/d/1HfBDIsCYb3QBn0V8W513EpiE0WVZZT7K/view?usp=sharing https://drive.google.com/file/d/1U_clwpLFj5n1FGvX4ndILnGHRV6uzaTK/view?usp=sharing

The livery is indeed in F14A livery list Phoenix now pitbulls according to target size as expected, and so does the blinking TTI. Well done! Also noted that AI will respond to pitbull aim54 much sooner than indicated pitbull time, but now if the contact is lost at the last moment before missile goes active, the missile can still go active and find the target, assuming it is actually looking for the held track by awg9. Only tested in singleplayer tho, the game refuses to log in my account so no luck on MP yet. I'm not sure if this pitbull-by-range is realistic or just a temporary solution, but if it works (so far it works fine) and at least provides a pitbull indication on tid, id take it

test condition: caucasus, f14A free flight (QS), jettisoned all store, climbed to 40000 and engaged auto pilot. Started from subsonic, it takes very very very very very long to reach mach one.

Version: Steam open beta Server: Growling Sidewinder open conflict Map: Caucasus Additional info: The blue awacs was down, so I was manually IFFing "bogeys" on link 16, and as the video shows, the scan line in TWS froze as I moved my cursor past a certain area on radar display. This happened before with awacs up, but this is the only one that I have clipped. THIS IS VERY DISTURBING IN COMBAT, PLEASE FIX IT AS SOON AS POSSIBLE. THANK YOU. Video clip: https://drive.google.com/file/d/1Girb5Q2cD_JwyRIbLiWTPARj5zDIMl6-/view?usp=sharing

In the campaign, first I STTed the bandit mig23. After TCS-ID I told jester to switch back to TWS, and launched a phoenix in TWS. Right after the launch, this happens: Jester started spamming the RWS key and the phoenix did not receive any kind of mid-term guidance and flew straight to the bandit, while did NOT go active. Attached is the video https://drive.google.com/file/d/1sSTJmNJ0oj2IPxLIGq72x_eCv7MPXdPt/view?usp=sharing

Unfortunately anything related to in-service Chinese jet is classified. Yes, including the cockpit of a J11B.

Despite the change, excellent AI SU25T will still completely trash every aim54 launched at it almost every time (tested three runs so far), while 120 is guaranteed hit. I do feel like the notch resistance is what makes current AIM54 almost useless against AI target.