... And sometimes the best solution, which results in the least amount of loss & breakage, may actually be to LEAVE that bug as-is. Sometimes it has to be a sacrifice. This often upsets both QA engineers and customers, but you gotta pick your battles!

The developer list of things to do is usually really long, and there are only so many hours in the day. It’s not that the bug took months to fix, it’s that the dev attention is elsewhere while the modders is not.

It did. A lot of them. People love to ignore that little fact, though.

Homeworld.

Payday 2 has no arm and leg hitboxes. The devs said it would be impossible to do in the game’s engine but modders fixed it in no time.

“99 programing bugs in the code
99 programming bugs
Take one down
Pass it around
137 programming bugs in the code.”

This is true, but leads to something that actually does bother me: when developers seem to ‘go cowboy’ (god I hate that phrase, too) and rush out an update, saying something is fixed (then end up breaking more stuff in the process).

Even leaving aside terrible tools (as Destiny seems to have), most time between a really bad bug is discovered and its fix going to the users is usually spent on Q&A. The fix must be tested to death as actually fixing the problem and, more importantly, not causing new ones.

Not exactly applicable, but the Dark Souls PC port comes to mind in which the developers couldn’t get (intern) modern resolutions to work but some guy released a patch about 2 hours after the game released which fixed that.

my favourite thing is when a modder fixes one of these bugs with a single line of code, and it takes months before the developer decides to do it themselves.

But what I wanna know is, does it have a Heat Hawk in the trunk?

Sell it to the US as that and only that. Preferably with 210 hp, a manual, and RWD. We’re gonna buy it.

Because it would make too much sense.

the tooling exists in records and in an essence, physically. You gotta remember that people still make replacement parts for these

Not only would it be cheaper than the F-35 but also cheaper than developing a new jet that can fulfill the needs that time has proven the F-35 can not.

Since there appears to be little will in Washington to correct the error in judgement that ended the F-22 line by putting an improved F-22 back into production, we need to learn from this very expensive mistake.

Actually the tooling may well not exist. I can’t say for certain regarding the F-22, but it’s not uncommon for tooling to be destroyed once an aircraft’s production run has ceased.

My thoughts exactly; it’s not exactly pushbutton, but it’s still cheaper and fits the need better, so...why not?

You’d have to unpack and reinstall the tooling, but my non-expert thought is that the bigger problem is getting the people building them back up to speed. Planes get cheaper the more of them you make, and production lines get faster as they get experience, and it could very well take a dozen runs before things are…

Seems like the obvious solution would just be to buy some more... I mean they shut down the program, but it’s not like Lockheed dumped all the files when that happened. All the tooling and plans exist, why not just crank out a few more? Maybe it’s just too prohibitively expensive to start up the assembly line again?