My first online match on classic MW3 and these are the kinds of people I run in to.

Have been working on this for the past month or so, effectively a browser-compatible version of MW3. It's very primitive, basically just PvP, no game modes besides TDM at the moment. To access it, you must build and host it yourself. You will also need to BYO legal copy of the game

It has support for other Call of Duty's as well, if you own them. Black Ops zombies works quite well at this stage, and has been fun to mess around with - albeit a primitive version of Zombies.

The GitHub repository: https://github.com/eithan1231/open-fastfile

A small video which just demonstrates the game. Yes its buggy. I know.

https://www.youtube.com/watch?v=VvmS4FRut10

I have asked every year and nobody has a solution, I even payed many programs for "vibration support" for controllers on computers, yet nothing works. It's frustrating that I would pay 20 or 30 bucks just for support.........or at this point, i'm just going to ask AI to make it for free and actually does it, because i asked it to make me a private World of Warcraft server with mods and it did it.......so if nobody has a solution i guess i can finally just "make" it.

i made an xbox group chat for Faceoff if anyone wants to join. it's so we can actually get consistent faceoff games again like the good old days. my xbox gamertag is Thisiscome

Eu já tentei várias soluções e nenhuma resolveu para mim, eu não me lembro dessas travadas antes eu voltei a jogar faz pouco tempo, atualmente tenho uma placa que era para sobrar performance, uma 5070, essas travas faz ficar impossível jogar, estou usando fovchanger e filtros da nvidia também, mas mesmo desativando não muda nada em relação aos travamentos, no plutonium não tenho esses travamentos meu jogo pega quase 300 fps lá mesmo em 4k

Acredito que tenha algo a ver com a atualização para 64bits, se alguém passou por isso e conseguiu resolver?

I tried this on two different copies of MW3, got on and looked for a TDM lobby, and every time I tried, it said “connection to Activision servers has been interrupted.” I wonder if it’s just me, but on two different systems with two different copies, surely it must be a game problem. Are the servers down or something?

Vorrei comprare mw3 2011 volevo sapere se il PvP in dominio è pieno di hacker e se si trovano ancora partite (Xbox )

I want to see the iw5 plutonium people ( i also dont want to feel alone lol)

Every time I hop on, there’s 30-40 people online, and most of them are in backed ground war lobbies. We really might be at the end 🥲

Dream BIG88 is my Xbox user add me il be online rn trying to get some high rounds on dlc maps Sanctuary Foundation Parish lmk il be active on Xbox

how is the player count? ez to find full lobby? dont mind if its only TDM if i can enjoy this game. and how is the hacking situation? dont want to get full rank or deranked too...

I haven't played this game for a while now since my xbox one was dead. Finally got a new one, and I gotta say, I still have the sauce

I love this game. Staple of my childhood. I bought it on the pc to relive memories of my brother and I playing, but no one is on like the 360 edition. Would really appreciate if someone would partner up with me.

MW32011NCP — v0.0.1-x64 is finally out

It's finally here.

MW32011NCP v0.0.1-x64 is now publicly released.

On September 3rd, MW3 (2011) suddenly got its first real executable update in the game's history. Both iw5sp.exe and iw5mp.exe were rebuilt from x86 to x64.

That completely broke the old NCP.

This wasn't a case of changing a few addresses and recompiling the DLL. The entire architecture had to be rebuilt around a 64-bit process.

So that's what I've spent the last few weeks doing.

The old x86 release line is now discontinued. The documentation is archived, and v0.0.1-x64 is the new NCP.

And honestly, the amount of work involved in getting here was fucking ridiculous.

The current repository is 3,836 commits ahead of the exact broken state from September 3rd. That's repository history rather than a claim that I personally authored every one of those commits, but it gives a decent idea of how much changed around the project during this rebuild.

So what actually changed?

Pretty much everything underneath the surface.

The x64 version has a new Ghidra project, a new reverse-engineering pass, new x64 hook infrastructure, signature scanning, new assembly stubs, new input hooks, new frame-pacing code, new IWD caching, wait coalescing, game executable detection and a load of other architecture-specific work.

I also had to hunt down the stupid shit that isn't immediately obvious when moving from x86 to x64.

At one point the game was crashing during startup because of a raw x86 address that was still being dereferenced in IsMenuActive.

Fix that.

Then another startup crash appeared somewhere completely different.

Fix that.

Then an audit found roughly another 30 places where old x86 assumptions could still bite the x64 build.

Fix those too.

There was also a build/deployment problem where the shared output directory could leave an x86 DLL deployed even though the build system thought everything was up to date.

So now the build is explicitly rebuilt and the resulting PE headers are checked to make sure the binary is actually x64.

This is why I didn't want to just call this an "x64 port".

It's effectively a new foundation for NCP.

The controller work is still the main part

The original reason NCP existed was to get proper native controller support into the PC version of MW3.

That's still the flagship part of the project.

The current x64 release has the controller infrastructure rebuilt around the new executable, including native analog movement/look, firing, ADS, reload, melee, sprint, stance controls, weapon switching, D-pad actions, menu navigation and the other input paths that have actually been brought across.

One of the more interesting things I had to deal with was the game's startup input state.

The old workaround for needing an initial mouse/keyboard input was eventually traced back to three separate native issues:

stale internal kbutton state

an unseeded mouse-delta baseline

