ATI Card compatibility issues!

Dear Square,

For a few patches now your code has decided to be incompatible with ATI cards resulting in framerate dropping on mor dhona, in large parties or when changing zones. It has now gone to the point that it is crashing my system! ONLY with FFXIV:ARR does my atikmdag.sys crash; this does not occur with ANY OTHER GAME! this is entirely unacceptable for a AAA game that never previously had any problems (been playing since beta) leading me to believe that somewhere along the line you broke something. Having waited patiently for you to fix said problems and not minding being occasionally logged out of the game I cant wait any longer. Please note that this is NOT a driver issue on my end, this error does not occur with any other game or program only now with FFXIV. furthermore this does not occur as far as I am aware with any of my friends using NVidia cards. Im not a particularly tech savvy person with regards to hardware but I understand software and this is clearly an issue your end that you have failed to resolve for multiple patches. This needs fixing now and instead of focussing on pushing new content (like other MMO Developers.... cough cough *pandas* cough cough) you should fix the issues you have created.

Kind Regards,

Nox

Out of sheer curiosity, what is the model graphics card?

It's not just FFXIV. There have been known issues with DX9 games and ATI/AMD cards since around the 7000 family came out. The problem does not exist for older cards. There is something going on that the vendor needs to address in their drivers/firmware for the affected models.

Ok, makes sense. I have an AMD Radeon HD 6670, so wanted to ask.

this sounds like a bluescreen crash going by ops description, which would be down to unstable hardware...

usermode code cannot crash a system, and it if does it will explicitly state that the error occured while transitioning data from usermode to kernel mode (and would imply a driver bug).

I get this often as well with fully updated drivers on my HD8970M (alienware laptop). Trying to report on AMDs forums but still waiting on registration email.

Radeon R9 290.... Ive had the occasional bluescreen of atikmdag.sys crashing.... other than that lately im getting blackscreen which then recovers, once this happens however it will continuously happen. Multiple drivers installed and reinstalled have been to no avail. This is also a regular occurrence for other friends of mine using Radeon cards, however these errors only happen with FF. The older issues causing people to crash after teleporting around was due to memory leaks caused by LoD loads. I am also unwilling to blame ATI as these problems did not exist previously and only occurred after certain patches by SE notably the introduction of Hunts patch. furthermore it seems far fetched that it is a problem with drivers and or card when once again I play multiple games based on multiple platforms and none of them create the same errors or crashes; the fact that it is isolated to FFXIV leads me to believe there is a corruption in their code somewhere. The advice given by ATI is as follows and can be found at the link provided:

http://support.amd.com/en-us/kb-arti...rmessages.aspx

How to troubleshoot “Display driver stopped responding and has recovered”, ATIKMDAG.sys type errors
Article Number: 27116
​​This article provides information on the possible causes an ATIKMDAG.sys type error may occur and how to troubleshoot the system to prevent the error from reoccurring.

Issue Description:
During startup or use of an application, (most commonly a game / video application) the system or application will freeze, crash or exit to the desktop / a blue screen (BSOD). Additionally, an error message appears stating that the “Display driver stopped responding and has recovered” and may reference one of the following driver files:
ATIKMDAG.sys
ATI2DVAG.sys
ATI2CQAG.dll
ATIVPK.sys
AMD2DVAG.sys
AMDKMDAG.sys
AMDVPK.sys


Issue Cause:
The issue occurs when the Timeout Detection and Recovery (TDR) feature available in Windows Vista® and Windows 7 detects that the graphics card (GPU) has not responded within a predetermined period of time and reinitializes it with the Windows Display Driver Model (WDDM) to prevent the need to reboot. There is no single cause for a TDR event to be triggered.
Additional Details about TDR events can be found on Microsoft’s website.

Troubleshooting:
There are several factors that can cause the TDR event to be triggered. The following troubleshooting steps can help rule out / resolve the cause of the issue:
Note! If you do not feel comfortable performing any of the steps provided in these instructions, you should have your system checked by an expert.

If the issue occurs only when using a specific application, it may have known issues or corrupt files
Contact the application’s manufacturer for further information or for possible software patches

Perform a clean installation of the application

