Anyone else find the "444" mission ridiculous?

[Phileosophos]

I think it's the fifth mission of the campaign, and I think it's called "444". It's the first one in which SPOILER ALERT! you're a convicted bad guy and you're sent up with the rest of the scoundrels. You're supposed to shoot down bombers.

My beef with the mission is two-fold. First, I'm under CONSTANT missile lock from start to finish. And I mean START TO FINISH. Like, I've just taken off from the air field, there are no bad guys around yet, and I am under constant missile lock and having to dodge to avoid getting blown out of the sky. How does that make ANY sense when there are no enemies in the area and all the friendlies are weapons disabled?!

Second, no matter how fast I take down the bombers, despite constantly dodging like a ♥♥♥♥ing mad weevil rolling himself sick, I get a "mission failed" message a few minutes into the mission. Nothing seems to make any difference, so I'm obviously missing something.

Thoughts?

[Phileosophos]

引用自 Jonathan J. O'Neill：

Do you have a HOTAS and/or other controller plugged in that may be competing with input?

I do have a HOTAS plugged in, but I've had all of that plugged in through all the missions and have never before seen the can't-take-off issue. It went away after a reboot, though, so I'm thinking it was just something funky. I'll post again if it happens again.

[Phileosophos]

引用自 Orion：

If you're using Logitech, run the program as Administrator; problem solves itself when just launching the software from the taskbar, let alone a clean launch as admin. I only had the "couldnt takeoff" problem when it was minimized in the tray; opening it making it load the configuration did it. If you're using something else; apply the same logic.

Anyway, this is one of the easiest missions ever, haven't had this problem whatsoever in regard to locks let alone constant locks or locks supposedly on takeoff.

Honestly most problems with games are usually due to lack of user knowledge; you're on a PC, expect to troubleshoot and have the knowledge to troubleshoot things, it's not a console. There's so many configurations of hardware/software that can cause issues, so you should sit down, dont angrily type, dont lose your temper; troubleshoot and fix the issue. It's an easy game for just about anyone that's played one of these games before.

I'm not sure what software I'd try running as Administrator. I'm using an Xbox One Wired controller. It's about as stock as it gets, being a Microsoft controller plugged into a Microsoft operating system. It shows as working properly and calibrated in the USB game controllers setup screen FWIW.

As to your comments about the PC, I shouldn't have to deal with garbage just because it's a PC title. I've been doing that crap for too long anyway. I still remember fiddling endlessly with QEMM 386 to free up enough DOS memory to run Darklands back in the day. By now it should just work.

I do have access to the game on my Xbox One X, however, so now I'm curious to see if the mission is the same there. I'm going to have to give that a go and see if it's any different.

[K-S43]

I've had this a few times. And yes, its very annoying. I've seen it on 444, Long day, Pipeline Destruction, Bunker Buster, and Cape Rainy Assault on Ace, but at the time, I just figured it was some weird part of the scaling, only realizing it wasn't after replaying them. I would spend the entire mission watching as Missiles would come from just off my mini map. When I expanded it, I could not see where they were fired from.
As for the Cant-take-off bug, I experienced that one on the first mission when I tried to play through Steam Link. I can say that if you go 3rd person, you can see all your flight surfaces adjusting according to your input, the plane just doesn't respond to it at all.

[Phileosophos]

引用自 K-S43：

I've had this a few times. And yes, its very annoying. I've seen it on 444, Long day, Pipeline Destruction, Bunker Buster, and Cape Rainy Assault on Ace, but at the time, I just figured it was some weird part of the scaling, only realizing it wasn't after replaying them. I would spend the entire mission watching as Missiles would come from just off my mini map. When I expanded it, I could not see where they were fired from.
As for the Cant-take-off bug, I experienced that one on the first mission when I tried to play through Steam Link. I can say that if you go 3rd person, you can see all your flight surfaces adjusting according to your input, the plane just doesn't respond to it at all.

That is EXACTLY what I saw in both cases. At mission start I could see zero enemies, not a single bit of red on my mini map, and yet missiles are constantly coming at me. And you're absolutely right about the take-off problem too: I tried multiple times and could see all the flaps (ailerons?) or whatever moving as I moved the sticks without doing a thing. What an odd pair of bugs.

[LAUGHTER GANG CEO]

