AMD recommends using the graphics drivers provided by your notebook's manufacturer (OEM) as the manufacturer has customized the drivers to support the built-in display and the features and functions specific to the notebook. Customized graphics drivers are available for download from most notebook manufacturer's web site.
If the current operating system is not the version originally installed on the notebook it may not meet all requirements and compatible graphics drivers may not be available. Please refer to the notebook manufacturer for supported operating systems and drivers.
AMD Mobility Radeon™ Graphics Driver:
AMD provides generic reference drivers for AMD Mobility Radeon graphics with limited support for notebook specific features and functions.
Really? Use the OEM driver is the cure!? If AMD recommends only using the original OEM drivers, (they are 15.7.n at this point), then why does the driver keep prompting me to update to the latest driver for the 2 R9 M290x Crossfire cards installed in it?
(As a side query, once the drivers are in, they cards are identified as HD8970s, only MS drivers identify them as R9 M290x cards. If you market an updated/upclocked card by a new number, why don't the drivers identify them that way?)
The new drivers are downloaded from AMD as the recommended ones for the cards, by AMD. So, are you saying that AMD recommends not using the drivers that AMD recommends I use?
Not sure what or why you posted what seems to be an unrelated issue in regards to the topic title.
You have a laptop computer...which is entirely different than the issue posted. There are many differences in updating a desktop graphics card vs a laptop. Totally different. Laptop graphics update...How to
Instead of hijacking someones thread...start your own and include > INFORMATION REQUIRED WHEN POSTING A QUESTION
I have a gaming laptop with EXACTLY THE SAME ISSUE AS THE OP. I simply cannot use this fix, because it introduces a different fault caused by the newer driver that AMD recommends for my graphics cards.
Rolling back to 17.11.1 does seem to have helped, by the way, and instead of dozens of only 64kB DX shader cache files, I now have a new 32MB one after playing Destiny 2 again.
The long load times was fixed long ago with new driver(can't recall which one), and is still not a problem on newer drivers. So you will have the same issue by using older drivers.
If you are having some other issue with the game on newer drivers, start a new thread.
Seeing your recent posts on other threads e.g. Black Screen on Laptop , may be a better idea to start a new thread and list your issues/main issue on current driver.
Your going to have a hard time trying to get possible fixes, by posting all over the forum on other threads.
Sorry. The original post was because I have been having the same issue as this thread. I found a fix here, of rolling back to 17.11.1 drivers, but unfortunately the newer drivers that have a proper fix are useless to me.
I edited the original post to state this explicitly as you & kingfish missed that I stated that I play it as well & the implication that the reason for posting was that I have the same issue.
From reading this thread, I did find a solution of sorts, which you would have seen if you read all of the post to which you replied. Installing the older driver LISTED IN THIS THREAD, (17.11.1), is a partial fix. The latter 'proper' fix of the newer driver, however does not work, since that driver introduces the problems addressed in the other thread and was only mentioned as an afterthought in my original post, but which you and kingfish seem to have mistakenly taken as my main issue in this thread. You are even replying to my post where I explicitly stated that I had the same problem & this thread gave me a partial fix for it.
Não quero receber mensagem
Em ter, 19 de fev de 2019 às 02:30, pokester <firstname.lastname@example.org>
Long load times in Destiny 2 with 17.12.1 and 17.12.2
reply on Long load times in Destiny 2 with 17.12.1 and 17.12.2
helpful. View the full reply