Microsoft DirectX® files may be outdated or corrupt
Reinstall Microsoft DirectX or install the latest version
Microsoft Article 179113 provides instructions for downloading /installing the latest Microsoft DirectX version

The motherboard’s BIOS / chipset drivers may be outdated
Check the motherboard manufacturer’s website for available BIOS / chipset driver updates
Refer to the update’s release notes to determine if it has a fix for your specific issue

The operating system may require a service pack update
Refer to the following Microsoft pages for instructions on downloading / installing the latest service packs:

Windows Vista: Microsoft Article 935791

Windows 7: Windows 7 Updates

Several known issues in Windows Vista may be related to the issue
Refer to the applicable Microsoft article(s) to obtain any necessary hotfix downloads:
The Flight Simulator X game display flickers and become corrupted on a Windows Vista-based computer that is connected to more than one monitor
The enhanced video renderer (EVR) sends the EC_DISPLAY_CHANGED event when you play a video stream in Windows Vista
An update is available that improves the compatibility and reliability of Windows Vista
Virtual address space usage in Windows Vista game development
Error message is displayed when installing a new hardware device on a system running Windows Vista
Graphics performance can be improved in certain multiple-GPU scenarios on a Windows Vista-based computer
A WHQL test does not finish successfully on a Windows Vista-based computer that has multiple display adapters in an LDA configuration
A reliability and performance update is available for Windows Vista SP1-based computers
You receive a "STOP 0x0000010E" or "STOP 0x000000C1" error message on a Windows Vista-based computer or on a Windows Server 2008-based computer
Description of the Windows Vista or Windows Server 2008 hotfix that resolves certain system and application crashes on computers that have multi-core processors
A graphics card is not removed from the display settings on a computer that is running Windows Server 2008 or Windows Vista SP1 if you unplug the card while the computer is asleep or in hibernation
Stop error on a Windows Vista Service Pack 1-based or Windows Server 2008-based computer that has an integrated graphics adapter and a discrete graphics adapter: "Stop 0x00000018"

The operating system may have corrupt system / registry files
Try cleaning the operating system’s registry
Perform a clean install of the operating system
Note! Performing a clean installation of the operating system will erase all data on the hard drive. Ensure all important data is backed up before performing this action

The graphics card drivers may have known issues or corrupt files
Refer to Article 20870 for instructions on downloading / installing the latest drivers for your graphics card
Refer to the drivers release notes to determine if there is a fix for your specific issue

An overclocked processor (CPU), graphics card or memory can cause system instability
Run all hardware components at their default settings
Refer to the motherboard’s manual for instructions on how to set hardware to default settings

An inadequate or defective power supply (PSU) can prevent the processor / graphics card from functioning properly
Refer to Article GPU-104 for instructions on how to determine if the PSU is inadequate or defective

The CPU and / or GPU may be overheating
Check the operating temperature of the CPU or GPU through the motherboard’s BIOS
Refer to the motherboard manual for instructions
Ensure the temperature does not exceed the maximum operating temperature of the product
Refer to the AMD Products Resource Center to determine the maximum operating temperature of any AMD CPU
Contact the graphics card manufacturer to determine the maximum operating temperature of the GPU

AMD ​Partners
If the hardware is above its maximum operating temperature:
Ensure an AMD approved heatsink/fan (HSF) is being used with the processor
Ensure the HSF unit is properly installed on the processor
Ensure the bottom of the HSF is leveled on the top of the processor
Ensure a proper amount of thermal grease is installed between the HSF and processor
Ensure that the fan on the graphics card and processor’s heat sink is connected correctly and that it is spinning when the system is powered on
Check whether there are any loose cables stopping the fan(s) from spinning or blocking the air flow within the system case
Verify that the airflow within the system case is circulating correctly
Air should flow in from the front of the case and out through the back of the case

Failing Hardware (processor, graphics card, motherboard and / or memory) can cause system instability
If possible, try testing the hardware in another system to determine if the issue follows the hardware

Run a memory test to determine the stability of the memory
The following third party utility will test your memory for errors: Memtest86
If using multiple memory modules
Test each memory module individually in the system, referring to the motherboard’s manual to determine which slot(s) can be used for single memory setup
Verify that each module is identified at the correct size and speed
Contact the memory and / or motherboard manufacturer for more comprehensive troubleshooting instructions

