Unofficial : Significant performance loss when panning camera [any angle, any arc]

Have made this thread in hopes it gets treated as an official issue that is intended to be addressed or is currently being addressed already.

What this post is NOT about:

-Overall performance
-Bragging
-How you fixed your 'problems' by buying a new cooler or fan
-People's supposed knowledge of DirectX APIs
-Why Windows is bad

What this post IS about:

A performance issue where panning the camera causes significant frame speed loss.


How does it happen?: We don't know, it's what we're here to try and find out and get support from Square.

How does it manifest itself? What are the symptoms?: Anytime you pan the camera, there may be a noticeable drop in performance and frames per second. The panning itself does not need to cover an arc of any particular spread, i.e. 90 degrees, 45 degrees etc. It happens when making even minute adjustments to the camera. However it does not happen when strafing side to side, or in motion forward and backward.

Where does it happen?: For some people, everywhere in the game. For others (most with the issue), it happens in the vicinity of hot spots. 'Hot spots,' are areas in the game where when facing them physically, your performance lowers because of strain on the CPU and/or GPU. A simple example would be standing at an Aetheryte camp with lots of other players around. This is not uncommon and is treated as an 'overall performance' issue (which as mentioned above is not the purpose of this thread). What is not common, is that panning the camera creates even more performance loss of a noticeable degree. One to three frames per second MIGHT be within an error margin, however ten to fifteen frames per second is not normal.

Where does it happen that it shouldn't happen?: Unlike above when in a hot spot area, this can happen anywhere in the game. For most though it appears when you are facing a hot spot location yet are not actually within local proximity. Currently if you face a hot spot as described above, then run the opposite direction until you are unable to see the hot spot with the naked eye, you will still suffer the same performance degradation when panning the camera. Even despite the fact that the hot spot is not being rendered on screen.

Is it possible that the Occlusion Culling feature in the game's System Configuration is not working?: Depends on what defines "not working." If you disable the option, you lose performance. On that merit, it is working. Whether it functions properly to it's full extent is unknown - though this problem did not exist in BETA III or prior.

Could this be a two pronged issue, where a bad Culling system can cause the camera panning problem?: Possibly, though it doesn't explain why some people have the issue everywhere, even when not facing or near hot spots.

Is there any official response or word about it so far from Square?: To my knowledge no.

Does it affect all users?: No, it's not universal though it happens to enough people that it involves hardware from all companies Nvidia, AMD, Intel and all third party vendors in any non specific combination.

Do I have any idea what's causing it?: I am confident that it has a lot to do with player character rendering(PCs, not NPCs) and strain on the CPU. While this is a natural performance degrader, the panning issue is the anomaly that exacerbates the poor organic performance. The anomaly then manifests itself further when you are outside of hot spots yet still suffer performance loss - as if it has a residual effect that cannot be purged.

What has been tried to work around or fix it?:

Disabled SLI/Crossfire [GTX670s, 680s, Radeon 7950s, 7970s and others]
Physically removing one card
Swapping card positions (and repeating above)
New/old drivers
New/old modified drivers
Separate Windows install
Compatibility modes for FFXIV client
Fullscreen/Borderless/Window client
Multitude of manual adjustments in Nvidia Inspector/Radeon Pro (including no Vsync, adaptive Vsync, frame limiter, frame limiter 58/60hz etc)
Disabled overclock
Disabled memory overclock
Affinity combinations
Task priority (high/realtime)
Disabled/reduced motion blur(radial blur) in-game



What can I do about it?: If the knowledge was available, you'd be the first to know! In the meantime you can help with a generous first step by taking the time to /sign or post here that you understand what's been written and you experience this issue(s). Additionally you can fill out the template that was provided by Kittra and we'll see about identifying a common denominator. Please avoid commenting otherwise and refer to the comments above about the thread's purpose.

Quote:

---

Originally Posted by Kittra

If anyone is experiencing this issue, I'd ask if you would please post your setup in the format of:

CPU: xxxxx @ x.xxghz (include any overclock information in the speed)
Motherboard: xxxxxxxxx
Memory: xxxxxxxx xxGB @ speed here
Hard Drive: xxxxxxx (This is the HDD the game is installed on, not windows)
Video Card: xxxxxxx xGB (include any overclock information)
Power Supply: xxxxxxx (include the wattage)

Driver Information
nVidia or AMD/Radeon driver information should go here along with whether or not you did a clean install or just over wrote the previous drivers.

