Ideas
Hey, there
Wanted to reach out on this one and see if we can get some Crash logs from you. When you get a chance, can you navigate to C:\Users\Username\Documents\Battlefield 6\CrashDumps and attach the file so we can take a look?
Cheers
Wouldn't let me attach directly via comment - I tried just 1 and it didn't work.
Here's a link to copies of them in Google Drive and shared on my public gaming email. I zipped them. Will you let me know once you have them so I can take the link back down? Thank you :) If you have a different way you'd like me to get them to you, just let me know!
[removed link]
I can't tell you how much I appreciate this! I love BF6 and that map, and I always have to avoid it.
(Cm Edit - Removed Link)
- EA_Shepard2 months ago
Community Manager
RockTheMoose
Hey, thereOf course. We all have those games we love and want to play all the time. I got the link. I removed it from your post just to keep things on the up and up, but I saved it and passed it over to the team so they could take a look. I will update you when I get an update.
In the meantime, though, I know you have tried some things to get it working, but can you do me a solid and just give the short short version of the steps you have tried since this morning? I don't want to assume you have done something you may not have.
Cheers.
- RockTheMoose2 months agoSeasoned Newcomer
I suppose just refer to OP above for every step I tried... The only thing I've done since then is:
- Make sure my GPU and chipset drivers are up to date (frequently)
- Occasionally verify Steam install files. (rarely)
To reproduce crash:
- Go to New Sobek City (any non-portal mode)
- Run around in or near those buildings. Even in TDM, before shots have been fired, before any destruction, no vehicles, no chaos: Just run around. Sometimes it happens in the first 10 seconds, sometimes takes 2 minutes, but rarely longer than that.
The only other similar crash was the Fort Lyndon "downtown" crash that would happen right around the time of RedSec's launch, but that was fixed fairly quickly (I think it was a GPU driver update that did it but I can't say for certain)
- EA_Shepard2 months ago
Community Manager
RockTheMoose I appreciate the info. One more question. For AMD, have you, by chance, rolled back to a previous driver to test it?