Project Reality Forums

Guys after using the patch for V0.98 I tried to join an Operation Overlord match but it keeps crashing at 46% loading. Road to Saint Lo works fine though any suggestions? If it's any help I downloaded my patch from Moddb

Are you able to load it in local?

Run the game in windowed mod to see the error message if there is one.

Pvt.LHeureux wrote:Are you able to load it in local?

Run the game in windowed mod to see the error message if there is one.

Local doesn't work either. When it stopped loading I alt-tabbed and saw an error message would you like me to try to get it for you?

Yeah, when you see the error message press CTRL + C, then paste it here

That's strange it just loaded normally now. It crashed exactly 5 times before. All I did was play Doom didn't even reboot. Gonna try again for good measure...
Strange it worked again...
Dunno if I get the same problem I will make sure to post the error on this thread.

LOL Doom rescuing your computer.

I have the some problem in collision %48 when load Overlord day map, memory.dll error.

I have xp 64, AMD Phenom II 560 3.31 Ghz, ram 8gb

The virtual memory is in the partition C: whit 20gb of free space and the virtual memory is setting in 2Gb to 4Gb, I change the virtual memory to 8Gb and nothing change.

Ye, it sounds like you guys are simply just running out of memory on loading the map. Playing Doom must have just flushed your memory really well godfather_596 or something but ye, all of what you have said, and the memory.dll says your running out of ram...

Sounds like the map needs some serious optimization to me.

[R-DEV]Rhino wrote:Ye, it sounds like you guys are simply just running out of memory on loading the map. Playing Doom must have just flushed your memory really well godfather_596 or something but ye, all of what you have said, and the memory.dll says your running out of ram...

Sounds like the map needs some serious optimization to me.