Replace the hardware

Ive gone ahead and did an ingame report to SE to see what they say, if anything

Quote:

---

Originally Posted by Igninox

Radeon R9 290.... Ive had the occasional bluescreen of atikmdag.sys crashing.... other than that lately im getting blackscreen which then recovers, once this happens however it will continuously happen. Multiple drivers installed and reinstalled have been to no avail. This is also a regular occurrence for other friends of mine using Radeon cards, however these errors only happen with FF. The older issues causing people to crash after teleporting around was due to memory leaks caused by LoD loads. I am also unwilling to blame ATI as these problems did not exist previously and only occurred after certain patches by SE notably the introduction of Hunts patch. furthermore it seems far fetched that it is a problem with drivers and or card when once again I play multiple games based on multiple platforms and none of them create the same errors or crashes; the fact that it is isolated to FFXIV leads me to believe there is a corruption in their code somewhere. The advice given by ATI is as follows and can be found at the link provided:

http://support.amd.com/en-us/kb-arti...rmessages.aspx

How to troubleshoot “Display driver stopped responding and has recovered”, ATIKMDAG.sys type errors
Article Number: 27116
​​This article provides information on the possible causes an ATIKMDAG.sys type error may occur and how to troubleshoot the system to prevent the error from reoccurring.

Issue Description:
During startup or use of an application, (most commonly a game / video application) the system or application will freeze, crash or exit to the desktop / a blue screen (BSOD). Additionally, an error message appears stating that the “Display driver stopped responding and has recovered” and may reference one of the following driver files:
ATIKMDAG.sys
ATI2DVAG.sys
ATI2CQAG.dll
ATIVPK.sys
AMD2DVAG.sys
AMDKMDAG.sys
AMDVPK.sys


Issue Cause:
The issue occurs when the Timeout Detection and Recovery (TDR) feature available in Windows Vista® and Windows 7 detects that the graphics card (GPU) has not responded within a predetermined period of time and reinitializes it with the Windows Display Driver Model (WDDM) to prevent the need to reboot. There is no single cause for a TDR event to be triggered.
Additional Details about TDR events can be found on Microsoft’s website.

Troubleshooting:
There are several factors that can cause the TDR event to be triggered. The following troubleshooting steps can help rule out / resolve the cause of the issue:
Note! If you do not feel comfortable performing any of the steps provided in these instructions, you should have your system checked by an expert.

If the issue occurs only when using a specific application, it may have known issues or corrupt files
Contact the application’s manufacturer for further information or for possible software patches

Perform a clean installation of the application

Microsoft DirectX® files may be outdated or corrupt
Reinstall Microsoft DirectX or install the latest version
Microsoft Article 179113 provides instructions for downloading /installing the latest Microsoft DirectX version

The motherboard’s BIOS / chipset drivers may be outdated
Check the motherboard manufacturer’s website for available BIOS / chipset driver updates
Refer to the update’s release notes to determine if it has a fix for your specific issue

The operating system may require a service pack update
Refer to the following Microsoft pages for instructions on downloading / installing the latest service packs:

Windows Vista: Microsoft Article 935791

Windows 7: Windows 7 Updates

Several known issues in Windows Vista may be related to the issue
Refer to the applicable Microsoft article(s) to obtain any necessary hotfix downloads:
The Flight Simulator X game display flickers and become corrupted on a Windows Vista-based computer that is connected to more than one monitor
The enhanced video renderer (EVR) sends the EC_DISPLAY_CHANGED event when you play a video stream in Windows Vista
An update is available that improves the compatibility and reliability of Windows Vista
Virtual address space usage in Windows Vista game development
Error message is displayed when installing a new hardware device on a system running Windows Vista
Graphics performance can be improved in certain multiple-GPU scenarios on a Windows Vista-based computer
A WHQL test does not finish successfully on a Windows Vista-based computer that has multiple display adapters in an LDA configuration
A reliability and performance update is available for Windows Vista SP1-based computers
You receive a "STOP 0x0000010E" or "STOP 0x000000C1" error message on a Windows Vista-based computer or on a Windows Server 2008-based computer
Description of the Windows Vista or Windows Server 2008 hotfix that resolves certain system and application crashes on computers that have multi-core processors
A graphics card is not removed from the display settings on a computer that is running Windows Server 2008 or Windows Vista SP1 if you unplug the card while the computer is asleep or in hibernation
Stop error on a Windows Vista Service Pack 1-based or Windows Server 2008-based computer that has an integrated graphics adapter and a discrete graphics adapter: "Stop 0x00000018"

