Perf problems to report in build 70289

Lobby ID: 1269041763505297771

No mods used at all.

System has two planets and two smashable moons. Zoomed in on dox formation. Top is client, bottom is sim.

I will add more info if necessary.

Can you please clarify why exactly you'd include sim there?
10FPS it's normal value for sim...

@SXX because Uber asked for it here.

I followed the instructions in this thread. They specifically said to post both screenshots of client and sim.

Your graphics card driver is out of date by six months four days. PA is highly sensitive to drivers causes poor performance if there date.

Driver update -> http://www.geforce.com/drivers/results/77224

Thank you very much for following those instructions much appreciated.

@lokiCML: Actually, those are the latest drivers. I got my drivers from the EVGA website here.

And here's a screenshot from the Programs and Features to prove that my drivers are up to date.



P.S. I played a match half an hour ago and I experienced great performance. How can my drivers be six months and four days out of date?

The first number in the date is the month, not the day. Those drivers are just over a month old.

Please refer to the image in reply #6.

I installed those drivers myself and Programs and Features states that the drivers are from 7/29/14. Therefore, it means my graphics drivers are up to date.

I know, what I'm saying is there is nothing wrong with your drivers. 7/2/2014 is July 2nd, not February 7th, which I think is where the six month confusion came from.

Can you describe exactly what the issue is? As those screens show nothing amiss.

Though if the performance is inconsistent, it is most likely a problem in your internet connection. (typically this results in choppy games, often stalling for several seconds before jumping ahead)

I can only go off of what the DirectX diagnostic tells me.

Are you sure because that is a date format? It is possible that a maximum up but then that's the fault of Microsoft. Also there could be a problem with dxdiag reporting the wrong date.

ya I'm sure, here is the date field from someone else's dxdiag

Driver Date/Size: 4/17/2014

I don't know where the mm/dd/yyyy format comes from, but I agree it is dumb

I think that's where all of the confusion arose. The Dxdiag got the driver date wrong by 27 days.

@nixtempestas: Yes, I did have server lag in a prior match. That's why I experienced freezes lasting for seconds and choppy performance. But there was little to no server lag in my recent match.

Why? I must have deleted a planet to test the performance. And it seems the more planets I build, the worse the performance becomes. Same with building Dox swarms. I zoomed in on the Dox swarm and FPS dropped to around 30.

More stuff will put more strain on both the client and server. It can be difficult to tell them apart at times, though if you are over 30 fps and it is choppy, it is most likely a server/internet problem. If its choppy and you are only doing like 10 fps, that is likely client side.

Zooming in on a dox blob shouldn't have any affect at all on server (other than the base amount for having that many dox) but will hit your client (hence the drop to 30fps).

Server performance can be a real pain to attempt to debug the cause, since it can be caused by so many different things (client or server internet connection (unlikely to be server but can be), server congestion, etc)

Mostly client lag, but almost no server lag.

Lag comes up when I zoom in on an idle or a moving army formation, but only if the army is huge (like with the Dox). The lag disappears when I zoom out to system view or I zoom in on my base.

he has this 30 fps cap maybe
i get that sometime if i zoom out to orbit and than back to planet

30 FPS cap? I don't think PA has a 30 FPS cap.

I got 60 FPS most of the time with small moving armies and system view/planet view.

@sorian: I'll be playing another test match and uploading the client screenshot as requested.

your screen has exact 30 fps

That is not proof of a fps cap. I have seen PA go 70+ fps.

@kjotak109, currently looking into DXDiag issue.