PC Drivers & Software

[GanomPlaysTwin]

Hello,

I have a Asus Zephryus G14 2022 with a RX 6700s and Ryzen 9 6900HS, and was running Adrenalin 23.7.1, when an update appeared for 23.7.2. I updated the drivers and ran the game as usual, expecting a long loading time due to shader compilation, but the loading times were being suspiciously long. I could not load into a match, but could load into the lobby. After about 10 minutes, the game would crash. 

Assuming the drivers were the cause, I rolled back the drivers to 23.7.1, verified the game, cleared shader cache in Adrenalin, and reinstalled the game too, and none of this fixed it.

The game is able to be loaded in DirectX11, but I prefer the features in DirectX12. 

Please advise. I appreciate your time.

[BillyFeltrop]

I'm sorry to hear that you're experiencing issues with Fortnite and DirectX12 after updating to Adrenalin 23.7.2. Here are some troubleshooting steps you can try to resolve the problem:

1. Clean Installation of Drivers: Completely uninstall the current drivers using Display Driver Uninstaller (DDU) and then perform a clean installation of the Adrenalin 23.7.2 drivers. This can help ensure that any potential driver conflicts or remnants from previous installations are removed.

2. Verify Game Files: In the Epic Games Launcher, go to the Library, click on the three dots next to Fortnite, and select "Verify." This will check and repair any corrupted or missing game files that might be causing the issue.

3. Check for Fortnite Updates: Ensure that Fortnite is up to date with the latest patches and updates from the Epic Games Launcher.

4. Check DirectX and Windows Updates: Ensure that your DirectX and Windows operating system are also up to date with the latest updates from Microsoft.

5. Check Game Settings: In Fortnite's graphics settings, try lowering the DirectX12-specific settings to see if that helps. You can also try running the game in Fullscreen mode instead of Borderless Windowed mode.

6. Disable Overlays and Background Applications: Some overlays (like Discord overlay, AMD Radeon Overlay, etc.) and background applications can cause conflicts with games. Try disabling these overlays and closing unnecessary background applications while running Fortnite.

7. Temperature and Power: Ensure that your GPU and CPU temperatures are within safe limits, and your power settings are configured correctly to avoid any performance issues.

8. Contact Epic Games Support: If the issue persists, consider reaching out to Epic Games Support for more specific assistance.

Keep in mind that driver updates and game patches can sometimes introduce new issues, and it might be necessary to wait for further updates or patches to resolve the problem. Meanwhile, using DirectX11 as a temporary solution can allow you to continue playing Fortnite until a fix is available for DirectX12.

As always, before making any changes to your system settings or performing updates, consider backing up important data and creating a system restore point, especially when dealing with driver installations.

I hope these steps help resolve the issue, and I appreciate your time. Good luck!

[GanomPlaysTwin]

I did all of these, but it still seems to be happening. I wonder if it's an issue with the latest Fortnite update not playing well with the AMD hardware. Or perhaps simply the AMD update ruined it.

[timmhenson]

I'm experiencing exactly the same thing even after trying to resolve it using these steps, as well as reinstallation Fortnite, VCC redistributables, DX12, and Adrenaline. After every update my framerate drops and Fortnite runs like trash (if it runs), but nothing else does. I was able to complete one round of BR using DX11, but whats the point of that?! I don't want to use DX11.

After testing a few other games and getting normal/excellent results I think its just Fortnite being trash.

[GanomPlaysTwin]

All my other games seem to be working fine. I'm wondering if this is a result of Fortnite's latest update not playing well with the hardware.

EDIT: After enabling nanite (ray tracing) settings it loaded into a match after 8 minutes, but ran horribly. I then switched back to non nanite mode and it loaded properly, but it ran much worse than ever before. It runs worse than when I would have nanite mode on before.

[timmhenson]

I saw on twitter yesterday Fortnite tried to post that the issues were resolved only to have them re-state they were hearing users were still experiencing issues and would be working on it an hour later.

[GanomPlaysTwin]

I'm noticing that my memory usage is going up steadily when it's loading as well. Of my 40 GB of RAM, it's reaching 20 GB used in just Fortnite. I'm wondering if this could be due to a memory leak caused by the updates (possibly on both AMD/Fortnite's end)

[timmhenson]

I was definitely seeing a HUGE increase in memory consumption when trying to connect to the BR loading area before the battle bus, but it would never finish "connecting.."

[xXAURUMXx]

Its incredible, 2 days and I can't play, I tried everything that is placed here and nothing works. If I try to play with DX12 the game doesn't even launch and if I play with DX11 the FPS drops, as I'm playing without meet the specs, can you help us to play decently.

[Cosmochris]

I have been dealing with exactly the same issue. My pc isnt anything crazy but it can run D12 no problem. Just like you, everything was running fine until the last update. All my other games run fine, fortnite is the only one that ive been having this issue with. I was starting to think it was my pc, i just lost my job so the last thing i need is my pc **bleep**ing up lmao. Im trying the nanite thing as i type this with a timer set..its been 2 minutes so far of it "connecting". It would be really nice like said if someone could aid us properly or tell us whats really going on. 

[samoa683]

Dx12 mode is still super heavy on your GPU I wouldn't get your hopes up too high as running it myself on a 3060ti is a struggle. Something you can try in the meantime is turning on dx12, close the game then apply read only to the file so it doesn't change it back to 11.

[shidnfard]

were you able to fix this issue