The operating system may have corrupt system / registry files
Try cleaning the operating system’s registry
Perform a clean install of the operating system
Note! Performing a clean installation of the operating system will erase all data on the hard drive. Ensure all important data is backed up before performing this action

The graphics card drivers may have known issues or corrupt files
Refer to Article 20870 for instructions on downloading / installing the latest drivers for your graphics card
Refer to the drivers release notes to determine if there is a fix for your specific issue

An overclocked processor (CPU), graphics card or memory can cause system instability
Run all hardware components at their default settings
Refer to the motherboard’s manual for instructions on how to set hardware to default settings

An inadequate or defective power supply (PSU) can prevent the processor / graphics card from functioning properly
Refer to Article GPU-104 for instructions on how to determine if the PSU is inadequate or defective

The CPU and / or GPU may be overheating
Check the operating temperature of the CPU or GPU through the motherboard’s BIOS
Refer to the motherboard manual for instructions
Ensure the temperature does not exceed the maximum operating temperature of the product
Refer to the AMD Products Resource Center to determine the maximum operating temperature of any AMD CPU
Contact the graphics card manufacturer to determine the maximum operating temperature of the GPU

AMD ​Partners
If the hardware is above its maximum operating temperature:
Ensure an AMD approved heatsink/fan (HSF) is being used with the processor
Ensure the HSF unit is properly installed on the processor
Ensure the bottom of the HSF is leveled on the top of the processor
Ensure a proper amount of thermal grease is installed between the HSF and processor
Ensure that the fan on the graphics card and processor’s heat sink is connected correctly and that it is spinning when the system is powered on
Check whether there are any loose cables stopping the fan(s) from spinning or blocking the air flow within the system case
Verify that the airflow within the system case is circulating correctly
Air should flow in from the front of the case and out through the back of the case

Failing Hardware (processor, graphics card, motherboard and / or memory) can cause system instability
If possible, try testing the hardware in another system to determine if the issue follows the hardware

Run a memory test to determine the stability of the memory
The following third party utility will test your memory for errors: Memtest86
If using multiple memory modules
Test each memory module individually in the system, referring to the motherboard’s manual to determine which slot(s) can be used for single memory setup
Verify that each module is identified at the correct size and speed
Contact the memory and / or motherboard manufacturer for more comprehensive troubleshooting instructions

Replace the hardware

---

Yeah, no, sorry.

User mode code cannot crash the operating system.

Quite similar problem here. XFX HD7970. At first it was like once a month and then became more and more often. Now I can only play long enough to land 1 fish before I get a black screen and a funny robotic squealing sound which shuts my display down. Computer stays running but I have to restart via power button. Pushing the restart button does not work. This happens with BF3 as well, minutes into the game.

Quote:

---

Originally Posted by Lazykitty

Quite similar problem here. XFX HD7970. At first it was like once a month and then became more and more often. Now I can only play long enough to land 1 fish before I get a black screen and a funny robotic squealing sound which shuts my display down. Computer stays running but I have to restart via power button. Pushing the restart button does not work. This happens with BF3 as well, minutes into the game.

---

:3 then RMA the heck out of that card, its faulty.

I heard if more people make complaints, the more attention will be paid to the issue.

http://www.amd.com/report

Quote:

---

Originally Posted by Squa11_Leonhart

:3 then RMA the heck out of that card, its faulty.

---

Yup. Turns out card is faulty.Swapped it out with my old card. Works just fine. Sending back to XFX for rep.

Bring back to front of forums and SE's attention as the problem still persists. Absolutely no response from in game support.

Quote:

---

Originally Posted by Athenial

Bring back to front of forums and SE's attention as the problem still persists. Absolutely no response from in game support.