---

Reserved for updates

Bump.
/10char

If you unlock the frame rate, go to a place where you can get 70+fps, then pan your camera do you still notice this drop in framerate? Do you notice it while maintaining 60 or more FPS while panning?

Windowed Mode or Full Screen... I notice this in window mode... NOT full screen.

Quote:

---

Originally Posted by Althea

If you unlock the frame rate, go to a place where you can get 70+fps, then pan your camera do you still notice this drop in framerate? Do you notice it while maintaining 60 or more FPS while panning?

---

Yes; it can happen from any arbitrary point/fps.

Quote:

---

Originally Posted by MysteriousStranger

Windowed Mode or Full Screen... I notice this in window mode... NOT full screen.

---

All modes. I have added this to the list of things tried; there was a post from another user a week ago where they had stopped using full screen because they got what they called 'stutter.' They switched to borderless window and said the stutter wasn't as noticeable but they got overall worse performance and had to alt-tab often to fix it.
Later we came to find out that the sutter they mentioned was actually the panning camera problem. Borderless/window mode did not fix it, it just masked it because the overall performance was lower and thus left a smoother impression with less hiccups.

AHAHAHAHA. WOW. An entire thread dedicated to chasing ghosts. I'm not even going to try to explain how dense you are for thinking your issue is unrelated to every other framerate issue players are experiencing. Enjoy the futility.

You realize, you MUST take ALL things into account. One of the joys of PC games. This includes drivers, hardware, fans, direct X knowledge everything right? What bother's me is you told me that having a multi-monitor setup paired with borderless windows has no impact on GPU performance. This would have been better served as a consolidation point for all FPS issues, instead of your own view of the problem instead of as a whole.

Quote:

---

Originally Posted by Syx

AHAHAHAHA. WOW. An entire thread dedicated to chasing ghosts. I'm not even going to try to explain how dense you are for thinking your issue is unrelated to every other framerate issue players are experiencing. Enjoy the futility.

---

Quote:

---

Originally Posted by C-croft

You realize, you MUST take ALL things into account. One of the joys of PC games. This includes drivers, hardware, fans, direct X knowledge everything right? What bother's me is you told me that having a multi-monitor setup paired with borderless windows has no impact on GPU performance. This would have been better served as a consolidation point for all FPS issues, instead of your own view of the problem instead of as a whole.

---

There are enough generic performance 'why is my FPS' bad threads. This is targeted at a specific anomaly that while may be 'performance' related, is not a direct result of any specific variable that I've listed, that you've listed or anyone to date has listed. Until that happens, then we can't 'consolidate' it and pass it off as normal.


As to your comment about multi monitors, it is irrelevant to any noticeable degree unless the displays are rendering content. If they are idle then the only thing they have in common is shared video memory - which can be monitored while in a 3d application. Even with four monitors in succession, FFXIV uses less than 1400 GPU RAM.
What was the point of mentioning this other than it bothers you(and why does it bother you?)?

I disabled motion blur and it got a LITTLE better... like one or two FPS, but it was only dipping to ~48 for me to begin with, so not really a noticeable improvement. Depending on the system, it might be more noticeable.

Just mentioned it because I didn't see it on the list of things tried.

Quote:

---

Originally Posted by Raist

I disabled motion blur and it got a LITTLE better... like one or two FPS, but it was only dipping to ~48 for me to begin with, so not really a noticeable improvement. Depending on the system, it might be more noticeable.

Just mentioned it because I didn't see it on the list of things tried.

---

Great thinking Raist. In some ways it seems so obvious. I have now tried this as well and it was unable to rectify the issue - added to list.

I've never personally experienced this issue (though I have experienced frame stuttering [Which I fixed]), however, I am extremely interested in finding out more about it.

As someone mentioned earlier, understanding the problem (and fixing it) usually goes hand-in-hand with how your system is setup (Ex: Hardware/software), what video drivers you have/are set up as, and what your in-game settings are.


I'd like to focus on the hardware/driver setup of the problem to try to understand it better (this is usually where most start). Chances are there are others with similar setups who do not experience this issue, or do experience it but have found a way around it and are unaware that others are having it, or just do not wish to take the time to help those with the problem to resolve it.

If anyone is experiencing this issue, I'd ask if you would please post your setup in the format of:

