Biggus

I'm talking about AI.

These crashes are harder to find on PGAW just because there's a bit more variety in the Frogfoot variants. I haven't had that pop-up before either.

I had four hits for four shots with -54Cs tonight in TWS. So long as you keep tracking them til they go active, they work fine for me. Roughly 70% of my shots connect, even down to PLM locks on hot targets down to 3nm. Generally for TWS shots, if you're going to maneuver before the missiles go active, you need to be very gentle.

I re-enabled track files while this bug is still around. Track here. Scenario: GAW server, Jester was commanded to lock one of two Su-25Ts at 21nm. So it appears that it isn't a PLM lock that is responsible, either. I asked Jester to switch to P-STT and at 8nm, I fired an AIM-7M or MH (I can't recall which). The missile appeared to track, and then the crash happened.

Keep it simple-ish. F-4J and S. Both use many of the systems that are already in the Tomcat, both shared decks with the A-6E and the A-7E, and both are useful for scenarios where we have some good opfor modules already in existence (Fishbed) or coming (Flogger and early Fulcrum). Add to that, we'd get the VTAS helmet cueing and PD radar that isn't on the land-based birds. I'll take a better radar over a gun any day of the week.

Just to reiterate, it's not weapon related. It's lock related. I am pretty sure that I'll be able to generate a crash using guns on the GAW server. It only looks like it's related to the Sparrow because that weapon needs a lock held for more than a brief moment. Haven't had a chance to run up a server to test offline but will in the next few days. Edit: I know this isn't nearly as helpful as a track, but to prove the point about a guns-kill using PLM on a Su-25T, I just recorded this a few moments ago.

Negative. These are all -7Ms, -7MHs, -9Ms and one report (that I haven't looked at the Tacview for) about a -54C. Edit: I did see a single user using a -7F and he did not experience a crash. From memory, he appeared to have an extremely short time between locking and Su-25T being out of gimbal limits.

Thanks @IronMike. I've logged it as an issue on the Hoggit Bitbucket. They're good server admins so I think they'll probably investigate at their end as well. I can't reproduce the issue in single player scenarios so far. I'll try another server, but getting that magic combination of the right AI units might be a bit hard to do. Having watched all the tacviews so far today, I've spotted one player who appeared to have the same general circumstances causing a crash except instead of using a Sparrow, he used a Sidewinder. It's almost always a hot aspect target with a pilot initiated lock, but if that lock is only maintained for a handful of seconds, the crash doesn't seem to occur. My small group of four will test it more over the next few days and I'll report back in again. I'll try to gather some actual tracks, however they end up being extremely large and often corrupt themselves immediately when I try to view them.

No mods at all. "Features" is a bit ambiguous. There's a fair bit of scripting and it is reasonably memory-intensive, but it's been like that since before the Tomcat was released.

I've just spent about 45 minutes examining the Hoggit GAW tacviews from the last few days, observing every instance where an F-14 launched a sparrow. Here is the link where you guys can download them. In nearly every instance, the crash appears when an F-14A/B engages an Su-25T with a Sparrow. I noted one instance where an F-14 launched a Sparrow at what appeared to be very close to Rmin with very high closure resulting in a victory for the Tomcat with no resultant crashes, but that was very much the exception to the rule. Quick edit: The PGAW server does not seem to have the same issues, but it apparently also uses other Su-25 variants and there are not nearly as many players flying there.

That's interesting. That's where I'm experiencing the crashes too. Edit: It seems to be repeatable with reasonable reliability. At least 50% since the hotfix for me. Steps: 1. Join Hoggit GAW, arm up and launch from the boat (haven't tried from land yet). 2. Engage enemy Su-25T with a pilot initiated lock. 3. Fire missile at Su-25T.

Mine are mostly as expected. There are some that fail immediately on launching, but it's not a majority of the shots I take with either the 7M or the 7MH.

Hey guys, Quick bug report. Game crashing when engaging an Su-25 WVR with STT tracks initiated by the pilot. A friend mentioned experiencing it a couple of times since the patch and I've just experienced i myself. I don't have a track to upload, however I've attached my logfile. There's a small thread with other users on r/hoggit mentioning crashes that sound nearly identical. Thanks in advance for looking into it. dcs.log

For me it was an issue with my install. Repairing didn't help, I needed to do a full wipe and reinstall. But that was a long time ago.

Just to clarify, SRS will make the ICS work with the other human crew member in your cockpit in addition to the two radios.

Adding my voice to those requesting a bump in brightness.

Just bumping this one because it's an ongoing issue. I regularly have Jester call 'buddy' on hostiles. Seems to be mostly when locking up F-5Es, although I have had it with some other aircraft.

Same way you'd do it in a Cessna or a Hercules. You want to descend 300ft per nautical mile from the threshold. Or take your ground speed, halve it and add a zero, and that's roughly your descent rate for a 3 degree GS. Get an idea of what "right" looks like, so you can spend more time looking out the window than down at the altimeter or VSI. Wind and traffic require more attention. Edit because I've reread the original post and I'm not sure that I've been terribly helpful to you so far, so I'm going to give you a suggestion that might help you find that sweet spot for not falling out of the sky or ballooning into space. Set yourself up a mission with an empty plane and say half a load of fuel at 5000ft, 25nm away from and directly lined up with a runway at 250kn. When you load in, do what you need to do to get on-speed. Brakes out, gear down, flaps down at 200kn, DLC. Trim it to be close to hands off. Nose will probably be around 10-12 degree above the horizon. You want to be in this state at around 17nm to intercept the G/S. But you've got enough height and distance that you can experiment with finding the right range of throttle to use. It'll give you more of a feel. Hopefully this helps.

I've noticed this and just assumed it was how it was meant to be. It has a huge amount of thrust at very low fuel flows above a certain point compared with the B, and the throttle is much less linear. A very short range of travel seems to go from 1500pph to 4500pph.

I certainly use DLC more on the A than the B. I use a smaller range of throttle at far lower fuel flows I do in the B. I haven't found a sweet spot and I suspect that environmental factors like gusting winds probably make a set-and-forget throttle position impossible IRL. As for visuals, I do like to have the needles on the VDI to get me in the ballpark. I also raise my head position so I can see the yaw string. Then it's just lineup, AoA and meatball.

I don't suppose ED would be willing to maybe let a hotfix happen a little earlier than the 16th of December?

I'm seeing similar seemingly random changes in performance from day to day, but with both Tomcats. I'm suspicious that this is an ED problem rather than an HB one.

It's happening for me, too. It raises the question of what else doesn't work correctly on the Supercarrier. The speed callouts from the LSO seem to be broken for both Tomcats, so I would assume that the LSO grading is not accurate. I'm not convinced the ball is where it should be, but ICLS seems to me to be pretty close.

These are beautiful. Thank you very much for taking the time to make and share them!

Jester menu has those instructions.