Page 1 of 1
Burning sands CTD
Posted: 2010-10-16 02:20
by crot
I dont know wtf. Every map loads, yet Burning Sands CTD with some memory error right before it finishes loading. Anyone else have this problem? I restarted comp after install, I reinstalled PR, still.
Any suggestions. I run pr on max settings.

Re: Burning sands CTD
Posted: 2010-10-16 03:44
by Lange
crot wrote:I dont know wtf. Every map loads, yet Burning Sands CTD with some memory error right before it finishes loading. Anyone else have this problem? I restarted comp after install, I reinstalled PR, still.
Any suggestions. I run pr on max settings.
Been talked about a lot in the bug forums mate, seems like quite a few people are having similar problems maybe worth a look to check there.
Re: Burning sands CTD
Posted: 2010-10-16 03:45
by Genestealer
Try lowering your settings?
Re: Burning sands CTD
Posted: 2010-10-16 03:46
by M_Striker
Ive got the same problem.. crashes in the map, and BF2 memory error. I never used to get this on 4km maps
Re: Burning sands CTD
Posted: 2010-10-16 04:27
by crot
lol I lowered settings to medium and it loaded. Although the graphics look like utter sh*t.

Re: Burning sands CTD
Posted: 2010-10-16 06:25
by PLODDITHANLEY
Same here.
Re: Burning sands CTD
Posted: 2010-10-16 08:16
by joethepro36
Everyone is currently crashing due this CTD error as far as I know. It'll get fixed soon so don't worry too much about it. If you want to help out the DEVs post in the bugs forum about the situation when it crashed, may help them find the solution.
Re: Burning sands CTD
Posted: 2010-10-16 10:22
by Jigsaw
joethepro36 wrote:Everyone is currently crashing due this CTD error as far as I know. It'll get fixed soon so don't worry too much about it. If you want to help out the DEVs post in the bugs forum about the situation when it crashed, may help them find the solution.
This is not true, as a matter of fact I played Burning Sands on all high yesterday and it worked flawlessly, so please avoid generalising.
Locking this thread as it's in the wrong section and has been reported already.