CPU: xxxxx @ x.xxghz (include any overclock information in the speed)
Motherboard: xxxxxxxxx
Memory: xxxxxxxx xxGB @ speed here
Hard Drive: xxxxxxx (This is the HDD the game is installed on, not windows)
Video Card: xxxxxxx xGB (include any overclock information)
Power Supply: xxxxxxx (include the wattage)

Driver Information
nVidia or AMD/Radeon driver information should go here along with whether or not you did a clean install or just over wrote the previous drivers.

Any Additional Information you feel might be relevant to the way your drivers are configured

As an example (although I do not suffer from this problem):

CPU: Intel i7 3770k @ 4.5ghz
Motherboard: ASUS P8Z77-V PRO
Memory: Kingston Hyper X Blu 24GB @1600mhz
Hard Drive: Samsung 830 SSD 256gb
Video Card: ASUS GTX 670 4GB (Overclocked to 1000mhz speed)
Power Supply: Corsair AX850watt Modular Gold Certified

Driver Information
nVidia drivers 327.23 WHQL installed as a clean installation via nVidia's driver install program.
Previously I was running the 326.41 Beta drivers with great results.
I've tested the 327.23 WHQL drivers for about 8 hours without any problems in FFXIV:ARR as of yet.

Any Additional Information you feel might be relevant to the way your drivers are configured
I've personally configured the nVidia drivers via their configuration tool in Windows.
Relevant information that effects the game as I've discovered:
FXAA - ON
Antialiasing - Gamma correction - ON
Antialiasing - Mode - Application-controlled
Maximum pre-rendered frames: 1
Power management mode: Prefer maximum performance
Triple buffering - ON
Vertical sync - Use the 3D application settings


As I've said, I don't experience this problem, but I have experienced many others, the majority of which I have fixed through driver updates, driver configuration, CPU and Video card tweaking.
I also have 5 PCs all with different hardware that I "can" run the game on and test different elements with.

I considered having people put down their specifications to find a common denominator but when that was tried in the other performance threads, it went into 'well I have your components and I don't have that problem. But I did have a bad performance problem until I replaced my CPU fan' and it got all muddled.

Hopefully if this garners attention, it will stay purposeful.

Quote:

---

Originally Posted by Kittra

FXAA - ON

---

Curious that you have FXAA on at the driver level. The in-game version was fixed and now does both transparency AA on the flora/tree leaves as well as normal FSAA style edge detection.

Quote:

---

Originally Posted by Ranebow

Curious that you have FXAA on at the driver level. The in-game version was fixed and now does both transparency AA on the flora/tree leaves as well as normal FSAA style edge detection.

---