---

not really something the game developers can fix anyway.

I figured it had to be something FF related since this is the only game I am playing that has crashes. DAI had slight issues but that was fixed with a driver update. I'm trying to get onto the ATI forums but yeah still haven't received the verification code :/
just sucks that everything is in Mor Dhona and that is crash city

Quote:

---

Originally Posted by Athenial

Bring back to front of forums and SE's attention as the problem still persists. Absolutely no response from in game support.

---

SE does not manufacturer ATI video cards, nor do they develop the drivers for them.

It's silly that this post forum post exists and that you guys assume it's something SE can rectify. Like really, wtf?

*also some of the issues a few of you are describing almost sound like an issue regarding your power supply. It sounds almost as if you guys do not have the required amperage on your 12v rails to support the card's power requirements.

This in itself can cause havoc on your system overall and can cause the very issues you all are describing. Including but not limited to frying your PSU, motherboard or card itself.

You can purchase a video card that requires a 550w PSU, and have a 550w PSU and think that you meet the power requirements. (There are many PSU's on the market and not all of them are made the same. PSU's can have different amperage on their 12v rails which are extremely important to know prior to installing a new card. )

However, your 550w PSU may only have a single rail with 38A, when your card requires 42A. This can cause stability issues and blue screens if your GPU utilization gets high enough....IE, a place like Mor Dhona.

Im not 100% sure what the issue is nor do I want to argue what it is but I have also had the exact same issue with my old HD7870.

I crashed atleast twice a day but only in FFXIV. Recently upgraded to GTX970 and not a single problem.

Seems to me like poorly developed drivers?

I was wrong to assume SE for any of this. I would crash only minutes after log in. It started slow at first (maybe once a month) then more and more until i couldnt play at all. Tested other games, same problem. Researched it quite heavily. Power supply, RAM, Motherboard, everything. The video card is not that old so I didnt assume any problems there. After a Memtest came back good it had to be the GPU. Swapped it out for my 6850 and FFXIV run's just fine. GPU is currently with manufacturer getting repaired.

Bad call on my part, sorry Yoshi.

Quote:

---

Originally Posted by VoltaAsura

SE does not manufacturer ATI video cards, nor do they develop the drivers for them.

It's silly that this post forum post exists and that you guys assume it's something SE can rectify. Like really, wtf?

*also some of the issues a few of you are describing almost sound like an issue regarding your power supply. It sounds almost as if you guys do not have the required amperage on your 12v rails to support the card's power requirements.

This in itself can cause havoc on your system overall and can cause the very issues you all are describing. Including but not limited to frying your PSU, motherboard or card itself.

You can purchase a video card that requires a 550w PSU, and have a 550w PSU and think that you meet the power requirements. (There are many PSU's on the market and not all of them are made the same. PSU's can have different amperage on their 12v rails which are extremely important to know prior to installing a new card. )

However, your 550w PSU may only have a single rail with 38A, when your card requires 42A. This can cause stability issues and blue screens if your GPU utilization gets high enough....IE, a place like Mor Dhona.

---

FFXIV is the only issue that I have had in regards to this rig, and its an Alienware so Im assuming that it was built to handle the equipment in it. Everything is fine save for Mor Dhona as well as some S ranks if i port in during the mad rush. Im not burning houses and stuff just seems to be a common thread among ATI users that it could be an issue. If so would like a response from SE regarding this. I have also sent requests for it to be looked into with AMD as well.

Once again if its not SE's issue they could easily have a dev or someone say, "hey not us"

I am finding FFXIV has the most issues out of any game I play with interacting with Video drivers. Even more so then other SE games. Things seem to break from patch to patch with no changes on my side. Personally I think the blame falls on a mix of the Video card manufactures and SE. IF it was 100% ATI then a patch would not break as many things as I've seen break (Crossfire, etc.) I think a lot of the issues are due to the fact this is a DX9 game. I hope that the DX11 update with 3.0 addresses some of them. Sadly it appears this game runs better on older video hardware.

Yeah I am also hoping that the dx11 will play a lot nicer with my computer...but that is quite a few months away to deal with the constant ctds

