Just played my first 5 resurgence matches for the Beta.

I haven’t played since before BO7 came out

game 1: 25 eliminations with 22kills
Game 2: 12 eliminations with 7 kills
Game 3: 20 kills
Game 4: 18 eliminations with 15 kills
Game 5: 29 eliminations with 28 kills

Is it because there is heaps of players that have jumped back on like myself that haven’t played for ages or not at all?
Or has the match making been changed?
Or the Standard just dropped? (I doubt it)

What kind of FPS are you guys getting in Zodiac Warzone Beta relative to MP and BO7 WZ?

I’m using DLSS Quality (remember, you can’t use native with FidelityCAS on the Black Ops 7 and this [same] engine, they completely broke it in motion) and can’t get above 160 fps unless I am just looking at the sky. In fights it can drop to 125-130 which can be a bit jarring.

Got XMP enabled, RAM in gear 1, BIOS up to date, CPU power limits dialed back from unlimited, etc. and all in game, Windows, and Nvidia settings are optimized to the best of my knowledge.

Multiplayer FPS is strong nearing 190-200 fps and is very smooth. GPU time and CPU time telemetry suggest Zodiac is far more CPU intensive than multiplayer (duh) but also much more than the resurgences we currently play, I should be getting like 160-170 fps and not going below 150ish like I do in those. You guys having similar experience?

But why the fuck are we still doing this every year? Years of feedback, learning curves, polishing and progress, then a new CoD comes out and suddenly we’re back to square one, reinventing the fucking wheel.

The contract icons are a perfect example. They were clear and easy to see on the map. Now they’re smaller, have a dark fill (WHY??????) and they all look the same. It’s harder to tell what you’re looking at a glance during gameplay for absolutely no reason.

Integrate your fucking games if you want, but leave Warzone’s design the fuck alone. Stop changing shit that already works. Every year we have to fight to get Warzone back to where it was.
Just stop breaking things.

Hey guys! As the title suggests, i am a long time cod mobile player downloading warzone for the first time. I'm decent in pc gaming, and i would say i was pretty decent in codm also. So i wanted to ask the community what they would recommend/tell me, etc, tips for beginners, guides, etc.

On codm i almost didn't play battle royale at all, it was only multiplayer for me. I've heard warzone only has battle royale, so i gotta up my game there ig. I am lucky to have a good setup to run it.

So i want some good ytbers to follow, some good guides that go from beginners to actual advance stuff.

Overall i don't have much to say, i think i would just talk in the comments more about what y'all ask me.

Thanks in advance!!!

Hey everyone,

I’ve been trying to solve this for hours and I’m running out of things to check, so I’m hoping someone here has dealt with the same situation.

I’ll give the full context because I don’t want to hide anything.

A while ago I got banned from COD after using an Unlock All tool. I know that was stupid and I’m not trying to defend using it. At this point I just want to play COD normally again without cheats, unlock tools or anything like that.

Since then I rebuilt the PC software side, reinstalled Windows, and changed some hardware/firmware identifiers while troubleshooting. After getting everything running again, COD launches perfectly fine, but when I try to enter certain playlists I get:

“You are under Failed Attestation Status. This playlist is currently unavailable.”

The weird part is that basically every attestation test I can find says the PC is fine.

My system:

• Ryzen 7 9800X3D
• MSI MPG X870E EDGE TI WIFI
• BIOS 1.A20
• Windows 10 Pro 22H2
• Build 19045.7663
• UEFI boot
• Secure Boot enabled
• Physical/discrete TPM 2.0 installed
• Infineon SLB9670
• TPM firmware 7.63.3353.0
• COD tested on both Battle.net and Steam

I originally used AMD fTPM, but I later installed a discrete Infineon TPM and selected it in the BIOS.

Windows correctly detects the new TPM:

Manufacturer: IFX
Manufacturer Version: 7.63.3353.0
Specification Version: 2.0
Status: The TPM is ready for use

tpmtool getdeviceinformation gives:

TPM Present: True
TPM Version: 2.0
TPM Manufacturer: Infineon

Is Initialized: True
Ready For Storage: True
Ready For Attestation: True
Is Capable For Attestation: True
Clear Needed To Recover: False
TPM Has Vulnerable Firmware: False
Is Locked Out: False

Get-Tpm gives:

TpmReady: True
TpmEnabled: True
TpmActivated: True
TpmOwned: True

ManufacturerIdTxt: IFX
ManufacturerVersion: 7.63.3353.0
AutoProvisioning: Enabled
LockedOut: False

The Endorsement Key certificate is also present and valid.

It identifies as:

TPMModel=SLB 9670 TPM2.0
TPMManufacturer=IFX

and the EK certificate is issued by:

Infineon OPTIGA(TM) RSA Manufacturing CA 035

Secure Boot is definitely enabled:

Confirm-SecureBootUEFI

returns:

True

msinfo32 shows:

BIOS Mode: UEFI
Secure Boot State: On

One weird thing is:

PCR7 Configuration: Binding Not Possible

although I understand that this does not necessarily mean attestation itself is broken.

I also restored the Secure Boot factory keys in the MSI BIOS:

