EVE General Discussion

I'm a new player here.
I expected a lot of problems concerning the learning curve of the game, but my real problem atm is another.
Perfomance.

It's about Interval.
From what i understand its another name for vsync.
Im running everything maxed out, and i get around 200~300fps with interval set to immediate.
While that would run the game smoothly, it's really bad for my GPU temperature, it would overheat very fast.

The logical solution would be set it to Interval 1 and have the game at the perfect 60fps.
But this is not happening.
While the game stays a solid 60 fps in most places, it drops to 40fps in a lot of areas for no reason.
For example, the first combat of the tutorial, where you fight to enemy ships, it drops to 40 and stays at this framerate for no reason.
It makes no sense. Being able to put 300fps, getting 40 should never happen.
So the choice atm is between bad perfomance or overheating the GPU.

Does anyone had/have this problem and can help me?


( Sorry for the bad English btw )

Maybe, i'm not sure.
It happens in a lot of places.

Dust clouds, gas clouds, pretty graphic stuff like that hands out a much bigger fps hit than you might imagine, I believe especially if you have shader quality at high. When they first put in the new model clouds, it crashed my $3000 gaming rig when I jumped into a grid with one.

I know that.
But, like i said, this is not a problem for me with the fps unlocked.
The problems seems to be with the interval, it appears to hit the perfomance even worse then normal vsync.

just install another fan.... easy to do and about 50 quid for a decent one. Also you can never go wrong with more cooling.

I tried that alredy before posting here.
No change.
And yeah, the places where the FPS drops with interval immediate. It never goes under 150.

Errr no.
You're not up to date.

Okay.

I just realised a mistake i shouldn't have made in the first place.

Thinking in terms of "fps" is bull.
What's relevant is spf.


What i'm talking about is that if you run a game and see 1000fps
and then see a drop down to 500fps, you see a huge loss in regards to fps,
but actually it only added 1msec worth of computation.

If a frame needs two msec, you'll drop down to 250fps.

At 60fps, the computer has 16msec per frame. (1000/60=16.66..7)

The computation is 1000 / fps = msec, so at 60fps your computer
needs around 16msec to compute a frame,
or is limited to 16msec to compute a frame.


Sooo ... you have to see this in a different light. Not in terms of fps,
but msec wasted during each frame.


What VSync does is letting the gfx only push frames out during
what was called "vertical retrace" during the era of CRTs,
but the concept still applys nowadays anyway.


The image is only getting displayed in the short amount of time
the screen doesn't paint a new image, which avoids the chance
of actually painting two different images onto the screen at the same time.
(like ... 50:50 or 30:70 etc etc. it's called "tearing" iirc)


This means that there isn't actually any change
in how long it takes for your gfx to render an image and you will always see the drop in fps,
simply because fps are meaningless and your gfx simply needs more msec in specific environments.


This makes an awfull lot of sense for it being 0322am here
and i might actually be completely wrong,
although i have an msec counter running when i'm coding.

Why not?

it's probably this. my system is also uber, yet goes down to the 40s in gas clouds.