Sadly, I had to downgrade my drivers (7870XT) to 13.12. It seems to play the nicest with this game. Still get some micro-stutters and hitches, but it runs fairly smoothly. Tried every driver from 13.XX to the 14.12 Omega Drivers and none of them were worth a damn, except 13.12. So, if you have older hardware, try those, they seem to be the most reliable.

For the ones saying "hey, its not the game, is your card", please, you are not helping. Also, i have the same problem, with a R9 280x. This problem occur only in this game, i play all my other games without problems, and this one, and since patch 2.3 to be precise, is the only one who crash. This is not the first post about this problem, and im sure this is not gonna be the last one.

Especially with the increase in usefulness of hunts it is becoming an even larger problem. I want to say that this should be addressed, but no response from anyone on the SE side is quite telling. I can barely get in and out of rev toll without issues now

Memory-Leak-Preformance-Issue This isn't the first time this problem showed itself. The last time was, can you guess it? Was the last time hunts was popular. Back when they gave us hunts and the ability to get sands/oils from them. Read that thread, its exactly the same issue. Check the dates when the thread started to die down. That was conveniently around the time they nerfed hunts. Or rather when they pushed myth out the door, and gave us poetics, and made it where no one wanted to do hunts. The issue nearly all but disappeared. Now hunts are back in a big way, and so is this issue. My Fiancee uses a AMD 6970 and has this problem as well. The work around in that thread does help some but the issue will still happen. I have a R9 290x and haven't experienced a crash. But sense 2.5 my GFX lag has went to about 30 FPS for the most part. I use to be 60+ even sitting in Mor Dhona.

Also idk why that thread is under resolved. If they put it in their because someone found a work around by disabling a option in FFXIV, then that was not the right thing to do. SE should work with ATI and get this issue fixed already. How long do we need to wait, until the DX11 client?

Well I forgot to mention this issue actually has changed sense that thread. It use to just freeze up for the most part, and rarely crashed. Usually what would happen is it would really freeze up bad for awhile, then when it finally got back to normal textures were missing all over the place. Certain npcs would be missing legs/arms, or entire mobs were invisible. But now it seems instead of the game simply recovering, and showing missing textures, it just crashes the game. Maybe someone at SE could use that knowledge to help them find out what the cause is.

Workaround: Enable LOD and LOD streaming. Issue goes away for the most part. If it doesnt, select standard laptop settings, and make sure those two LOD options are checked.

It's depressing when people that can run Elite dangerous, Crysis, Star Citizen, <insert any nextgen game> at 60FPS but can't seem to run this without disabling stuff.

Quote:

---

How long do we need to wait, until the DX11 client?

---

More or less.... yes. Soooo many of this games performance/stability issues revolve around the shoddy DX9 implementation... and Microsoft's lack luster support for DX9 (and by extension the vendors as well with their drivers in the last several generations). It's nothing new... and it isn't isolated to just XIV either. There are many DX9 games that have issues with the newer generations of cards when they are running in the newer versions of Windows.

Have to remember that DX9 is now run through an emulation layer. It hasn't been natively supported by Windows since XP. That was the last version of Windows where DX9 was supported properly by Micro$oft. It wasn't long after Win7 came out that we started seeing issues with DX9 in the video card drivers as well. It is more or less because of the fundamental changes in how Windows handles graphics, and that has also extended into how the drivers are coded as well.

So, yes... the DX11 client should resolve a lot of problems for people with cards released to market after around 2009/2010. I just hope they do a better job with it's implementation than they did with the DX9 client.

Quote:

---

Originally Posted by Raist

More or less.... yes. Soooo many of this games performance/stability issues revolve around the shoddy DX9 implementation... and Microsoft's lack luster support for DX9 (and by extension the vendors as well with their drivers in the last several generations). It's nothing new... and it isn't isolated to just XIV either. There are many DX9 games that have issues with the newer generations of cards when they are running in the newer versions of Windows.

Have to remember that DX9 is now run through an emulation layer. It hasn't been natively supported by Windows since XP. That was the last version of Windows where DX9 was supported properly by Micro$oft. It wasn't long after Win7 came out that we started seeing issues with DX9 in the video card drivers as well. It is more or less because of the fundamental changes in how Windows handles graphics, and that has also extended into how the drivers are coded as well.