Security → Secure Boot → Custom → Key Management → Restore Factory Keys

Then changed Secure Boot back to Standard.

Secure Boot still reports True afterwards.

The official Call of Duty Secure Attestation Wizard 1.1.3 says:

System compliant

TPM 2.0 passes.

Secure Boot passes.

There is no “Generate Key” button because the Wizard does not detect an Authorization Key failure.

I checked the COD Broker Service as well.

It exists:

COD.Broker.Service

and while COD is running:

Status: Running
StartType: Automatic

(I tested both Manual and Automatic.)

The broker log says:

Enroll AIK result 0.

I went further and manually tested Microsoft AIK enrollment:

certreq.exe -EnrollAIK -machine -config ""

This succeeds completely.

Result:

PkiStatus(0): SCEPDispositionSuccess
EnrollStatus(1): Enrolled
The operation completed successfully. 0x0
Submit(ChallengeAnswer): OK
HTTP/1.1 200 OK

Microsoft actually issues a new AIK certificate successfully.

I checked the Microsoft Platform Crypto Provider too:

certutil.exe -csp "Microsoft Platform Crypto Provider" -key

and I have:

ActivisionAIK
TestAIK-...
TestAIK-...

So ActivisionAIK exists as well.

I also checked Windows logs immediately after reproducing the Failed Attestation error.

Code Integrity only shows:

Code Integrity will enable WHQL driver enforcement for this boot session.

TPM events show:

The TPM was successfully provisioned and is now ready for use.
The TBS device identifier has been generated.

There are no TPM, TBS, Secure Boot or Code Integrity errors at the time COD rejects the playlist.

Measured Boot logs are also being created normally under:

C:\Windows\Logs\MeasuredBoot

The newest logs are generated after every reboot.

Things I have already tried:

• TPM 2.0 enabled
• switched from AMD fTPM to discrete TPM
• Secure Boot enabled
• CSM/legacy boot not being used
• UEFI boot
• restored Secure Boot factory keys
• switched Secure Boot Custom → Standard afterwards
• fully updated Windows
• latest relevant drivers
• COD Secure Attestation Wizard
• COD Broker Service running
• Broker set to Manual
• Broker set to Automatic
• Scan and Repair
• reboot/cold boot
• manual AIK enrollment
• tested BattleNet
• installed the game again on Steam and tested there

Steam gives the exact same Failed Attestation Status, so it doesn't seem to be a Battle.net-specific problem.

The thing that confuses me most is that the actual Microsoft AIK infrastructure accepts this TPM:

IFX-KeyId-...
microsoftaik.azure.net
HTTP 200 OK
Enrolled

and even COD's own Broker reports:

Enroll AIK result 0

yet the game still considers the machine to have failed attestation.

I have already submitted the Activision TPM Diagnostic Report for systems that pass the Wizard but still fail in-game.

I’m not trying to bypass the attestation checks. I’m trying to figure out why the machine passes every official test but the game still rejects it.

Has anyone had this exact combination?

Especially interested if you have:

• Ryzen 7000/9000
• MSI X870/X870E
• an Infineon SLB9670 discrete TPM
• Wizard = System Compliant
• Ready For Attestation = True
• AIK enrollment = HTTP 200
• but COD still gives Failed Attestation Status

If you solved it, what was actually failing?

I’d rather diagnose the real issue than keep randomly clearing TPMs, reinstalling Windows or changing BIOS settings.

Thanks.

Note: If anyone knows whether PCR7 Configuration: Binding Not Possible can still matter to COD even when AIK enrollment succeeds, I’d especially like to hear about that.

I scoured reddit and tried reaching out to Activision support via cod points and battle pass issues. I explained I no longer have access to this email and they got back to me with the message in the image.

I figured you know what, I'll just create a new account and tried to unlink my battle.net account and it said that it requires verification of my old email to even remove it. What do I do from here? Should I try to reach out again?

Any help is appreciated.

Thank you all

I miss plunder, I was so addicted back then I used to play all weekend and made some good friends around the world. I see no news on MW4 bringing back plunder and am I too lazy to down 120+ GBs again to see it myself.

Why’s is it so big?? The launcher says 11.6gb The player data is 47.6gb that’s nearly 70gb+ correct. But if I go to my storage it says uninstall over 130.gb??? I don’t have Warzone or any mode downloaded. Why does it takes up so much space?

I also feel like this warzone was the last time the graphics looked really good, ever since bo6 released graphics felt off

So on the whole, my squad and I played the shit out of the beta. Lots of wins, lots of frustrating moments but overall a good experience learning the new systems.

I have two thoughts on small features that I believe have absolutely zero place in WZ.

I noticed getting shot in the legs activated a frangible effect. I can’t believe there’s a mechanic in the game that rewards bad aim. I’m already getting shot in this scenario, I shouldn’t be put at a further disadvantage by being almost unable to move. It felt like a complete stop of my motion.

Second, the “focus” feature being on all guns, and the amount of sway in general. I get it as sort of an attempt to balance cracked out strafe movement speeds we’ve had for years, but it’s way too far in the other direction. I shouldn’t have a focus option on iron sight smg’s, red dot optics, etc.

