I know alot of people have had issues with the new maps running slow but I've been having a different sort of problem.(I think) Really complex new maps (mostly the dense jungle map who's name eludes me at the moment) start out running perfectly. I can move around, look at all the plants and fancy scenery all I want and still have an impressive fps. But after about 20 or so minutes into the map things change. Suddenly when I look at dense foliage, my framerate is noticably lower. About 5 minutes later I can't look at bushes period. 5 more minutes later, I have to stare at the floor to get a framerate above the single digits.(which isn't very good for fighting)
Is this the general issue most people face(starts out fast but starts slowing down later for no reason) or could this be like a "memory leak"(I don't know much about comp terminology so be kind)? If so is there a way I could solves this without going from high to super low settings or cramming another gig into my comp?
check your ram usage after 5 minutes of playing and compare it to what it is after 30 minutes of playing and you can see if there is a memory leak. If it more or less stays the same than there is no memory leak. I don't have any of the problems you describe though.
I know alot of people have had issues with the new maps running slow but I've been having a different sort of problem.(I think) Really complex new maps (mostly the dense jungle map who's name eludes me at the moment) start out running perfectly. I can move around, look at all the plants and fancy scenery all I want and still have an impressive fps. But after about 20 or so minutes into the map things change. Suddenly when I look at dense foliage, my framerate is noticably lower. About 5 minutes later I can't look at bushes period. 5 more minutes later, I have to stare at the floor to get a framerate above the single digits.(which isn't very good for fighting)
Is this the general issue most people face(starts out fast but starts slowing down later for no reason) or could this be like a "memory leak"(I don't know much about comp terminology so be kind)? If so is there a way I could solves this without going from high to super low settings or cramming another gig into my comp?
I have no problem with Operation Liliput, has been as smooth as anything so far, havent had a crash there either. I have experienced some choppyness on Fall Gelb, yesterday it ran smooth with about 55 people, but then it crashed.
Quote:
Originally Posted by George Bernard Shaw
No man ever believes that the Bible means what it says; he is always convinced that it says what he means.
I have no problem with Operation Liliput, has been as smooth as anything so far, havent had a crash there either. I have experienced some choppyness on Fall Gelb, yesterday it ran smooth with about 55 people, but then it crashed.
It's not lilliput. It's the other one with the really lush green jungles and screaming monkies.
My specs are:
Pentium M 1.5 ghz
1 gig ram
ATI Mobility X300 128 mb
an 80 gig HD(but the game itself is on a USB 150 gig external HD)
Ditto here, no issues at all with the really dense jungle maps (Lilliput, Tulagi.) Fall Gelb is a bit choppy on a full 56-player server (AMD 3600, 2 gb memory, 7800 card.)
Pentium M 1.5 ghz
1 gig ram
ATI Mobility X300 128 mb
an 80 gig HD(but the game itself is on a USB 150 gig external HD)
Honestly, your rig is a little "old fashioned" for the new maps.
Time moved on, and the fanmappack really made the most out of Forgotten Hope, so its no wonder that the system requirements are a little higher now.
You might get a good boost by adding more ram, and for fucks sake, move your BF42 off of the usb drive.
Defragmenting the drives and kidding around with the swapfile (not, NEVER move it to the usb drive) might help a little, too.
if i had to guess i would say it sounds like a over-heating issue that happens when something is pushed to its limits. which these maps will certainly do with your specs.
check all your temps from start, then when you get the slow down.
You might get a good boost by adding more ram, and for fucks sake, move your BF42 off of the usb drive.
Defragmenting the drives and kidding around with the swapfile (not, NEVER move it to the usb drive) might help a little, too.
Good luck !
JW
Good points. Check Virtual memory settings as well. "Lock" your swapfiles: don't let Windows decide for you.
This site is part of the Defy Media Gaming network
The best serving of video game culture, since 2001. Whether you're looking for news, reviews, walkthroughs, or the biggest collection of PC gaming files on the planet, Game Front has you covered. We also make no illusions about gaming: it's supposed to be fun. Browse gaming galleries, humor lists, and honest, short-form reporting. Game on!
Forgotten Hope General Yib-Yab (Off Topic) 
New maps memory leaks. 
.gif "Sad at the sad color")
Linear Mode