In my time playing AC7, I haven't seen 444 as a mission that deviates from the style of the rest of the games. Constantly being under radar lock shouldn't be a surprise at that point in the game, even if it's your first playthrough. Mission 3 is a prime example of constant missile warnings, because the arsenal bird's AAM launchers mainly target Trigger (you), as if it can see the future. As for the bombers, I don't have any better advice to offer other than to use an aircraft like the F-14D or the MiG-29A, since they both have LAAMs. Aircraft with multi-target missiles such as the 4AAM, 6AAM, and 8AAM are also relatively effective for this mission. Also keep in mind that the Tupolev Tu-160s you encounter in the mission are both more durable and faster than the Tu-95s. Two missiles (or one LAAM) is not enough to down one.

[Phileosophos]

Interesting. Maybe I did better in the prior missions or something and avoided putting myself in a position where missile-lock-on was such a thing. Since my last posted I've finished a few more missions on PC and tried the "444" mission on the Xbox One X and found it happily without the can't-take-off-bug at least.

[Dr_Skoda]

引用自 {O|G}Phileosophos：

引用自 BEEP BEEP BEEP MISSILE ALERT：

It's impossible to be locked on as soon as you take off, stop exaggerating. Yeah, you must be missing the bombers bombing the airfield, go watch a video of someone clearing the mission and compare with your own performance.

I'm not exaggerating at all. Once I take off and get the "altitude restrictions lifted" message, I am locked onto and have missiles coming at me non-stop the entire time all the "humorous banter" is taking place with my fellow convicts. I'm not making a thing up. It makes no sense. That's why I'm posting.

Ive replayed this mission god knows how many times and i dont get locked on to immediately after the altitude restrictions were lifted, roughly maybe 5 seconds afterwards flying towards the nearest enemy fighter

[K-S43]

引用自 8x50mmR：

引用自 {O|G}Phileosophos：

I'm not exaggerating at all. Once I take off and get the "altitude restrictions lifted" message, I am locked onto and have missiles coming at me non-stop the entire time all the "humorous banter" is taking place with my fellow convicts. I'm not making a thing up. It makes no sense. That's why I'm posting.

Ive replayed this mission god knows how many times and i dont get locked on to immediately after the altitude restrictions were lifted, roughly maybe 5 seconds afterwards flying towards the nearest enemy fighter

The word your looking for is Bug. As in it is caused by a bug.
Again, Ive experienced it. You have missiles coming at you from off the mini map, when its expanded, you can see no enemies in that area, its similar to the ones from Faceless Soldier, or Mission 3 post dogfight.

[LAUGHTER GANG CEO]

引用自 K-S43：

引用自 8x50mmR：

Ive replayed this mission god knows how many times and i dont get locked on to immediately after the altitude restrictions were lifted, roughly maybe 5 seconds afterwards flying towards the nearest enemy fighter

The word your looking for is Bug. As in it is caused by a bug.
Again, Ive experienced it. You have missiles coming at you from off the mini map, when its expanded, you can see no enemies in that area, its similar to the ones from Faceless Soldier, or Mission 3 post dogfight.

Huh. Never thought they'd waste Helios on convicts.

[LAUGHTER GANG CEO]

For all we know, it may have been an intended effect, made to imply that the radar systems on the planes are out of whack (let's face it, most of their planes are built out of spare parts, and it's not like the convicts deserve any better.)

[AlmX]

Hate this mission too. A few minutes into the mission and I'm constantly under a stream of missiles, turning around like mad, and the bombers just keep coming while their support piles up. Eventually, it's the usual "mission failed" and you do it from the start all over again.

[Dr_Skoda]

引用自 LeraYTZ (민지)：

Hate this mission too. A few minutes into the mission and I'm constantly under a stream of missiles, turning around like mad, and the bombers just keep coming while their support piles up. Eventually, it's the usual "mission failed" and you do it from the start all over again.

It doesnt seem that hard...

[Mad Scientist]

引用自 {O|G}Phileosophos：

As to your comments about the PC, I shouldn't have to deal with garbage just because it's a PC title.

You deal with the problems and quirks involved with what you wish to play something on.
In the case of PC, unlike consoles which always have the same generalized setups; PCs have different hardware, software, settings, BIOS and otherwise. There's too many factors to have everything always work across all setups, plus you need so much raw power to play games.

This isn't a game issue; it's a user issue.

Don't like it? Stick with consoles.

[LAUGHTER GANG CEO]

I mean, Golem 1 Knocker did say something about being able to use chaff in a 9G turn, but we saw how well his advice worked for Golem 2 Brownie.

[Dr_Skoda]

引用自 Rad Russian：

I mean, Golem 1 Knocker did say something about being able to use chaff in a 9G turn, but we saw how well his advice worked for Golem 2 Brownie.

To be fair she took a hit, control surfaces were probably damaged.