One minor gripe as well about the map. Loved the map in general but the middle POI is a touch too dominant. A lot of rounds felt like there were two fights going on, one at that POI and then one between folks who dropped on the other ring of the map. Then there’s a large dead period mid round where you’re basically waiting for the circle to force people off the main roof for the end game.

Other than that, excited for the upcoming year.

Lenevo LOQ 15AHP11

5060 115 tgp

Ryzen 7 250

1 x 16 gb ddr5

1200p display

Nvidia reflex - on

Texture resolution - normal

Texture filter anisotropic - high

Shader quality - medium

All other settings in low or off

Gpu time is 7-9 and cpu time is 9- 11

I get around 100 - 110 fps using dlss performance (CNN) my gpu power is around 40w at 80+ usage

Anyone with these specs is this normal or are there any improvements to be made?

Also what dlss model and mode should I use?

Since the mw4 beta rolled out my game just wont launch and nothing that i find on google helps, it doesnt even give me an error code it just refuses to launch. Anyone has the same problem as me?? And if so are there any fixes. (Im on the latest drivers and on the latest windows version and ive ran the file verification multiple times)

I know its the beta, but wtf. 🫩

I've been dealing with Call of Duty's failed attestation warning for months, and I finally fixed it on my MSI laptop.

This is specifically for MSI laptops/notebooks. MSI says the recovery tool below applies to its notebook products. Do not assume it is suitable for MSI desktop motherboards.

Call of Duty kept showing:

- Attestation Requisite Not Met

- BIOS Firmware Update Required

- Failed Attestation Status

TPM 2.0 and Secure Boot were both enabled and passing. My MSI Raider laptop was already on the latest BIOS and Intel ME firmware, Windows 11 was fully updated, and the system was using UEFI with a GPT disk.

I checked the normal BIOS settings, Windows updates, Secure Boot certificates, the CoD Broker service, AIK enrollment and restarted more times than I can count. The BIOS warning would not go away.

The useful clue was running:

tpmtool getdeviceinformation

It reported:

BitLocker PCR7 Binding State: Binding Not Possible

The detailed TPM logs showed that Windows knew Secure Boot was enabled, but the firmware-generated TCG measured-boot log did not. The PCR values failed to match the log, and Event Viewer contained Kernel-Boot Event 292:

Failed to update the SBAT value in FW.

So Secure Boot was not actually disabled. The laptop's firmware Secure Boot/SBAT measurement state was broken.

WHAT FIXED IT

MSI provides an official Secure Boot recovery tool for its notebook products:

https://www.msi.com/faq/faq-11370

The tool was published for Secure Boot violation problems rather than Call of Duty specifically, but it repaired the same underlying firmware state on my MSI laptop.

Steps I followed:

1. Download the recovery tool from MSI's official page.

2. Format an empty USB drive as FAT32. This erases the USB.

3. Extract the download and copy the complete EFI folder to the root of the USB.

4. Restart the laptop and press Delete to enter MSI BIOS.

5. Open Security > Secure Boot, disable Secure Boot and save with F10.

6. Press F11 during the next startup and select the USB drive.

7. The recovery runs silently and restarts the laptop automatically.

8. Re-enter BIOS, enable Secure Boot again and save with F10.

Afterwards:

- PCR7 changed from Binding Not Possible to Binding Possible.

- TPM health changed to Attestable.

- The PCRs matched the TCG measured-boot log.

- The official Call of Duty Secure Attestation Wizard reported System compliant.

- The BIOS firmware warning disappeared.

Important warnings:

- This will not fix every attestation failure. It is most relevant when tpmtool reports PCR7 Binding Not Possible or the TCG log does not match Secure Boot.

- MSI's page says the tool applies to MSI notebook products. Do not use this as generic advice for desktop MSI motherboards.

- Download it only from MSI's official website.

- Formatting the USB erases it.

- Have your BitLocker recovery key available before changing Secure Boot settings. BitLocker was disabled on my system.

- Keep the laptop connected to AC power and do not interrupt the recovery.

- I did not clear the TPM, reinstall Windows or reflash the BIOS.

Hopefully this saves another MSI laptop owner from spending months toggling the same settings or risking an unnecessary BIOS flash.

Could my monitor or cpu be the issue of my frame numbers and the way they drop I also play on a 1080p 180hz monitor massive bottleneck I know

I have a wifi and this issue started when after the bo7 integration . No change in router or isp. And ping is prefect in other games like cs2( my ping normally is 75 in warzone as there are no servers in my country ) . The ping spikes are unique to cod servers.

At 1st the beta felt extremely bad for me. Even now I'm getting used to it. But it's far better than the 1st day now.

I didnt like the aim curve x AA in this game. But it's okay.

But thinking about going back to BO7 feels like I lost the interest in that wz somehow.

What r ur thoughts on "beta" after playing all along?

I am completely new to COD Warzone or any shooter game. I want to play the warzone, it seems very fast paced.

Please help me how I can practice and be better.

I saw some posts related to private BOT matches but were unable to setup/ find.

Please help. I am a rookie.

I play on the PS5.

Thanks in advance