Callsign JoNay

That might be true inside of that 20-40 nm range that is awkward for the Phoenix and it lofts basically straight up sometimes, but I don't think that's true of 40+ nm shots. Tacview-20221016-221308-DCS.zip.acmiTacview-20221016-221842-DCS.zip.acmi Here's a couple tacviews. One is a level shot at 40k, 1.2m, at 60nm. The other is a 30-deg loft at only 35k, 1.2m, 60nm. Both missiles miss, but the level shot doesn't get any closer than 3.25nm from the target. The lofted shot at least gets to within 2000 ft. Can you share some tacviews of the results you mentioned?

I don't think it's intentional, and I don't think you're right about it losing energy. See my comment on Oct 4. The missile is losing over half a mach at impact when you do apples to apples tests against the original Phoenix overhaul on Sept 2.

I don't, not at all. Even at high altitudes the missile only lofts up to 65K max. Sometimes not even 60k. It flies a relatively flat trajectory through air that is still somewhat thick. The only way to get it into the 80-90k range (right now) is to loft. You'll get a better PK% shot by lofting at 30-deg from 25k than you will with a level shot at 40k. But even then, the missile is so garbage right now at dealing with a notch that it doesn't matter in the end. If the target turns even somewhat close to a 90-deg aspect during the active/pitbull phase it's a trashed missile. Edit/add: And on top of that, we are getting jamming effects next patch so it might be extra game over for the Tomcat depending on what range we get burn through. If we get burn through at the same standard 29 nm as other 4th gens then the last advantage the Tomcat has (AWG-9) will be nullified. RIP. The Tomcat seems to exist in no man's land. Too strong for 3rd gen cold war era environments, and too weak for modern 4th gen.

Same. In fact I've been lofting all the way to 30 deg. It's the only way to get the missile into the 80-90Ks. I'm hoping for good things this patch.

ED borked the 54 lofting profile on Sept 21. It should get a little bit better if they are able to correct it in the next patch. My biggest concern is how easy it is to notch the 54 now. The missile used to hold course after getting notched and try to pick the pitbull up again, now they just scoop upwards harmlessly away from the target.

Yeah, you're right. I did a tacview and the acceleration is pretty linear all the way. No acceleration spikes when the wheels lift up at around 200kts. My bad.

Long take off roll is probably being affected by the same sticky tires that make the landing roll too short, and prevent the plane from sliding around on the deck.

One of the most common places me, and friends, experienced the hanging freeze over the last few months is the Hoggit Caucasus training server, and I don't think there are any AI F-14s there.

Hey guys, I just want to bump this again. Here's a video, (not mine), dated Sept 3 showing a comparison of the Cm47 and Cm60 after the AIM-54 Overhaul Pt2. The author does a test shot for each missile from angels 30, sub mach, on a target at 40,000 about mach 1.05. In the video the C47 lofts up to 79,000 feet and impacts the target at M1.95. The C60 lofts up to 83,000 feet and impacts the target at M1.98. I recreated the test conditions on the latest open beta today. The C47 only lofts up to 61,000 feet and impacts the target at M1.38. (Tacview attached)CM47.acmi The C60 lofts up to 66,000 feet and impacts the target at M1.52. (Tacview attached)CM60.acmi I don't see any changes in the Sept 8 or Sept 21 patch notes regarding the AIM-54 overhaul that weren't already in the Sept 2 patch notes. Something has clearly changed on my end regarding the AIM-54 launch/loft at some point after the overhaul. Is this intended? Edit: Disregard Sept 8, that was a stable update patch. Something must've happened on the 21st patch, first reported here by @WarthogOsl on Sept 23rd. https://forum.dcs.world/topic/308085-dcs-f-14-development-update-aim-54-phoenix-improvements-overhaul/?do=findComment&comment=5054796

A-10C II WARTHOG RECRUITING HAS BEEN RE-OPENED! A-10C recruiting has been closed again as of Jan 1st, 2023. https://51stvirtualfighterwing.com/ https://discord.gg/51stvfw

It does if you have VR or a head tracker and physically move your head closer or farther away from the HUD. Zooming in and out is just the DCS version of "CSI enhance".

For me it's not even about immersion, it's just better. For me to be able to just say "scan sector angels 10 at 20" or "grid center" without having to navigate the cumbersome wheel is so convenient.

I've noticed this too. Two patches ago the missile would pitch up 60+ deg and climb to 80k, sometimes even over 100k depending on the range to it's target. We were all advised by the devs to stop assisting the loft of our phoenix shots and deploy them in level attitude to prevent them from over-lofting their targets. Now I'm finding the loft trajectory to be much lower. If I'm at 40K, level flight, the C47 only climbs to 55-60k. I've actually gone back to assisting the loft again. Is this intended behavior?

P-STT is a problematic mode right now, for sure. Anything active off the rail, or anything that loses TWS support early after weapon release has a good chance of putting the Phoenix into roller coaster mode.

F-16 recruiting has been closed again. Thanks for all the interest! We are still currently recruiting for LotATC, AV-8B, F-14B, AH-64D, and other various helos. And we will be standing up squadrons for F-15E and C-130 when those modules drop into early access.

+1 here.

It doesn't. I use the keybind all the time, I just used the Jester Wheel for this video specifically so people wouldn't say "it's probably a problem with the keybind".

I don't know how long this bug has been present, but ever since the new C-model Phoenix features have been introduced, I've been strategically breaking gimbals more often and I've noticed some buggy behavior as a result. See below a video that demonstrates radar mode selection and some inconsistent behavior between the Jester wheel and doing it yourself in the RIO seat.

I meant, maybe you had it on by accident? I've RIOd for people who didn't know the engage switch alone did something, and they thought as long as they didn't flick up the ALT augmentation and pinky switch the AP REF light off, they thought AP was disengaged. I've seen guys try to AAR with the AP on because they didn't know that, and were flopping all over the place because of it. Just throwing it out there since I can't open your track and look for myself. I pilot the Tomcat even more than I RIO it, and I haven't noticed anything like what you are describing yet.

I can't open your track because it requires a mod I don't have. Sounds like your AP might be engaged?

F-16C VIPER RECRUITING HAS BEEN RE-OPENED! LIMITED SPOTS AVAILABLE. This is a very popular module, so join today, don't delay! https://51stvirtualfighterwing.com/ https://discord.gg/51stvfw

I think that's probably the most likely explanation.

Well it might not be a flight thing then. Maybe the bug can occur even with same allied individual AI fighters in close proximity. Abysmal AI™ as usual.

Gotta love that DCS bug that causes only the first guy in the flight to properly defend while the others maintain straight and level. Also, 30 nm with a Sparrow? I don't shoot outside of 7-ish!

You don't need to depress the trigger for 3 seconds. Is that in the manual? If it is, it's wrong. You just need to pull and release. The weapon just takes 3 seconds to shoot. Pay attention to the hot trigger light. If it's lit up then you can shoot. If the light goes out there is no shot available, or the WCS is in the 3-second process of shooting.