LOW FPS - GTX 660 Ti I5 2500K ~13 fps in towns

Quote:

---

Originally Posted by Prk

I have..
GFX: 660-ti 3GB
CPU: i5 3.4-3.6
RAM: 16GB
STORAGE: SSD

I run @ 60fps constant, so it could possibly be...
Drivers, Registry, Corrupted Install, Hm

---

60fps constant? What black magic are you using there as in the towns you WILL be dropping into the 30's/40's if running anything higher than 'High' settings...

Quote:

---

Originally Posted by Driium

I've got to agree with Gl0ry,

Anyone who claims to be getting 60FPS in towns or under the same circumstances several people are seeing the same drop are:

1) Running at the lowest possible settings. Or lying.
2)Not monitoring their FPS and not noticing the apparent drops.
3)Needs to start mass producing their rigs to sell on ebay as FFXIV machines because you've managed to put together a rig that meshes with this game perfectly somehow. You'll make millions.

Its not just fps dropping when panning/ looking towards fates/aetherite hubs from a miles aways, even modest fps drops down to 40 FPS (Which should still look smooth) looks stuttery. I myself am using an I7 960 @ 3.6Ghz paired with a GTX 770, as well as an I7 3770K with a gtx 760 the fps drop is exactly the same when comparing the two under the same circumstances side by side.

There is a distinct difference between a smooth drop in fps down to 30 which I can acknowledge when in densely populated areas (Which is normal and tolerable), And the stuttery inconsistent frame rate mess that some of us are experiencing despite having VERY capable hardware setups.

---

I'm running crossfired Radeon HD 7870's and have EXACTLY the same experiences - I see maximum frame rates around 120fps, but the 'lows' are saddening, especially when they dip sub 30fps occasionally - again, disabling crossfire results in improved performance when the low FPS hit. If you run with fraps or afterburner active its very apparent that the dual card setups aren't being utilised @ only 40-60% utilisation per card at any one time.

Question are any of you trying to override the aa settings for in game or enhance aa settings in game that have the turning the camera issue? Cause i was able to recreate your tanking in fps by forceably changing the aa settings and then the problem presented itself soon as i turned it off its pretty normal. it would happen in town .. Slightly happen anywhere else..

Quote:

---

Originally Posted by JamieLee

Question are any of you trying to override the aa settings for in game or enhance aa settings in game that have the turning the camera issue? Cause i was able to recreate your tanking in fps by forceably changing the aa settings and then the problem presented itself soon as i turned it off its pretty normal. it would happen in town .. Slightly happen anywhere else..

---

The client doesn't recognize FSAA style driver commands so super sampling might be a moot point.
If anyone has FXAA or Morphological AA turned on simultaneously with in-game anti aliasing, I suppose they could conflict in some cases. It does make you wonder if AA compatibility flags from different games might have some influence.



I started a designated thread concerning the panning camera issue here http://forum.square-enix.com/ffxiv/t...90#post1262790
It would be good to move the discussion there.

Something to add based on recent experimentation.

It seems setting the ingame framelimiter with Nvidia at least doesn't also vsync properly.
Forcing VSync on in the NV controll panel alongside setting the ingame setting to 60fps makes a difference between irksome stuttering and silky smooth when panning the camera.
This also applies in areas when the fps drops as low as 20fps while still feeling smooth.

Yesterday, I swapped out one of my GTX460's for a GTX760 ... Actual performance was comparable between the too... But the 760 just /felt/ less smooth with stuttering when panning that it did not with the 460 ... But forcing vsync on in NV CP alongside with the ingame framelimter to the displayes refresh rate resulted in /feeling/ as smooth as the 460 while panning.

Quote:

---

Originally Posted by Nin-Lil-izi

Something to add based on recent experimentation.

It seems setting the ingame framelimiter with Nvidia at least doesn't also vsync properly.
Forcing VSync on in the NV controll panel alongside setting the ingame setting to 60fps makes a difference between irksome stuttering and silky smooth when panning the camera.
This also applies in areas when the fps drops as low as 20fps while still feeling smooth.

Yesterday, I swapped out one of my GTX460's for a GTX760 ... Actual performance was comparable between the too... But the 760 just /felt/ less smooth with stuttering when panning that it did not with the 460 ... But forcing vsync on in NV CP alongside with the ingame framelimter to the displayes refresh rate resulted in /feeling/ as smooth as the 460 while panning.

---

I noticed that also.. I reported a bug like that in closed beta.. The funny part is when it would rain and that would happen the rain would actually flow from the ground to the sky and not the sky to the ground even tho it said you have say 70 fps it felt like the fps was tanked to low 13+s

Quote:

---

Originally Posted by Nin-Lil-izi

Something to add based on recent experimentation.

It seems setting the ingame framelimiter with Nvidia at least doesn't also vsync properly.
Forcing VSync on in the NV controll panel alongside setting the ingame setting to 60fps makes a difference between irksome stuttering and silky smooth when panning the camera.
This also applies in areas when the fps drops as low as 20fps while still feeling smooth.

---