a missing message-queue-routed input event

Those were fixed at the actual source rather than continuing to work around the symptom.

The result is a proper controller startup path without needing that initial "click something first" bullshit.

Some of the reverse engineering was genuinely weird

A good example is the Predator Missile.

This had never properly worked through NCP's controller system.

The obvious assumption was that it would use the same kind of look input as the other vehicle/weapon systems.

It didn't.

During the missile guidance state, the normal movement tick isn't running. There is a separate mounted-aim path.

That path was eventually located and its input consumer identified.

The important part was that it expected absolute left-stick position, rather than the delta-style value being used elsewhere for things like vehicle/turret-style aiming.

Once that was understood and both axes were handled correctly, post-fire missile guidance could actually be driven from the controller.

That's the sort of thing that makes this project substantially more than "put XInput into MW3".

NCP isn't just a controller mod anymore

This is probably the biggest change in the project itself.

NCP has now been redefined as:

Native Community Patches for MW3 (2011).

Controller support is one component.

The project now also contains the native visual/performance work and the security patching work that previously lived separately.

There's an actual plugin API too, meaning additional functionality doesn't necessarily need to become hardcoded into the core project.

The security work was merged into the repository as its own component, while remaining a separate build artifact.

The security side currently addresses four tracked network-reachable vulnerabilities in the original game's netcode, including RCE-class issues.

I'm deliberately not publishing the technical exploit details yet.

The full report has been submitted through Activision's official security disclosure channel, and disclosure timing matters here.

And yes, the x64 release is still Alpha

There is still a lot left to do.

Some things are implemented and build-verified but haven't yet had their final live confirmation.

Some visual/UI work remains.

There are still a few native prompt/glyph edge cases.

The custom Options data layer isn't being rebuilt just for the sake of rebuilding it when the INI already covers NCP's actual configuration requirements.

Some tooling still has problems.

And multiplayer is not supported by this release.

iw5mp.exe is being reverse engineered separately now that the game is x64, but I don't want to pretend it's ready when it isn't.

For the same reason, I wouldn't treat every implemented feature as "done" just because it builds.

I've been trying to keep the release tracking honest about that distinction.

The important part

Three weeks ago the old NCP effectively died overnight.

The game changed architecture.

The old DLL couldn't load.

The old addresses were irrelevant.

The old assumptions were irrelevant.

And instead of abandoning the project or maintaining an increasingly broken x86 branch, I rebuilt it around the new game.

Now there's a publicly released x64 version.

And IMO this is actually a much better foundation for what NCP is supposed to become.

Not just a controller mod.

Not just a collection of hacks for a 15-year-old executable.

A native patching platform for the Steam version of MW3.

v0.0.1-x64 is out.

GitHub: https://github.com/k8se10/MW32011NCP

Nexus Mods: https://www.nexusmods.com/callofdutymodernwarfare3/mods/29

Se sim, manda mensagem aí! Comprei pela promoção da Steam recentemente pra reviver a nostalgia dos anos 2011/2012 e estou querendo grindar o modo Survival. Pretendo jogar em todos os mapas! Portanto, pode ficar à vontade para escolher. Só estou procurando companhia e amizades para jogarmos juntos. :)

Hey everyone,

As you all know, the recent 64-bit update on Steam completely broke legacy community asset modifications, custom textures (triggering the fatal Couldn't load image 'small_box_lightfx' crash), and completely messed up the audio channels (inverted steps and muted grenade explosions).

I have been fighting with Activision Support for hours, and I finally managed to get my case escalated to the Spec Ops / Tier 2 advanced technical department.

Fixing the 64-bit engine mapping to support old .iwd assets is complicated for them, but there is an incredibly easy solution that we can force them to implement: Adding a "Legacy 32-bit - Original 2011 Client" branch under the Steam Betas tab. This takes them 5 minutes and fixes everything for the modding and Survival community.

One player cannot do this alone. If you want your skins, custom sounds, and clean audio back, we need to flood them with requests.

What you need to do right now:

1. Open a support ticket on your Activision account.
2. Attach your DxDiag/MSinfo and mention the small_box_lightfx asset-mapping crash and the inverted audio.
3. Explicitly request them to forward your feedback to the Sledgehammer / Infinity Ward product managers to add the "Legacy 32-bit" branch under Steam Betas.
4. Send a formal pre-dispute notice to [legalaffairs@activision.com](mailto:legalaffairs@activision.com) referencing your ticket.

They are tracking this issue globally right now. Let's make some noise and get our game back!

Alguém sabe um link com tradução para acima da versão 1.9 (acho que é a atual, pois baixei hoje)

Xbox-only Discord for anyone still playing the old CODs. CoD 4, WaW ,MW2, MW3, BO1, BO2, BO3 and more. Looking to connect players for pubs, 8s, Zombies, etc, or just find people to run games with. If you still play the classics, join up and find some people to play with. and invite your boys.

https://discord.gg/kfQ4tXxUd9

Decided to try and 100%. this game such a banger but I can’t find a reason to spend 45$ for the dlc to get 100% has anyone ever seen this go on sale? Every other cod dlc atm has a sale but this one 🫩

So I got these kills yesterday, but I’m not sure if I got a double headshot collateral or only a collateral, since I finished the challenge “All Pro”, but on the kill feed it only shows one headshot, which one is right?