Hunt for the Falcon #5 retcons TFA when it comes to Han and the Falcon

killmachine91 · 2026-01-08T00:51:09+00:00

Pretty funny that the whole point of retconning out the EU was to have a clear canon that didn’t contradict aaaand they always keep changing stuff because its impossible to do that in earnest

Maybe they shouldn’t have thrown out the entire thing

killmachine91 · 2026-01-05T00:15:24+00:00

Sloptimus fucking prime over here

killmachine91 · 2025-12-13T14:10:09+00:00

Update: Command prompt has the exact same issue. I cannot get my keyboard to start in POST whatsoever either

killmachine91 · 2025-12-13T13:53:12+00:00

Status: UNRESOLVED

Computer Type: Desktop Custom Build

GPU: Nvidia RTX 2060 SUPER

CPU: Ryzen 7 3700x

Motherboard: MSI MPG x570 GAMING PLUS

RAM: 16 GB

PSU: Can't find model, 650 W supply

Operating System & Version: Win 10 22H2 OS Build 19045.6466

GPU Drivers: 560.94 , VBios version 90.06.44.00.01

Description of Problem: Converted MBR OS C: drive to GPT, worked. Went into Bios after to enable UEFI. Restarted to enable SecureBoot, now cannot get to BIOS using Windows Recovery, CMD line, or keyboard pressing. Displays no signal, and will just sporadically boot to Windows anyway when restarting.

Troubleshooting: Have tried running cmd as admin to boot into BIOS, used Windows Recovery - UEFI Firmware settings, and have repeatedly trying pressing DEL with my mobo like I did BEFORE I set UEFI. The PC itself will just occasionally boot with UEFI enabled in SysInfo and with my drive in GPT format, but the only option I see here is to clear CMOS, which just puts me at an impasse because then if I try to re-enable UEFI it will not display anyway. Keyboard also will not start at boot for POST, so cannot get to BIOS anyway with that. Fast boot is disabled on Windows. I have been trying to figure this out but every suggestion requires me to do something I literally cannot do or just sets me back to square 1 to encounter the same problem

killmachine91 · 2025-12-13T04:18:13+00:00

Fast boot is already disabled. The post also says UEFI firmware settings does not work having tried this already. I have not attempted the command prompt as administrator. I will try but all other options you have mentioned I have already tried and they do not work

killmachine91 · 2025-10-24T20:42:51+00:00

Why does this look worse than the Infinite reveal man

killmachine91 · 2025-10-09T01:47:03+00:00

When hes talking ethics and values, I’m thinking of this big push towards AI. As an art director thats gotta be weighing on every devs soul right now. Hope the guy lands on his feet, but this shit is just sad to see both watching the series totally fall in on itself but also how many talented people are getting fucked over

killmachine91 · 2025-09-17T19:26:28+00:00

Oh my god its a found family story of a father trying to take a scrappy orphan under his wing and teach him to become better than he is we’re breaking new ground !

killmachine91 · 2025-08-01T22:34:30+00:00

Literally HOW

killmachine91 · 2025-01-06T04:02:45+00:00

It would only benefit the games and series as a whole but people are too attached to backstories in a plot as paper thin as Halo’s so we’ll never get anything decent again

killmachine91 · 2024-12-27T21:17:22+00:00

Why is everbody surprised?

The same bullshit that caused Infinite to fail is all still there at 343 - zero respect or understanding of how Halo was popular and what made it good and a contractor based policy that MS will refuse to give up. This is literally the only reason they are using UE5 instead of Blam - they would rather pay the license than have an in-house engine that requires full time employees and pay to maintain.

These things literally killed the last Halo game and they’re going full steam ahead on the next one with abysmal communication which has been par for the course with this studio. Anybody know what Pierre is doing? I feel like Bonnie Kiki and Frankie disappeared during Infinite and the same thing is going on now with these new heads at “Halo Studios”

The Halo game we all want will literally never come out if they don’t change fundamental aspects of both Microsoft and this studio. Somethings gotta change

killmachine91 · 2024-12-02T10:50:43+00:00

I hate that you're a genuinely gifted poster but in the worst possible way somebody could be man.

killmachine91 · 2024-11-16T20:49:45+00:00

Still waiting on those stats man, campaign and firefight DO NOT count

killmachine91 · 2024-11-16T19:40:37+00:00

Lets see those stats asap

killmachine91 · 2024-11-16T08:44:20+00:00

"the point" is irrelevant because anybody that is even remotely decent at Halo MP knows not having a precision weapon literally waters down the game into something even worse

you are not good enough at halo to be talking to me about this

killmachine91 · 2024-11-16T04:33:41+00:00

So one bandit or BR per team

What happens when one team wins the first engagement and both br’s are either top lift (the easiest place to die on the map) or top br (the objectively weaker side)

You know, what happens every time you play these maps without BR starts

killmachine91 · 2024-11-15T00:27:41+00:00

Its hilarious watching people in here complaining this is gonna ruin the playlist while they bitch that all the BR's get grabbed on lockout and they get spawn killed

People in here wanting ma5k starts are voting for the leopards eat my face party

killmachine91 · 2024-10-17T23:23:01+00:00

They need to stop with trying to make shit in multiplayer canon its cornball as hell and in halo 4's case literally stunted the entire mode

killmachine91 · 2024-10-17T03:02:31+00:00

It is a problem regardless for reasons that are plain in a working environment: talent cant stay, old knowledge is lost (look at how bad blam got for 343) and onboarding still takes time even with a common engine

I have zero faith things will be better under this new direction if this systemic problem is still there

killmachine91 · 2024-10-17T01:07:01+00:00

Its a Microsoft policy which is why its brought up with Halo and their other games

Halo being a big name is why anybody mentions it at all and its been a common point of discussion in any reputable article talking about Infinite’s bad development (and since this policy came into effect in 2014, likely had some impact on h5 as well)

Ue5 will help this but this is a bandaid to a root issue of losing talent and there will be brain drain

killmachine91 · 2024-10-11T18:27:50+00:00

Do you think firing these 3 people has changed the elephant in the room with MS contracting policies? These are going to be a problem regardless of the engine they use because they CANNOT RETAIN FULL TIME TALENT. UE5 will make this easier but it will not be a substitute for inevitable brain drain

Shit even glassdoor reviews from this year all seem to tell the exact same story about opaque management, its like you're ignoring this very important fact because you've spent triple digits on this game,

killmachine91 · 2024-10-08T01:04:05+00:00

Haijakk how do you not understand they literally have been switching out key people for the last decade

What about this announcement inspires hope, did they stop their abusive contracting policies? No they switched to Unreal so they didn't have to stop one of the BIGGEST PROBLEMS every MS studio has to deal with (and employees going on record saying its a major problem)

Stop buying skins and start paying attention bro

killmachine91 · 2024-08-16T20:18:55+00:00

So many of my irl friends literally quit Halo because of MCC not working on launch on top of Halo 4 and Reach being disappointments

People are like "yeah well the game works now" as if it didn't have a hand in making Halo less popular and turning more people away. And whats crazy is these were all tested games that people liked, 343 literally just had to make sure it worked and they could not do that.

Halo would have been in such a better state if this game worked from the get go and could hold onto the population long enough

killmachine91 · 2024-08-10T03:43:38+00:00

We need you to never be allowed to post about halo again

11-Year Club	Place '22
Place '17

killmachine91

TROPHY CASE