First of all, I read the other low FPS thread and didn't work for me.
Since 2 o 3 months ago, I'm suffering from low FPS. When I'm near too much action (other players, explosions, effects, etc), the FPS count decrease from about 60 to less than 10. The game cannot be played that way, the screens goes frame by frame and sound gets cut.
I have a P4 2.4GHZ, 1GB memory, ATI X850 PRO, Windows XP.
I have installed the latest video drivers.
Internet connection works fine, I have a 5Mb broadband connection.
I play NS since it was released, its first version. This is the first time I'm having this problem.
Now I can play TFC and CS and they work perfectly. The problem is only with NS.
Any help will be appreciated.
Full Version: Low FPS only in NS mod
TFC and CS are not as system intensive as NS.
is your FPS actually going from 60 -> 10? (net_graph 3 to tell us exact fps, choke/loss/whatnot)
an idea of what all you have tried would help.
Do you remember changing anything when this first started?
is your FPS actually going from 60 -> 10? (net_graph 3 to tell us exact fps, choke/loss/whatnot)
an idea of what all you have tried would help.
Do you remember changing anything when this first started?
As I said, I've been playing NS since its first version and with less performant PCs than the one I currently have. Never had this problem. I can't remember modifying something, I just know this started from one day to another. I was thinking about unistalling and reinstalling NS.
QUOTE(NS-SkorpioN @ Jan 19 2008, 04:55 PM) 
First of all, I read the other low FPS thread and didn't work for me.
Since 2 o 3 months ago, I'm suffering from low FPS. When I'm near too much action (other players, explosions, effects, etc), the FPS count decrease from about 60 to less than 10. The game cannot be played that way, the screens goes frame by frame and sound gets cut.
I have a P4 2.4GHZ, 1GB memory, ATI X850 PRO, Windows XP.
I have installed the latest video drivers.
Internet connection works fine, I have a 5Mb broadband connection.
I play NS since it was released, its first version. This is the first time I'm having this problem.
Now I can play TFC and CS and they work perfectly. The problem is only with NS.
Any help will be appreciated.
Since 2 o 3 months ago, I'm suffering from low FPS. When I'm near too much action (other players, explosions, effects, etc), the FPS count decrease from about 60 to less than 10. The game cannot be played that way, the screens goes frame by frame and sound gets cut.
I have a P4 2.4GHZ, 1GB memory, ATI X850 PRO, Windows XP.
I have installed the latest video drivers.
Internet connection works fine, I have a 5Mb broadband connection.
I play NS since it was released, its first version. This is the first time I'm having this problem.
Now I can play TFC and CS and they work perfectly. The problem is only with NS.
Any help will be appreciated.
I got the same problem.
Only in NS-MOD.
My CS works perfectly.
Only in NS my FPS gets from 100 -> to 50 ot 60. (As Scropion said, when im in much action)
When the FPS gets to 50 i cant move my mouse.. ir freeze's. (Its no the mouse problem)
And thats really annoying. Cant AIM properly.
I got ATI Radeom 9550 / x1050 Series Secondary, 512mbRAM, Windows XP, 2.0GHz Have the latest Driver aswell.
So post anything that could help.
Thx :o
ok, 50 FPS is 100% acceptable (it is actually really damn good). Hell, if I remember correctly, GldSrc doesn't render above 60 FPS (it lies when it says it does).
So, net_graph 3 to let us know wth else is going on.
Oh, and try setting the priority of hl.exe to high, your problem sounds like common one that is fixed by that. (check the sticky thread about common problems)
And for NS-SkorpioN, unfortunately it sounds like the first thing would be to try a reinstall of NS.
If you have tried all the tweaks, and other games run fine (especially as you tested with TFC and CS, both HL based games), then it has got to be a sour install.
you might even want to try re downloading the game.
either way, good luck.
So, net_graph 3 to let us know wth else is going on.
Oh, and try setting the priority of hl.exe to high, your problem sounds like common one that is fixed by that. (check the sticky thread about common problems)
And for NS-SkorpioN, unfortunately it sounds like the first thing would be to try a reinstall of NS.
If you have tried all the tweaks, and other games run fine (especially as you tested with TFC and CS, both HL based games), then it has got to be a sour install.
you might even want to try re downloading the game.
either way, good luck.
No I know EXACTLY what he means! Same for me! I was able to play just fine but it seems the one of the latest Steam updates or something has changed something. I don't understand exactly. All I can say is what I have noticed and Sandman[SA] has noticed the same thing! It is not our settings or our computers! On certain areas of maps my fps drop drastically! No change in settings or configs or drivers or anything helps! And I didn't do anything different for things to go like this!
Sandman doesn't get the drop like I do in FPS as his system is way better but even he says in those EXACT SAME AREAS of those maps, he says his game is stuttering! And there is no excuse!
What is up with NS lately??
I have net_graph 3 set and I took screenshots. I will have to make the images into an animation so you can see what I mean .. see how the fps drop when looking at certain spots and then comes back up when I look somewhere else.
Sandman doesn't get the drop like I do in FPS as his system is way better but even he says in those EXACT SAME AREAS of those maps, he says his game is stuttering! And there is no excuse!
What is up with NS lately??
I have net_graph 3 set and I took screenshots. I will have to make the images into an animation so you can see what I mean .. see how the fps drop when looking at certain spots and then comes back up when I look somewhere else.
With both of you running ATI cards, I'm inclined to think it's a driver problem. Have you tried installing a previous version of the ATi drivers?
QUOTE(SnappyCrunch @ Jan 25 2008, 10:48 PM)
With both of you running ATI cards, I'm inclined to think it's a driver problem. Have you tried installing a previous version of the ATi drivers?
I have tried every driver..
Still the problem appears..
QUOTE(smile112 @ Jan 30 2008, 08:42 AM)
I have tried every driver..
Still the problem appears..
Still the problem appears..
I'm not an ati user fyi, but hope helps.
~userconfig.cfg
ati_npatch "0"
gl_cull "1"
fps_max "101"
fps_modem "100"
ATi performance with NS is pretty bad, I've had them forever. Using older drivers helps quite a bit, the newer ones crash many games on startup and I actually get better performance with ones from a year ago. Stick with NVidia on your next buy.
yeah same thing. my geforce 4mx 64mb outperforms my ati 9650 128mb.
also noticed the same thing when firing or blinking, i lose control over all movements; aiming, walking, jumping, etc.. at any rate i'm definitely not buying ati again. because tbh steam game performance is all i care about.
also noticed the same thing when firing or blinking, i lose control over all movements; aiming, walking, jumping, etc.. at any rate i'm definitely not buying ati again. because tbh steam game performance is all i care about.
QUOTE(commofdoom @ Jan 31 2008, 11:27 AM)
yeah same thing. my geforce 4mx 64mb outperforms my ati 9650 128mb.
also noticed the same thing when firing or blinking, i lose control over all movements; aiming, walking, jumping, etc.. at any rate i'm definitely not buying ati again. because tbh steam game performance is all i care about.
also noticed the same thing when firing or blinking, i lose control over all movements; aiming, walking, jumping, etc.. at any rate i'm definitely not buying ati again. because tbh steam game performance is all i care about.
Those problems are a known issue with NS actually.
The work around is:
use +Movement instead of the actual attack skill for blink and leap.
if you are having problems with the mouse 'lagging' then you need to set the hl.exe process to 'high' priority.
or set it to low, works for me and I have to do it every time I play. I'll try high the next time I feel like playing.
Issue has been solved for me:
If you are having similar trouble try downgrading to the catalyst 7.9 drivers, they do not have this issue.
I have a similar issue and nothing I have done has resolved it.
Here is the r_speeds output from the area of co_prime with those weird tubes:
172fps 2 ms 662 wpoly 1680 epoly
175fps 2 ms 662 wpoly 1680 epoly
167fps 18 ms 662 wpoly 1680 epoly
46fps 2 ms 662 wpoly 1680 epoly
166fps 2 ms 662 wpoly 1680 epoly
173fps 1 ms 662 wpoly 1680 epoly
172fps 1 ms 662 wpoly 1680 epoly
Where is that extra 16ms coming from?
It doesn't happen all the time but certain areas of certain maps bring this on.
Specs:
---------
Intel Core2 Duo E4300
ASRock 4Coredual vsta motherboard
Sapphire Radeon X1950 XT 256MB PCI-E
2048MB PC5400 DDR2 Dual channel
Sound blaster live
Windows XP Home
If you are having similar trouble try downgrading to the catalyst 7.9 drivers, they do not have this issue.
I have a similar issue and nothing I have done has resolved it.
Here is the r_speeds output from the area of co_prime with those weird tubes:
172fps 2 ms 662 wpoly 1680 epoly
175fps 2 ms 662 wpoly 1680 epoly
167fps 18 ms 662 wpoly 1680 epoly
46fps 2 ms 662 wpoly 1680 epoly
166fps 2 ms 662 wpoly 1680 epoly
173fps 1 ms 662 wpoly 1680 epoly
172fps 1 ms 662 wpoly 1680 epoly
Where is that extra 16ms coming from?
It doesn't happen all the time but certain areas of certain maps bring this on.
Specs:
---------
Intel Core2 Duo E4300
ASRock 4Coredual vsta motherboard
Sapphire Radeon X1950 XT 256MB PCI-E
2048MB PC5400 DDR2 Dual channel
Sound blaster live
Windows XP Home
We have a LAN PARTY.
we have a LOTS of machines . maybe around 100 differents.
from P3 to P5. ( i mean Crossfires, SLIs )
The NS need a LOTS more NAKED power, than a COD2.
Here is an OPTIMAL template: if u have a WELL maintenaced P3 with VOODOO 5
the NS reach 99 fps in case of 30 Players in LAN.
(of course this is not a SERVER, only a client.)
(of course Voodoo5 HARD, or impossible to beat with ati 9800, and gef 4-5)
U guys have a lots MORE POWER in CPU, and take the FPS problem?
paymore attention on to your PC's performance.
we have a LOTS of machines . maybe around 100 differents.
from P3 to P5. ( i mean Crossfires, SLIs )
The NS need a LOTS more NAKED power, than a COD2.
Here is an OPTIMAL template: if u have a WELL maintenaced P3 with VOODOO 5
the NS reach 99 fps in case of 30 Players in LAN.
(of course this is not a SERVER, only a client.)
(of course Voodoo5 HARD, or impossible to beat with ati 9800, and gef 4-5)
U guys have a lots MORE POWER in CPU, and take the FPS problem?
paymore attention on to your PC's performance.
Natural selection is a nice but resource hungry half-life modification :|--< <3 i love natural selection.
QUOTE(nizb0ag @ Feb 18 2008, 01:05 AM)
... resource hungry half-life modification...
naked true
Here you can see how the FPS move down until 4 FPS in game.
I had this PC from Nov'2004 and installed everything then. Is it possible that a large Windows registry could cause this and I need to reinstall the OS?
I had this PC from Nov'2004 and installed everything then. Is it possible that a large Windows registry could cause this and I need to reinstall the OS?
QUOTE(NS-SkorpioN @ Jan 19 2008, 12:55 PM)
Internet connection works fine, I have a 5Mb broadband connection.
So? What matters in online games isn't so much your average bandwidth being high, but that you have high QoS. (quality of service)
Case in point, I lived for a time at an apartment complex where my ISP had nodes overloaded past design capacity (i.e.: most were at 95%!), this resulted in ridiculous lag spikes in the game every 3 to 7 seconds that would last anywhere from 50ms to 1000ms. This resulted in online games like NS being pretty much unplayable. My bandwidth would appear to be a nice 8.2Mbps downstream and 1.1Mbps upstream, but this didn't consider the gaps in service. This won't be noticeable in text-chat or web browsing applications, but is PAINFULLY obvious in other apps like games, live video & voice chat, and streaming video or music.
Poor QoS from your ISP and programs running in the background (spyware or viruses possible too) are by far the most common and the most significant in interfering with online multiplayer gaming.
Remember that residential ISP broadband likes to advertise their average downstream bandwidth with no comments on QoS.
Turn on netgraph so you can see that data over time. The instantaneous data doesn't mean much.
Although the 4 frames per second is crap... still need to see if it's spiking or continuous.
What do you have running in the background?
And if you still have time, run dxdiag or 3DMark08.
QUOTE(Savage UK)
fps_max
While this setting will no longer improve your connection it does help stop the confusion between connection lag and graphics related lag when, for example, jumping from 85 FPS to 23 FPS. Set this by monitoring your FPS while playing using net_graph 3 or cl_showFPS "1", then set fps_max to your average steady FPS
rate
This controls network packets so that your connection bandwidth does not get saturated, setting is for maximum bytes per second. Note that with 1.1.04 or above and a Stac/Microsoft compressed connection you can no longer use higher rates than normal for your connection type, connection tweak tables have been adjusted to reflect that. See net_graph for a guide on how to adjust this setting or try the suggested settings that appear at the foot of this page.
cl_cmdrate
In HalfLife patches prior to 1.1.0.0 your FPS governed how many gameworld updates you sent to the server, this is no longer the case in 1.1.0.0 and above. Similar to cl_maxpackets in Quake3 this setting restricts the number of packets being sent to the server by your client and can be used to help connection bandwidth related problems for those with low upload bandwidth. Note that 56K modems, while downloading at up to 56000 BPS, only upload at 33600 BPS or less. You may wish to experiment with a higher or lower setting based on your connection type, for example 40 or higher for a digital connection.
Further tweaking, try to set cl_cmdrate to equal your average framerate or your fps_max setting or a divisor of it without saturating your upstream bandwidth. Example, if you are currently at fps_max "76" then try a cl_cmdrate value of 38 or 76 for a digital connection.
cl_updaterate
Similar to snaps setting in Quake3, the cl_updaterate setting is used to calculate how many gameworld updates you receive from the server. See net_graph for a guide on how to adjust this setting.
cl_lc
To use this setting the server and modification must support lag compensation. On servers that have lag compensation enabled this setting toggles its use of lag compensation for the client, 1 to enable, 0 to disable. When set to 1 the server will take into account your ping when deciding if you hit your target or not. If you have a very low ping or wish the older style of play then set this to 0.
cl_lw
This setting determines how weapons fire is controlled, for example with regard to sounds and animation. When set to 0 the client will perform as it used to prior to 1.1.0.0, the server returns/confirms weapon related sounds and animation fire information.
If you set this to 1 the clients weapon sound and animation will all happen client side as soon as you press fire. It should be noted that when set to 1 the animations and marks displayed are determined client side, as a result they may not be an accurate representation of where you are actually hitting.
It should be noted that the server always determines if you have hit your target or not, only weapon related sounds and animation are controlled by cl_lw.
You may find it useful to bind different settings of cl_lw and cl_lc for different weapons. It is very important to note that if you use a setting of 0 for cl_lw that the cl_lc setting should be set to 0. While cl_lc is supposed to be ignored when cl_lw is set to 0, some users have reported that manually setting to cl_lc to 0 was needed.
cl_lb
Very similar to cl_lw, however this setting determines how blood and damage trails are displayed. When set to 0 the client will perform as it used to prior to 1.1.0.0, It should be noted that when set to 1 the animations and marks displayed are determined client side, as a result they may not be an accurate representation of where you are actually hitting.
pushlatency
You should no longer need to adjust this setting and our suggestion is to leave it at default. This affects the client prediction code, depending on the modification 0 or -1000 is default. When using 1.1.0.0 or above default is the suggested setting if you have set cl_lc and/or cl_lw to 1.
To reiterate, altering pushlatency from the default is not recommended if you are taking advantage of lag compensation commands mentioned above, if however you do wish to alter pushlatency then there are two options. Set it to -1000 and let HalfLife do full prediction as it will ignore anything that is higher than your current latency or try setting your pushlatency to a negative value that is around 50% to 100% of your average ping. Example if you are pinging 200 on average then try a setting of -100. If you are unsure leave this at its default value.
net_graph
When setting this to 3 or 1 you will see a figure display(3) or graph display(1) appear at the base of your screen. On the graph display, just below the numeric readout, green lines mean packets are being received okay, yellow that rate capping is causing your client to reject packets and red that the packet was lost. If you have steady flat green line then all is well. In the case of long rising/falling green hills lower your rate or decrease your cl_updaterate, for yellow increase your rate. If you have a lot of red then change ISP or server. If you have to play on the server or use the ISP then try adjusting cl_resend or cl_cmdbackup to compensate for the lost packets.
cl_cmdbackup
cl_resend
These settings determine if duplicate commands(cl_cmdbackup) or packets(cl_resend) are sent, if a command gets lost then a 'backup command' in the latest packet may still be received. If you have an excellent connection with very little or no packetloss at all then try setting cl_cmdbackup to 0 and raising cl_cmdrate. However, as with all settings experiment to see which is best suited for your connection - See net_graph for a guide on how to determine if you need to adjust this setting.
cl_download_ingame
This determines if downloads are allowed during a multiplayer game. this to 0 to stop downloading of decals etc. while playing.
While this setting will no longer improve your connection it does help stop the confusion between connection lag and graphics related lag when, for example, jumping from 85 FPS to 23 FPS. Set this by monitoring your FPS while playing using net_graph 3 or cl_showFPS "1", then set fps_max to your average steady FPS
rate
This controls network packets so that your connection bandwidth does not get saturated, setting is for maximum bytes per second. Note that with 1.1.04 or above and a Stac/Microsoft compressed connection you can no longer use higher rates than normal for your connection type, connection tweak tables have been adjusted to reflect that. See net_graph for a guide on how to adjust this setting or try the suggested settings that appear at the foot of this page.
cl_cmdrate
In HalfLife patches prior to 1.1.0.0 your FPS governed how many gameworld updates you sent to the server, this is no longer the case in 1.1.0.0 and above. Similar to cl_maxpackets in Quake3 this setting restricts the number of packets being sent to the server by your client and can be used to help connection bandwidth related problems for those with low upload bandwidth. Note that 56K modems, while downloading at up to 56000 BPS, only upload at 33600 BPS or less. You may wish to experiment with a higher or lower setting based on your connection type, for example 40 or higher for a digital connection.
Further tweaking, try to set cl_cmdrate to equal your average framerate or your fps_max setting or a divisor of it without saturating your upstream bandwidth. Example, if you are currently at fps_max "76" then try a cl_cmdrate value of 38 or 76 for a digital connection.
cl_updaterate
Similar to snaps setting in Quake3, the cl_updaterate setting is used to calculate how many gameworld updates you receive from the server. See net_graph for a guide on how to adjust this setting.
cl_lc
To use this setting the server and modification must support lag compensation. On servers that have lag compensation enabled this setting toggles its use of lag compensation for the client, 1 to enable, 0 to disable. When set to 1 the server will take into account your ping when deciding if you hit your target or not. If you have a very low ping or wish the older style of play then set this to 0.
cl_lw
This setting determines how weapons fire is controlled, for example with regard to sounds and animation. When set to 0 the client will perform as it used to prior to 1.1.0.0, the server returns/confirms weapon related sounds and animation fire information.
If you set this to 1 the clients weapon sound and animation will all happen client side as soon as you press fire. It should be noted that when set to 1 the animations and marks displayed are determined client side, as a result they may not be an accurate representation of where you are actually hitting.
It should be noted that the server always determines if you have hit your target or not, only weapon related sounds and animation are controlled by cl_lw.
You may find it useful to bind different settings of cl_lw and cl_lc for different weapons. It is very important to note that if you use a setting of 0 for cl_lw that the cl_lc setting should be set to 0. While cl_lc is supposed to be ignored when cl_lw is set to 0, some users have reported that manually setting to cl_lc to 0 was needed.
cl_lb
Very similar to cl_lw, however this setting determines how blood and damage trails are displayed. When set to 0 the client will perform as it used to prior to 1.1.0.0, It should be noted that when set to 1 the animations and marks displayed are determined client side, as a result they may not be an accurate representation of where you are actually hitting.
pushlatency
You should no longer need to adjust this setting and our suggestion is to leave it at default. This affects the client prediction code, depending on the modification 0 or -1000 is default. When using 1.1.0.0 or above default is the suggested setting if you have set cl_lc and/or cl_lw to 1.
To reiterate, altering pushlatency from the default is not recommended if you are taking advantage of lag compensation commands mentioned above, if however you do wish to alter pushlatency then there are two options. Set it to -1000 and let HalfLife do full prediction as it will ignore anything that is higher than your current latency or try setting your pushlatency to a negative value that is around 50% to 100% of your average ping. Example if you are pinging 200 on average then try a setting of -100. If you are unsure leave this at its default value.
net_graph
When setting this to 3 or 1 you will see a figure display(3) or graph display(1) appear at the base of your screen. On the graph display, just below the numeric readout, green lines mean packets are being received okay, yellow that rate capping is causing your client to reject packets and red that the packet was lost. If you have steady flat green line then all is well. In the case of long rising/falling green hills lower your rate or decrease your cl_updaterate, for yellow increase your rate. If you have a lot of red then change ISP or server. If you have to play on the server or use the ISP then try adjusting cl_resend or cl_cmdbackup to compensate for the lost packets.
cl_cmdbackup
cl_resend
These settings determine if duplicate commands(cl_cmdbackup) or packets(cl_resend) are sent, if a command gets lost then a 'backup command' in the latest packet may still be received. If you have an excellent connection with very little or no packetloss at all then try setting cl_cmdbackup to 0 and raising cl_cmdrate. However, as with all settings experiment to see which is best suited for your connection - See net_graph for a guide on how to determine if you need to adjust this setting.
cl_download_ingame
This determines if downloads are allowed during a multiplayer game. this to 0 to stop downloading of decals etc. while playing.
Hi all
Sorry for reviving a somewhat dead thread, but it didn't seem to have a solution, and I am also suffering from the same issues.
My FPS will typically hover around 60 fps (ya, vsync is on, but i had it off and the problem remained), but will drop to ~30 and even down to 20 at times of high action, or when joining a team on servers that make sure of the autohelp text windows that flood your screen. I have reviewed multiple other threads that reported similar issues and have tried everything I saw. Here are the deets:
Windows XP X64
AMD64 3500+
1GB RAM
nVidia 8600 GTS (256MB)
No AV/FW software installed on this machine. That would be silly.
Config.cfg (truncated for relevance):
------------------------------------------
cl_cmdrate "30"
cl_dynamiclights "1"
cl_forcedefaultfov "0"
cl_gammaramp "0"
cl_highdetail "1"
cl_himodels "0"
cl_hudmapzoom "2"
cl_updaterate "20"
fps_max "100"
Steps I have already taken:
Enabled Triple Buffering
Disabled Antisotropic filtering
Disabled In-game Steam Community
Set hl.exe process priority to Low
Set hl.exe process priority to High
Killed all other process I could
Reinstalled NS (deleting the ns folder after uninstalling)
I've been monitoring the issue with net_graph 2, as it provides a graph of your PC's performance/demand (tho i'm not sure specifically what it details)
The first image, you can see, is normal; i'm facing a wall, and not much is goin on around me.
The second image, i'ld just walked into the hive, with fellow marines, and it's full of aliens and structures.
While not examplary performance loss, you can see in the net_graph, that i've lost about 20fps, and the pretty graph is goin all hay-wire. It's quite a debilitating problem, even if this example doesn't really show it. =P
So, I'm not too sure what else to try at this point. But if anyone has any ideas, I would love to hear from you.
Edit: and now a really annoying thing; since reinstalling it, I now have the issue mentioned above where each launch of NS, i have to set the priority to high or "above normal" otherwise i only get 20fps... before i reinstalled, i never had to do that. Weird... Must have something to do with the 32bit emulator....
Sorry for reviving a somewhat dead thread, but it didn't seem to have a solution, and I am also suffering from the same issues.
My FPS will typically hover around 60 fps (ya, vsync is on, but i had it off and the problem remained), but will drop to ~30 and even down to 20 at times of high action, or when joining a team on servers that make sure of the autohelp text windows that flood your screen. I have reviewed multiple other threads that reported similar issues and have tried everything I saw. Here are the deets:
Windows XP X64
AMD64 3500+
1GB RAM
nVidia 8600 GTS (256MB)
No AV/FW software installed on this machine. That would be silly.
Config.cfg (truncated for relevance):
------------------------------------------
cl_cmdrate "30"
cl_dynamiclights "1"
cl_forcedefaultfov "0"
cl_gammaramp "0"
cl_highdetail "1"
cl_himodels "0"
cl_hudmapzoom "2"
cl_updaterate "20"
fps_max "100"
Steps I have already taken:
Enabled Triple Buffering
Disabled Antisotropic filtering
Disabled In-game Steam Community
Set hl.exe process priority to Low
Set hl.exe process priority to High
Killed all other process I could
Reinstalled NS (deleting the ns folder after uninstalling)
I've been monitoring the issue with net_graph 2, as it provides a graph of your PC's performance/demand (tho i'm not sure specifically what it details)
The first image, you can see, is normal; i'm facing a wall, and not much is goin on around me.
The second image, i'ld just walked into the hive, with fellow marines, and it's full of aliens and structures.
While not examplary performance loss, you can see in the net_graph, that i've lost about 20fps, and the pretty graph is goin all hay-wire. It's quite a debilitating problem, even if this example doesn't really show it. =P
So, I'm not too sure what else to try at this point. But if anyone has any ideas, I would love to hear from you.
Edit: and now a really annoying thing; since reinstalling it, I now have the issue mentioned above where each launch of NS, i have to set the priority to high or "above normal" otherwise i only get 20fps... before i reinstalled, i never had to do that. Weird... Must have something to do with the 32bit emulator....
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.