Endline

Is there anyone else that uses labels? Labels work fine in every other mission but for the ones in this campaign and since I have a small screen it's almost unplayable for me. Could it have something to do with the in-mission loading that takes place? Maybe it's a DCS bug.

Thank you both. I'll probably give it a pass then.

I'm probably missing something, but why is there no trial option for Kola? Especially since it's in EA?

I know that there are workarounds, that's not the point.

It'd be much more realistic if Jester was able to at least move the azimuth and elevation on his own when DL contacts show up and the AWG-9 won't pick them up. The player shouldn't have to direct him to look at the DL's direction and elevation. It's breaking immersion, although I get that from a technical point of view, it's probably too much to ask to implement. Maybe Jester 2 will be improved in this aspect.

Any chance for a hotfix for the stable version?

Perhaps others can offer their experiences as well but prior to 2.9 I never had trouble topping up in this particular mission (Refuel Fight Recover).

It couldn't have been empty. It's an instant action mission, which starts with the S-3 1nm ahead for the player to refuel.

Tried refuelling yesterday with the Tomcat. First the animation seemed broken as the hose looked so stiff that it resembled more a pole than a fuel hose and sometimes the probe would clip through the basket. Second the S-3 retracted the basket prematurely, way before I was close to being full and dived away. I'll try to get a track.

I have the exact same thing happening as well. As soon as I turn off the TADS screen the white flashes go away. I also own the F16 and F18 modules, which I haven't tested but I suspect it's happening with them as well. The Tomcat on the other hand is perfectly fine as far as I know, but I haven't tried using the LANTIRN so it may be also problematic. I have an AMD 6750XT on stable and I'm not using FSR or NIS. As far as I'm concerned, it's unacceptable that the devs knew about this bug and they stll pushed the problematic open beta to the stable branch. It's going to be months before the fix reaches stable users.

Apparently there was some error with the F18 on my end. It wouldn't show up in mission or in the ME. I've run a repair and it's working fine now. Please disregard this thread.

I'm currently away, so no video. I did however manage to take a look at the mission in the ME and it does list A10s instead of presumably F18s. No mods either. Isn't this a Heatblur mission? I thought there would be at least some sort of acknowledgement.

Just tried this one and surpisingly there are 4 A10s being perfectly catapulted at the mission start.

Regarding Kola, please tell me that you are considering a Tomcat mid-80s cold war gone hot scenario after Arctic Thunder. Set in the winter, giving off "Hunt for the Red October" vibes.

I was wondering if there's any news regarding the early A model? Wasn't there just the RWR left to do or am I mistaken? Everyone is focused on the Phantom release with good reason but this one seems to have gone under the radar.

After reading the thread, I got confused. Is the alternate AOA buffet in the options, the realistic one?

Stable 2.8 preparing to trap on the carrier: It doesn't seem like it's game breaking. I clicked ok and landed without issues.

I'm assuming that this still isn't fixed? Because I am seeing it in the stable 2.8 too. Also off topic but did the Forrestal get the improved longer supercarrier wake? This is currently Forrestal's wake:

Yes that's the one, 4 J-11s. It makes sense if it is bugged, since it seems impossible to get a hit.

Can anyone try the Marianas Dragon Tooth BVR instant action with the F-14A and 54As? Had two runs yesterday, launching from 37,000+ at ~1.1 Mach from a distance between 40 and 50 miles. Both I and the AI wingman went 0/8. 0/16 in total.

I have been flying almost exclusively the Tomcat in singleplayer since I got it some months ago, but it does seem like the end of the road for now. The Phoenix just isn't usable with a success hit rate of less than 10% no matter the launch conditions.

The mission starts around 32k I think. I was trying to climb too but at a very shallow angle. Maybe it justs needs more time although with 4 J-11s incoming at 40k that's in short supply.

I've been trying the F-14A BVR instant action mission in the Marianas and true enough it's not possible to go past mach 1.0 with the A (4/2/2 loadout). Which seems weird but maybe it's realistic. Could it be a bug?