I turned it on just to make sure that the drivers were not overriding the game settings, and other game that I play use it as well so there was really no reason to leave it off.
(I didn't really notice a difference in the game unless I turned FXAA off there, then the driver FXAA took over and it looked about the same.)

It happens to me as well with GTX 780. I have two of them, with or without SLI enabled the same behavior occurs. I could be getting a flat 90 fps, the minute I even touch the camera even if it is a slight budge, the fps could drop down to 50, but when I leave it alone it jumps back up to 90.

People can say they don't experience it, but I think it's the fact their frames aren't high enough to notice the drops. Honestly I think it's an optimization issue.

Quote:

---

Originally Posted by Kittra

I turned it on just to make sure that the drivers were not overriding the game settings, and other game that I play use it as well so there was really no reason to leave it off.
(I didn't really notice a difference in the game unless I turned FXAA off there, then the driver FXAA took over and it looked about the same.)

---

Yea, in one of the beta phases it had to be turned on. I am unsure if the driver level FXAA gives the same level of transparency coverage that the in-game version does.

Quote:

---

Originally Posted by gl0ry

It happens to me as well with GTX 780. I have two of them, with or without SLI enabled the same behavior occurs. I could be getting a flat 90 fps, the minute I even touch the camera even if it is a slight budge, the fps could drop down to 50, but when I leave it alone it jumps back up to 90.

People can say they don't experience it, but I think it's the fact their frames aren't high enough to notice the drops. Honestly I think it's an optimization issue.

---

Unfortunate to hear you have this. Please fill out the template on the front page if you'd like to help.
I do agree it's most likely an engine issue that needs adjusted and optimized.

any fixes yet? I have a bad fps drop ONLY when I pan the camera around :/...other than that I get a solid 60 fps everywhere.

Here are my specs, any help to fix this would be greatly appreciated, thank you!

CPU: Intel i5 3570K @ 3.8ghz
Motherboard: GiGabyte GA-Z77X-UD4H
Memory: G.Skill RipjawsX DDR3-1600 x 4 @16gig
Hard Drive: Samsung 840 Pro Series SSD 120gb
Video Card: MSI GTX 660 TI Power Edition x2 (SLI)
Power Supply: Thermal Take SmartM 850W Gold Certified

Everything is stock and not overclocked.

Driver Information
nVidia drivers 327.23 WHQL

MAX SETTINGS ON EVERYTHING

FXAA - ON
Antialiasing - Gamma correction - ON
Antialiasing - Mode - Application-controlled
Maximum pre-rendered frames: Use the 3D application settings
Power management mode: Prefer maximum performance
Triple buffering - ON
Vertical sync - Use the 3D application settings

I just tested this with SLI in Costa del Sol, panning near the Aetheryte with a lot of fates going on in the distance (there were a lot of players participating).

My test system was:

CPU: Intel i7 2600k @ 4.6ghz
Motherboard: ASUS P8Z77-V PRO
Memory: Kingston Hyper X Blu 16GB @1600mhz
Hard Drive: Western Digital Blue 620mb @ 7200 RPM
Video Card #1: EVGA GTX 570 1.25GB (Overclocked to 800mhz)
Video Card #2: MSI GTX 570 1.25GB (Overclocked to 800mhz)
Power Supply: Cooler Master GX750watt Bronze Certified

Driver Information
nVidia drivers 327.23 WHQL installed as a clean installation via nVidia's driver install program.
I was running the 314.22 WHQL drivers previously before with decent results (a few crashes here and there).
I've tested the 327.23 WHQL drivers for about a week now without any problems in FFXIV:ARR (this includes my previously listed system as well as the SLI system).

Any Additional Information you feel might be relevant to the way your drivers are configured
Pretty much the same as my last listed system:
FXAA - ON
Antialiasing - Gamma correction - ON
Antialiasing- Mode - Application-controlled
Maximum pre-rendered frames: 1
Power management mode: Prefer maximum performance
Triple buffering - ON
Vertical sync - Use the 3D application settings

For pure FPS speed to monitor drops I'm using a BENQ 120hz monitor, and the game is set to "unlocked" for the FPS limiter (this is unaffected by driver Vertical sync).


Facing the Aetheryte in Costa del Sol, I started out at a solid 120fps without moving the camera. Upon panning the camera slowly to the left I experienced a slight FPS fluctuation between 115 and 109 (not a large drop at all), I then sped up panning to the left and the FPS counter stayed constant at 115-109fps. Panning almost in a complete circle the FPS suddenly dropped from 115-109 to 55-50fps.

I was a little shocked when it did this but I had a pretty good idea of what caused it. Upon opening the map I discovered my field of view indicator was set squarely on the Fate "It's not Lupus" (A high reward fate that yields between 10,000 and 30,000 EXP).
Panning away from that Fate, my FPS indicator shot back up to 115-109.

In systems I quickly locked my FPS to 60 to see if there was a difference in panning. The results were about the same as unlocked. I stayed at 60fps throughout the entire pan, the second I hit "It's not Lupus" my FPS dropped to 55-50fps. In this case it's clearly the Fate causing my FPS drops.


I then tried strafing to see if there was a difference (I re-unlocked the FPS). Strafing around the Aetheryte my FPS was a constant 120fps (about 119-120 but it was almost always a solid 120), facing "It's not Lupus" the results were about the same with panning (50-55fps), at the same time the Fate ended and after a few seconds my FPS went back up to 120.

TL;DR I see a drop while panning as opposed to strafing while using SLI but it is minimal at best, not nearly as bad as some people are reporting, and I'm still dumbfounded as to how your FPS can go from a solid 120 or 60 to barely anything (just by panning the camera) without facing a giant group of people off in the distance.

Hi Noxaru, we haven't had any progress nor an update from our various support tickets.

Other systems tested included an old Core 2 E6600 with a 4870X2 card on an old EVGA board using drivers Kittra listed below (And some others).
Unfortunately the problem persisted.

I am going to work on an AMD system next.


Kittra, I would say losing five to ten frames from a simple camera adjustment IS a large drop. Considering especially that all the content is already rendered, the scene is finished drawing and there's no obvious or extenuating circumstances - that's very poor.
Performance loss from camera movement - in most cases - I would put down to a lack of memory on the GPUs. E.g. Skyrim with so many mods going that you've used up 2GB of video memory and now are suffering jerkiness as the system tries to flush and purge. Yet FFXI at 1600p (for example) uses no more than 1300 memory - clearly well below the limits.

What you mention about strafing is also key as that is one of the odd aspects. Movement in general can induce frame loss, however that means ANY movement. Being able to strafe which in itself is a type of 'camera' motion, does not cause performance loss, yet the actual act of 'panning' the camera does!
This inconsistency makes the situation unique as per my original thread comments and has exclusivity in difference from simple bad performance when facing a FATE at a distance.

I understand what you're saying Ranebow, but that drop isn't very different from what I experience in other games while panning, especially First Person Shooters like Planetside 2 (an online FPS).

The drop is fairly consistent and happens in the majority of Direct3D games I have so that's why I didn't believe I was experiencing the same drop that others were reporting.

I was under the impressing that the drop was from 120 or 60 fps down to 55 or 25 fps just from panning the camera. This scenario I could understand as a drop that large is definitely a problem.

Quote:

---

Originally Posted by Kittra

I understand what you're saying Ranebow, but that drop isn't very different from what I experience in other games while panning, especially First Person Shooters like Planetside 2 (an online FPS).

The drop is fairly consistent and happens in the majority of Direct3D games I have so that's why I didn't believe I was experiencing the same drop that others were reporting.

I was under the impressing that the drop was from 120 or 60 fps down to 55 or 25 fps just from panning the camera. This scenario I could understand as a drop that large is definitely a problem.

---

Yes, you are correct, frames are being lost to wild amounts between twenty to thirty at times. As an example I have posted pictures standing in Gridania facing the Chocobo porter.
First shot is camera stationary, second shot is camera with a quick flick left (towards the Inn) and back resulting in the drop to 41.

http://i39.tinypic.com/o78twp.jpg
http://i39.tinypic.com/23lftih.jpg

Interestingly, and I may update this on the front page - I disabled occlusion culling so that it was rendering things 'off screen,' and my performance dropped as expected to right around the same speed that I get when panning the camera.
More and more I am convinced now it's something to do with the culling system.

Quote:

---

Originally Posted by Ranebow

Hi Noxaru, we haven't had any progress nor an update from our various support tickets.

Other systems tested included an old Core 2 E6600 with a 4870X2 card on an old EVGA board using drivers Kittra listed below (And some others).
Unfortunately the problem persisted.

I am going to work on an AMD system next.

---

I see, thank you for the response.

Hrm... I had the mind to add one thing here, mentioning that when I updated my drivers (using an AMD card) the issue here vanished (the particular 'graphics lag when panning' issue). Howevre, Ranebow, what you just said made me think...
That updated improved my FPS as a whole, and now that you mention occlusion culling I think I might know WHY the panning suddenly drops your FPS and it's quite... Logical.

Occlusion culling doesn't renders things which are offscreen, that saves you on processing power and memory but it ALSO requires you to suddenly load and render everything outside your view range when you pan your screen.
Which means that when that is on you are causing a sudden spike in processing/memory requirements by asking a lot of new things to be rendered suddenly, causing a huge drop in FPS temporarily. Notice how your issue is worse the more things are there around you? (try that in Revenant's Toll, then try that in, say... Urth's Gift? Or, hum... Nym? Somewhere that is kinda barren playerwise)

Quote:

---

Originally Posted by Skies

Hrm... I had the mind to add one thing here, mentioning that when I updated my drivers (using an AMD card) the issue here vanished (the particular 'graphics lag when panning' issue). Howevre, Ranebow, what you just said made me think...
That updated improved my FPS as a whole, and now that you mention occlusion culling I think I might know WHY the panning suddenly drops your FPS and it's quite... Logical.

Occlusion culling doesn't renders things which are offscreen, that saves you on processing power and memory but it ALSO requires you to suddenly load and render everything outside your view range when you pan your screen.
Which means that when that is on you are causing a sudden spike in processing/memory requirements by asking a lot of new things to be rendered suddenly, causing a huge drop in FPS temporarily. Notice how your issue is worse the more things are there around you? (try that in Revenant's Toll, then try that in, say... Urth's Gift? Or, hum... Nym? Somewhere that is kinda barren playerwise)

---

Logical though several rebuttals:

A) If anyone plays without Occlusion culling disabled(which you won't find a lot as it eats performance badly), then every time they moved the camera, they'd have performance loss. Though we know this isn't the case as it doesn't affect everyone - occlusion or not.
B) Have to remember that ANY motion would induce this issue, not just panning the camera and in most games character movement as a whole will cause some performance degradation but standing still and turning the camera will not.
C) Memory is not exhausted so why the stutter?