So, yes... the DX11 client should resolve a lot of problems for people with cards released to market after around 2009/2010. I just hope they do a better job with it's implementation than they did with the DX9 client.

---

Good post, however I would really like SE to at least acknowledge this thread with a response. I know they have to read these threads, do they not care? If they said something maybe that can give AMD users a glimmer of hope. Right now the silence is pretty much telling us "f off we only like nvidia"

You don't hear much official response here because it was intended to be used as a user-to-user forum more than a direct line to the developers and such. It's detailed in the sticky welcoming you to this forum.

The vendors have more actively communicated with users though (both AMD and nVidia... unfortunately more so nVidia than AMD)...but that is over at their forums. Which is actually more appropriate, as it is an issue with their drivers not properly interfacing with all of DX9.

Both camps had pretty much written off DX9 about 18 months or so ago. A big chunk of both brands' lines got sloughed off into legacy status. Forget exactly when it was in the AMD line (late 2012 or early 2013 I think), but for nVidia it was around their 340.xx to 343.xx driver releases. There are notes in there where anything pre-400 series has been dropped. So users have to use the older drivers for the proper legacy support (ie: pre DX10/11). Ever since then, all the newer cards have been solely dependent on the DX libraries to properly thunk back to DX9--which is where the problems come from. There is so much deprecation in Micro$oft's latest platforms (not just DirectX, also .NET and such as well), that with each new release more crap gets broken. You sometimes have to go back and enable older .NET just to get a program's installer to run properly because only 4.x is installed by default.

Things like that are all because Microsoft is moving away from those older methods faster than the vendors and the users are able to adopt the new methods Microsoft is thrusting on them. Look how they had to extend the XP end of life...it is still in use in some business circles regardless of no more support for it because the tools they use won't run properly in the newer OS environments. So, we pretty much are going to have to wait for the DX11 client to see how they remedy the stability problems on new hardware and other misbehaving things like broken hardware cursor and such that have plagued the game since it went public.

Quote:

---

Originally Posted by Raist

You don't hear much official response here because it was intended to be used as a user-to-user forum more than a direct line to the developers and such. It's detailed in the sticky welcoming you to this forum.

The vendors have more actively communicated with users though (both AMD and nVidia... unfortunately more so nVidia than AMD)...but that is over at their forums. Which is actually more appropriate, as it is an issue with their drivers not properly interfacing with all of DX9.

Both camps had pretty much written off DX9 about 18 months or so ago. A big chunk of both brands' lines got sloughed off into legacy status. Forget exactly when it was in the AMD line (late 2012 or early 2013 I think), but for nVidia it was around their 340.xx to 343.xx driver releases. There are notes in there where anything pre-400 series has been dropped. So users have to use the older drivers for the proper legacy support (ie: pre DX10/11). Ever since then, all the newer cards have been solely dependent on the DX libraries to properly thunk back to DX9--which is where the problems come from. There is so much deprecation in Micro$oft's latest platforms (not just DirectX, also .NET and such as well), that with each new release more crap gets broken. You sometimes have to go back and enable older .NET just to get a program's installer to run properly because only 4.x is installed by default.

Things like that are all because Microsoft is moving away from those older methods faster than the vendors and the users are able to adopt the new methods Microsoft is thrusting on them. Look how they had to extend the XP end of life...it is still in use in some business circles regardless of no more support for it because the tools they use won't run properly in the newer OS environments. So, we pretty much are going to have to wait for the DX11 client to see how they remedy the stability problems on new hardware and other misbehaving things like broken hardware cursor and such that have plagued the game since it went public.

---

Ahh thank you for that information...really stoked for 3.0 I cannot wait for that to ship

I always get this in OLN. Other zones seem fine but OLN even with relatively low population (if compared for example with S rank in other zones) causes a crash.

How many of you are using AMD Gaming Evolved/Raptr? I read somewhere that this causes some problems for some games. I'm currently testing the FF14 without it and so far everything is working fine after 3 hours.

Update:
I take that back, my game just crashed.

Are you guys trying the work around I posted? Just wondering.
Enable LOD and LOD streaming.