415607E6 - Call of Duty 4: Modern Warfare

[AFirstTimeMapMaker]

Marketplace

Tested with EmuCr Xenia Git (2015/08/30)

Issues:

(SPLITSCREEN) When map finally loads, the screen becomes frozen and unable to do anything from that point on.

Log:

https://drive.google.com/file/d/0ByYmRipH7OkfdkhOMjBhNy1CTDA/view?usp=sharing

[AFirstTimeMapMaker]

Well, as of the (9/2/2015) EmuCr Xenia Git

Bog map now loads and is playable, some other maps still don't work etc.

[benvanik]

Crazy! What's the framerate like?

On Wed, Sep 2, 2015 at 12:40 PM mrsellermrbuyer notifications@github.com wrote:

Well, as of the (9/2/2015) EmuCr Xenia Git

Bog map now loads and is playable. [image: cod4works] https://cloud.githubusercontent.com/assets/7894021/9642229/f7cfeb0e-5188-11e5-884c-7e10be21afb9.png

— Reply to this email directly or view it on GitHub https://github.com/xenia-project/game-compatibility/issues/152#issuecomment-137223379 .

[AFirstTimeMapMaker]

Average is about 15 fps or so, barley playable but its getting there.

[Razzile]

@benvanik World at War also loads now. I would submit a report but i'm out atm

[heysehaven]

Shipment map also loads here - EmuCr Xenia Git (09/09/2015)

[theoldsport]

Not sure if this has happened to others, but I noticed that I'm only able to boot this game once (with each new build). Every other time it shows a gray window. Modern Warfare 2 is also affected. I haven't seen this occur with any other games. LOG: https://drive.google.com/file/d/0Bw1m9gdt8DfpUS10RUxNYXZhcDQ/view?usp=sharing

!> 0000007C BaseHeap::Alloc page count too big for requested range !> 0000007C PhysicalHeap::Alloc unable to alloc physical memory in parent heap

[heysehaven]

@theoldsport I can boot it normally here

[Roach115]

i wonder if its diffrent with only mp but i can not load the game anymore it just gose to a white screen.

[theoldsport]

@Roach115 I've had a this issue for the last few months and I'm not sure what's causing it. Sometimes the game will boot consistently, but after some unknown change, it doesn't boot at all. At first I thought it was an Nvidia driver issue, but other games I've tested work fine. I believe a similar problem causes Modern Warfare 2 to occasionally crash upon booting as well.

Here are both logs for Modern Warfare and Modern Warfare 2

Does your log show something similar?

[Roach115]

@theoldsport i do not know how to get to said logs. but i have tryed other call of duty games made by tryarc and this problem dose not happen the game boots up but will stall only when a map is loaded or switching to mp could it be that this problem is linked to how activison makes there game's? but i did not have this problem on an older build of xeina the game got to the menu's

[Roach115]

@theoldsport ok... found my log looks like yours made it futher than mine for some reson mine ends on !> 0000007C PhysicalHeap::Alloc unable to alloc physical memory in parent heap

yours ends at !> 0000007C PhysicalHeap::Alloc unable to alloc physical memory in parent heap d> 0000007C MmAllocatePhysicalMemoryEx(0, 6F500000, 20000004, 00000000, FFFFFFFF, 00000000)

[theoldsport]

@Roach115 It's just the same error repeating for different memory locations, so I didn't really get any further than you. Glad I'm not the only one who's come across this. But yeah, it looks like only Activision's games are affected. Can't say much more than that though :|

[Roach115]

@theoldsport it seems to be fixed now

[XeClutch]

When loading into any map (singleplayer included) it seems as though the last frame of the loading screen doesn't get turned off and so as a result you can hear things in game and interact with them but all you see is the last frame of the loading screen.

Also, when you click Multiplayer to switch to the default_mp.xex the game freezes. The same happens when you try going from Multiplayer to Singleplayer (default.xex).

So.. this happens when trying to get in via Resume Game.

Also, this is what I was talking about when trying to load into a map (doing this through split screen btw). I can hear myself navigating through the menu in game and once I pick a team and class I can hear myself walking around and even shooting my weapons.

After a little while I went back and checked on the xenia process and found this. Not sure what's going on with the game. Maybe just insane lag on my part? CPU is a OC'd FX-8320 and GPU is a OC'd GTX 750 Ti.

This is all as of the 7/12/2016 Xenia Git.

[jc1999]

The SP will load, but there is some issues like, you can't see shit

[spectrumm]

Tested on https://github.com/xenia-project/xenia/commit/cecc66622f278ca057e19afe86768af6dfe640ba

Log

[spectrumm]

OpenGL 4.5 test from a few weeks ago, forgot what build it is but should say on screenshots, sorry. NVIDIA GTX 970

Very impressively correct rendering of guns.

[AFirstTimeMapMaker]

Tested Alpha version 253, not working, Crashes when you load into a MP Map. output.log

[spectrumm]

Only bad fps(30-45?) and some gpu draw errors, else very nice

[Josivan88]

way better these days: a problem on split screen, only player one is shown properly.

[HyproZe]

Tested on xenia-project/xenia@293851d

Tested the singleplayer, the games run at 30fps.

Shoud rename this thread to "415607E6 - Call of Duty 4: Modern Warfare" only no? Not only MP

Issues:

After the prologue and the first mission on the cargo, the game start at the third mission to lag and the audio becomes completely a garbage maybe due to the choppers near (fps drops..) the screenshot with the yellow car

Log:

xenia.zip

Screenshots:

Labels:

state-gameplay | gpu-shader-errors | gpu-corrupt-drawing

[Triang3l]

Lighting issues are no more, but there are occasional black textures that may be reloaded by pressing F5.

[Josivan88]

Good news! thanks for share, it already in Canary or only on master? others call of duty are ok too?

[Crsarmv7l]

Tested this last night. Played through "Crew Expendable," crashed once but made it through the second time. Crashed again in the Marine desert mission.

[Margen67]

Xenia Canary issue: https://github.com/xenia-canary/game-compatibility/issues/140