As for player and object density, yes I do think there's a correlation. The other side of this coin though is that even when those things are not being drawn physically, you still lose the performance when facing that direction but ONLY when panning the camera, not when simply standing still or moving your character.

one important thing needs to be taken into consideration when testing for this, and that is to avoid the "hotspots" when panning. For instance, an earlier post mentioned a high FPS drop when the inn was snapped into focus. That inn might be one of the spots where there is a rendering issue in general that causes a major drop in FPS regardless if the view is snapped there or you move casually that way as you walk. I've only confirmed this to be an issue with Hawthorne Hut so far (it's where I tested my graphics settings), but I'm sure there are other locations on other maps that also cause a significant drop in frame rate when your camera angle is aimed towards it. If your panning angle cuts across such a location, it is going to make your frame rate dive suddenly because that location has come into the potential viewing angle--not just because you are panning.

Quote:

---

Originally Posted by Raist

one important thing needs to be taken into consideration when testing for this, and that is to avoid the "hotspots" when panning. For instance, an earlier post mentioned a high FPS drop when the inn was snapped into focus. That inn might be one of the spots where there is a rendering issue in general that causes a major drop in FPS regardless if the view is snapped there or you move casually that way as you walk. I've only confirmed this to be an issue with Hawthorne Hut so far (it's where I tested my graphics settings), but I'm sure there are other locations on other maps that also cause a significant drop in frame rate when your camera angle is aimed towards it. If your panning angle cuts across such a location, it is going to make your frame rate dive suddenly because that location has come into the potential viewing angle--not just because you are panning.