Always thought Doom was awesome
The map I was playing before Operation Overlord was Road to St. Lo maybe that's the cause?
Would also like to note that I have 8 Gigs of RAM so there is plenty ( although BF2 won't use more than a few gigs).

Just played on a server a few hours ago that ran normandy. First time playing it,and first time it loads BANG runtime error (or I think it was since that's the only error I know to make the loud death knell of a runtime error and pop on screen on top of whatever is loading or playing when I play PR ). Then it did it again when i restarted pr,and then it started just ctding with no error.Every other time after rebooting it crashed around 44% every time with no discernible error. Haven't got it to load yet on any type of Normandy map (16,32,64). The first errors (runtime probably) might of been farther than 44% however.Unfortunately I do not have doom and rebooting does not get rid of it so I've yet to see this map for myself even once. And for anyone wondering I have the redistributables 32 and 64 bit for 2010,and there's more than enough ram and virtual I'd think for that to be a problem (6 gigs physical 9 virtual with barely a gig between the 2 used after a fresh restart from shutdown). The runtime error hasn't occurred since rebooting, just ctd with no error around 44% or so when I try to run Normandy locally. I've played a couple of the other ww2 maps no problem, just can't play this one.

BF2 doesn't allow more than 2gb anyway.

Did you have any other programs running in the back? Try to load the map in local without any other software running like Xfire or Skype, etc.

Or.... try to run Doom before

Just to mention, doesn't patch 1.50 allow bf2 to use more than 2gb of ram? The change log and such say it does. Although on the topic of background programs, while there's a number of minor ones, I don't use either skype or xfire and the only real program that would interfere might be AVG Internet Security 2012 and all the other related processes,although I've never had a problem I could point at that with PR before.Pretty much every other programs minor or necessary as far as I can tell. The essential windows programs take more memory than any of the other minor programs that are there almost put together.Unless mumble counts, but then I'm not playing online much in that case,am I?

Mmh I don't know what the problem is, I guess AD will have to look into it

Run in windowed mode, then screenshot the error message you get (if you get one).

Anything between 45% and 59% tends to be vegetation, so it's pretty strange that it's only crashing for him. Is there any placed on the secondary terrain?

I'll see if I can find an error,or if I can figure out what exact percentage and detail it's currently loading when I get a chance. Might try reinstalling PR,and see if that does anything,or repeatedly rebooting,and maybe just reinstalling everything bf2 related.

Just started trying this again after rebooting. I loaded another map, used a console command (game.togglefullscreen) to try to see an error (which screwed up the stuff on screen a bit and in the main menu),then switched maps. Unfortunately,it loaded correctly (ha),then crashed when I tried to switch back to fullscreen with that command. I then restarted PR and it crashed loading (fullscreen/normal mode this time) at 46% with a memory error I couldn't bring up to read as it only had a black screen with the task bar that I could get visible.It probably crashed the first time when I toggled fullscreen because it screws up the graphics (game had a black spot locked where I look probably as tall as a fifth of the screen from the left side to the middle of screen, the ground/terrain was missing or had spots missing,and the menu options are slightly off kilter), the second crash I'm not sure why it happened.It seems the ctd without errors are different each time as I just tried that again, and ctd with no error at 31% this time.

Just tried again (in normal mode), I got the error at 46% every time. It says

BF2 memory error

Memory.dll:sanity check: block size -2129682048 (2064.98 mb) doesn't seem sane

Has 3 options, cancel,try again,continue.

I clicked try again and got an error, forgot to screen shot it, but probably the same as below,but with the first errors memory block instead.

Just tried again, same error except it's block size -1065353088 (3080.00 mb) . Second error when I click try again:

BF2 memory error
Memory.dll: all aloc attempts failed for size 1065353088

Then clicking try again closes the error and bf2/PR.

Just tried the fullscreen console command again, ignoring how it screws up everything graphically, Normandy loads correctly when it's applied but not when it's fullscreen/normal.

Just tried modifying a shortcut with the +menu 1and +fullscreen 0. It didn't center properly until I moved it manually, the graphics errors in the main menu are the same as the console command but in game graphics are fine. And for some reason I got the same exact message as the second error(memory error with block 3080)when there was a memory error. So, while the console command screws the graphics,it loads fully without error.And while it looks right in fullscreen,and in shortcut induced windowed mode minus the main menu, it crashes every time. For the record, all errors and crashes have only occurred in Normandy so far. Also,it ctd'd once again with no error once more in shortcut windowed mode around 14% or so percent,possibly after 14 but before 20 or 30 percent. So the no error ctds seem sort of random. To note,the error I got the first time this happened with my first reply may have been a memory error instead of a runtime,although I'm not sure entirely.

I rebooted,gave it one more try again normally and it crashed with no error at 44% again,as before.I think I'm going to leave this be until someone has an idea about this.

crs24 wrote:Just started trying this again after rebooting. I loaded another map, used a console command (game.togglefullscreen) to try to see an error (which screwed up the stuff on screen a bit and in the main menu),then switched maps. Unfortunately,it loaded correctly (ha),then crashed when I tried to switch back to fullscreen with that command. I then restarted PR and it crashed loading (fullscreen/normal mode this time) at 46% with a memory error I couldn't bring up to read as it only had a black screen with the task bar that I could get visible.It probably crashed the first time when I toggled fullscreen because it screws up the graphics (game had a black spot locked where I look probably as tall as a fifth of the screen from the left side to the middle of screen, the ground/terrain was missing or had spots missing,and the menu options are slightly off kilter), the second crash I'm not sure why it happened.It seems the ctd without errors are different each time as I just tried that again, and ctd with no error at 31% this time.

Just tried again (in normal mode), I got the error at 46% every time. It says

BF2 memory error

Memory.dll:sanity check: block size -2129682048 (2064.98 mb) doesn't seem sane

Has 3 options, cancel,try again,continue.

I clicked try again and got an error, forgot to screen shot it, but probably the same as below,but with the first errors memory block instead.

Just tried again, same error except it's block size -1065353088 (3080.00 mb) . Second error when I click try again:

BF2 memory error
Memory.dll: all aloc attempts failed for size 1065353088

Then clicking try again closes the error and bf2/PR.

Just tried the fullscreen console command again, ignoring how it screws up everything graphically, Normandy loads correctly when it's applied but not when it's fullscreen/normal.

Just tried modifying a shortcut with the +menu 1and +fullscreen 0. It didn't center properly until I moved it manually, the graphics errors in the main menu are the same as the console command but in game graphics are fine. And for some reason I got the same exact message as the second error(memory error with block 3080)when there was a memory error. So, while the console command screws the graphics,it loads fully without error.And while it looks right in fullscreen,and in shortcut induced windowed mode minus the main menu, it crashes every time. For the record, all errors and crashes have only occurred in Normandy so far. Also,it ctd'd once again with no error once more in shortcut windowed mode around 14% or so percent,possibly after 14 but before 20 or 30 percent. So the no error ctds seem sort of random. To note,the error I got the first time this happened with my first reply may have been a memory error instead of a runtime,although I'm not sure entirely.

I rebooted,gave it one more try again normally and it crashed with no error at 44% again,as before.I think I'm going to leave this be until someone has an idea about this.

re-download (from a different site than you first did_ and Re-install the latest patch and see if you still get the same errors. Seems to me it's either a corrupt download or an OG problems messing up lower end PC's seeing as 14% can sometimes be because of OG and 45%-59% is vegetation on the surrounding terrain.

gx wrote:re-download (from a different site than you first did_ and Re-install the latest patch and see if you still get the same errors. Seems to me it's either a corrupt download or an OG problems messing up lower end PC's seeing as 14% can sometimes be because of OG and 45%-59% is vegetation on the surrounding terrain.

By OG do you mean the graphics card or something else?

The 14% was confusing as I wasn't expecting it that early and couldn't read it clearly when it was windowed,but it seems when I don't screw around with windowed mode, it always crashed around 44% with no error.When I run PR,load a map that works correctly,use the game.togglefullscreen command,the graphics screw up when it switches to windowed mode,and entering it again crashes the game when it tries to switch back to fullscreen.However for some reason when I disconnect and load Normandy locally after using the command and screwing the graphics,but don't try to fix them, it always loads Normandy correctly (ignoring the graphical errors)every time.But for some reason it seems that using it might of caused the memory errors and ctds at different percentages when trying it normally after using the fullscreen command,as I never got an error the first time I tried to get one normally,just the 44% no error ctds,same thing after restarting and trying again without using windowed mode.I'll download the patch again,and see what happens after reinstalling with it.Just a thought I had,the terrain basically all but disappearing when the graphics screw up with the console command might have something to do with why it works only then. And (im curious about this)I don't think my pc is lower end for bf2pr with windows xp64 os,6 gigs of ram, 2.67 quad core,Realtek hd audio,and the FX 580 graphics card I'm currently using (the video card I'm not so sure).

Just to note I think I used ancientdev's download link for the 0.98 patch for the installer I used to install it currently,as I didn't use moddb. So I'll try a different one.

Try this at the end of your target line " +fullscreen 0 +szx 1440 +szy 900" with out the "".