I cannot recreate this problem and I would have noticed immediately as I'm super fast at detecting screen tear. Currently in-game frame limiting and driver level forced Vsync (standard) gives the same performance and/or smoothness.
Adaptive Vsync is slightly faster by about 1-2 frames (in-game frame limiter disabled), yet induces a synthetic tear when the game drops between 50-60 frames during a stuttering moment. I imagine if there was no stutter, you wouldn't see this.

Quote:

---

Originally Posted by Nin-Lil-izi

Yesterday, I swapped out one of my GTX460's for a GTX760 ... Actual performance was comparable between the too... But the 760 just /felt/ less smooth with stuttering when panning that it did not with the 460 ... But forcing vsync on in NV CP alongside with the ingame framelimter to the displayes refresh rate resulted in /feeling/ as smooth as the 460 while panning.

---

I want to say that's driver related since the driver would (if the client allows - which we know it does) over ride the in-game setting. Have you turned the frame limiter off and used only the driver level Vsync?



Unfortunately none of this sounds like it's related to the panning issue. I've gone through eight GPU combinations now - starting to wonder whether Square will acknowledge a problem. Salt in the wound is that in BETA III, a single card had overall better performance than two of them do now. Yes they instituted official SLI support but it seems like the predefined profile is broken and what's more is that the pan problem happens with a single card as well.

Heh, no my issue that fixed by forcing on vsync was not tearing at all.... I saw no sign of tearing. none.
The issue was with horrible eye pain inducing stuttering while panning.

Pretty sure its a driver issue beyond anything else, tbh.... And maybe a bus contention issue for a proportion of others.
NVidia hasn't release a new RTM driver for a few months now... So, hopefully they'll release a new 100% more awesome with FF XIV driver sometime soon.

TBH i think its the drivers and possable the same time the way the game is coded..

Test systems

Intel Dual e5600 @ 2.6 ghz
4gb DDR 3 @ 800 mhz memory
Nvidia geforce gtx 460

1920 x 1080 Desktop high settings @benchmark Score:4339
Average Framerate:38.062
Performance:High
-Easily capable of running the game. Should perform well, even at higher resolutions.

Intel quad core @ 2.83 ghz
8 gb ddr 3 memory @ 1333 mhz
geforce gtx 460

1920x1080 maximum settings Benchmark Score:4949
Average Framerate:40.695
Performance:High
-Easily capable of running the game. Should perform well, even at higher resolutions.


Yes we all know that benchmark is not 100 percent but it should be a decent representation on how the game SHould run as you base the game on the benchmark..

Latest Nvidia drivers...

The dual core setup was unplayable in game even on the lowest settings and could not get constant frame rate reguardless were taking anywhere from 8 fps to 17 fps open world occasional 30 and in town with camera panning was 1-4 fps (unplayable)

The quad-core actually benched about the proper speeds in game 40-60 outside areas 20-30 in towns..

Why would i bring this up if higher end rigs behave so badly with camera panning what does this have to do with anything.. While at first glance it looks like a inferior system is being outpaced by a ok system and there high end and ultra systems should smoke the game...

Untell i decovered this ( thanks god for debugging)

Your video card has about 20-30 gb of bandwith from the processer to the gpu for graphics ( dont confuse this with fill rate etc.) this is the amount of data over a 60 second to 120 second time frame that can be pulled from the cpu to the frame buffer and back again ). This is how Video cards work cpu sends request from game to have video images rendred it gets displayed it asks for more data to process..

Cpu wise handles everything else from ai to contoller input so on so forth also manages memory in game..

The bandwidth or maximum theoretical throughput of the front-side bus is determined by the product of the width of its data path, its clock frequency (cycles per second) and the number of data transfers it performs per clock cycle. For example, a 64-bit (8-byte) wide FSB operating at a frequency of 100 MHz that performs 4 transfers per cycle has a bandwidth of 3200 megabytes per second (MB/s):
8 B × 100 MHz × 4/cycle = 3200 MB/s


that's a 64 bit program 32 bit is 4 b x 100 x 2/cycle = 1600 mb /sec of bandwidth..

How does that pertain to panning..

Simple reason why high end systems are getting murdered.. Is you might have the lastest quad core with the top end gpu but because its a 32 bit program and with the way its trying to stream all the textures across your gpu + cpu pipeline eg dynamic loading of bosses and people... Your bottleneck is actually software limitation....


it took me a medium spec / lower end spec pc that is capable of running the game to figure it out..

The reason panning is screwed is the frame timer eg the time it takes for it to release 1 frame and present the next is bottle necked...

more or less its like this your cpu cannot supply enough data to actually make use of your cards atm cause it seems there using streaming textures and assets across the pipeline ( the way consoles do) instead of more traditional frame buffer across the pipeline)

immigration having a 4 lane vs 2 lane vs 6 or 8 lane road with 1 express lane for the gpu to just run at full speed.)

There trying to cram 4-8 lanes of traffic across a 2 lane highway... Hence your getting data backup and drooped frames.


dual core cpu's are getting massacred regardless of the gpu cause it cant keep up so its very pronounced on them..

I do owe an apology to the people that were saying they had the issue and i gave them crap for it... For that im truly sorry.

And still there is no official SE statement