---

I have been through various high density areas where the frame rate is 60fps solid and established :

A) No camera movement and no character movement results in 60fps
B) No camera movement but with character movement results in 60fps
C) Camera movement results in XX reduced amount of frames.
D) Camera movement and character movement results in same amount of reduced frames.

Now in high density hot spot areas where performance is down simply due to strain, let's say around 45fps the following may happen :

A) No camera movement and no character movement results in 45 fps (no change)
B) No camera movement but with character movement results in 45 fps (no change)
C) Camera movement results in XX reduced amount of frames, but to a lesser degree.
D) Camera movement and character movement results in same amount of reduced frames.

In this second scenario where the performance was already degraded, the frame loss frame panning is not as significant.

Furthermore as per second to last post of mine, the disabling of Occlusion Culling drops the frames down to the same level equal to that of when panning the camera.
If my fps is 42 with it disabled, my fps will dip no lower than 42 when panning. This cannot be coincidence.


Lastly, there's been reports and claims that it affects some players anywhere in the game, even when staring at a wall that's bordering a zone line with nothing beyond it.

yeah.. was just more a thought about people who may be mixing in the hotspots when they are panning, and mistaking the major dip for being just because they panned their camera. The whole importance of isolation, consistency, and control so you can more accurately test if changing settings is affecting your panning problem or not.

Quote:

---

Originally Posted by Raist

yeah.. was just more a thought about people who may be mixing in the hotspots when they are panning, and mistaking the major dip for being just because they panned their camera. The whole importance of isolation, consistency, and control so you can more accurately test if changing settings is affecting your panning problem or not.

---

It's a plenty welcome suggestion and should be considered of course.

I *mostly* have this problem on two systems when facing the hot spots. Interestingly though are where some of the hot spots are. For instance, my screenshot is in relation to the camera pan towards the Adventurer's guild in Gridania ; yes at times there's a good amount of players in there causing an overall performance loss, but it doesn't have the same affect from all angles. If I am running from the Badger gate towards the opening to the Adventurer's guild, I get no resistance or performance loss until I reach the portion where the path forks onwards to the building or up towards the Aetheryte. However once I step inside the building at the first tables on the right, panning no longer results in fps loss.
Which means there is literally a X meters by X meters box of sorts where this happens if you stand in it. And like above, similarly when near the Chocobo porter, if I move down the ramp and do the same it doesn't happen.

I moved away from thinking this was a driver issue early on, when I confirmed that it doesn't happen in all areas of the game and it doesn't happen equally when facing the same hot spot e.g. standing on one side of the spot can result in something different.

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.