Memory Leak
Edger
Join Date: 2003-07-27 Member: 18484Members
in Tech Support
<div class="IPBDescription">Used to run fine...</div> NS ran fine for the past year or so. After I got a video card upgrade (TI 4200 AGP 8x), NS just started running really crappy, FPS wise. With netgraph, I'd get like 15-20 FPS 5 minutes into the game. This never happend on a my old video card (Geforce 2). I know for a fact that its not my video card or computer, because it ran fine before. Everything else runs fine, I have a higher FPS in UT2003 than in NS. I think it starts out fine when a new round starts, but after 5 minutes, it runs really crappy. Any suggestions?
<u>Spec</u>
1.8 Ghz P4 Compaq
TI 4200 Geforce 4 AGP 8x
512 RAM
P.S. Its not something running in the backround like WinAMP or something.
<u>Spec</u>
1.8 Ghz P4 Compaq
TI 4200 Geforce 4 AGP 8x
512 RAM
P.S. Its not something running in the backround like WinAMP or something.
Comments
First do a fresh install of all the drivers.
Older cards like a geforce 2 or My rage 128 32mb pro are actaully optimized for older games. With ns, i can have 20 turrets a phase-gate, all in-veiw on ns_bast and i would get 30fps. Normally (walkin around in base) i get 60fps. <!--emo&???--><img src='http://www.unknownworlds.com/forums/html/emoticons/confused.gif' border='0' style='vertical-align:middle' alt='confused.gif'><!--endemo-->
for general purpose, pls use the edit button mate (don't bother with bumps if we don't respond we either just havn;t gotten to you or don't know a solution)
ooook(disc world any one?)ay:
1) bind x invnext or invprevious, dont remember wich is broken (basicaly the front end wont do thisd you have to)
2) you ran the stress test thingy and it happened there also?
HAve you tried any other games?
to me this honestly sounds like hardware bugs, the 3 solutions to try for this are:
1) Reseat the card (simply pull it out of the MoBo and all connecters out of it and then put it all back to gether)
2) Flash Firmware (check the comps webbie to see if they have a firmware upgrade)
3) Complain to the comp and get a new one.
Note, I am not saying this is necesarily what is wrong it simply sounds like it to me (happens in multiple environments, drivers uptodate etc)