Guys completely out of topic here, but can anyone tell me where to find Warframe armor mod for fallout 4? i noticed the one shown in this mod is Ember and was wondering if there is somehow i can get a hold of one.
obsolete has become word that describes the world today. New thing arrives and suddenly everything made before it is called obsolete. Corporate is giving this trend a standing ovation, because it let's them sell more as people are getting taught to throw out things as soon as new model is released
As a pleb who only uses the GOG version even though he has had it on steam since launch, and has zero interest in NG, thank you! I know that Bethesda updates are inevitable and I have been doing them for over a decade, but NG is the first one that I just refuse to go to on PC.
For the hell of it I tried running the Starfield ASI version of this with fallout 4. Surprisingly it loaded fine. I added a diskCacheEnabler.txt file so I could see the console output, and it appears to be doing some type of file caching. Probably not optimally, but just wanted to share if anyone with more knowledge wants to check it out.
TL;DR: This mod seems to be responsible for CTD's regarding XAudio2_7.dll.
What happened? I was exploring the Commonwealth and wanted to visit Covenant for random trading. As I was approaching the Covenant area from the lake, my game started crashing. All the crashlogs were identical to one another, and all of them mentioned the same issue - the XAudio2_7.dll fail (audio driver crash).
How I tried to fix the issue: I followed the recommended actions from Buffout 4's Dictionary. The document in question suggests the following possible solutions that sadly didn't work on my system:
1) Install DirectX Runtimes June 2010 - I already had the said Runtimes installed; but even after uninstalling and installing them again, the issue was still present.
2) Disable Touch Keyboard and Handwriting Services, then restart PC - the services in question have been disabled on my system for as long as I can remember. I had these services disabled even before I had Fallout 4 installed.
3) Run PowerShell as administrator, enter regsvr32 and sfc /scannow commands, and restart PC - after running both commands, I received a message that there were no errors. I rebooted the machine anyways and, sadly, the outcome was the same . I attempted to solve the issue myself by placing the XAudio2_7.dll into the game's root directory (where Fallout4.exe is) - that too didn't work and I still experienced Audio crashes.
My next attempt was adding the following argument for Fallout 4 in Steam: WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%
Sadly, the argument trick didn't do it either.
Desperate for answers, I went through my download history and noticed that the only mod I've added since my last playtime is this one. I disabled it, and the crashing stopped.
Conclusion Disk Cache Enabler(DCE) is outstanding piece of work! It improves performance a lot on HDDs (not sure about SSDs). As much as I'd like to keep it in my load order, I cannot. With it, my game runs much smoother and the stuttering is pretty much gone. However, I don't want to sacrifice stability for performance.
Fallout 4 is very wonky game (even Vanilla). I want to keep the risk of CTDs to a minimum.
Still though, massive kudos for creating and sharing it! Hopefully DCE works better and without issues on other people's systems!
Endorsed nonetheless! Really hoping you can do something about this, but I 100% understand if there's nothing you can do.
Interesting report! Just so you know for the future, WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%is actually meant for running Fallout 4 under Proton on a Linux operating system, so there's no chance this would have worked under a Windows installation.
It's interesting that you're running into this crash in the first place. I'm a Linux user myself, running the GOG version of Fallout 4 under WINE. I had some trouble with Fallout 4 crashing on launch and at random intervals in-game due to xaudio2_7 related errors until I specifically added it as a native override in my winecfg settings. Since then, I've had complete stability with my installation, including using this Disk Cache Enabler plugin.
All this to say: the xaudio library is a strange piece of work indeed! It's possible that recent updates to Windows have caused it to become problematic when dealing with Fallout 4.
At any rate, thanks for providing this information and potential fix for those who may be specifically affected by it.
I know that WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command% is meant for Proton - I was hesitant at first but someone over at Discord suggested that it helped them solve their audio issues. They didn't say whether they use GNU/Linux or Windows, and as soon as I've seen winedlloverrides I knew it'd be something wine-related, but gave it a shot nonetheless (when you're desperate to play the damn' game, you really are desperate lol).
Regarding the xaudio library - yeah, it's very strange. I did get a new update to Windows - KB5001716 but I doubt it's related to crashes. Don't know, I'll have to test things out a bit more.
Either way, glad to see a fellow FOSS enjoyer! I managed to set up Fallout 4 on my machine quite easily, but due to the age and specs of my machine the performance is... not that great; hence I'm sticking with Windows for now.
I literally just did the Covenant quest after installing this, and was so confused at all of the CTDs that I've been getting around that area.
Thank goodness it has been replicated by others.
As has been mentioned before, I'm also occasionally getting infinite black loading screens when entering interior cells. There doesn't seem to be any rhyme or reason to it, other than it occurring after roughly an hour of playtime.
I didn't experience any infinite black loading screens, but I'm pretty confident that's because I've disabled black loading screens in High FPS Physics Fix config.
Don't take this the wrong way, but I'm glad I'm not the only one with crashing near Covenant with Disk Cache Enabler.
@RubberDuck001 Slow performance is the worst reason to stick with Windoze and the #1 reason to switch to Linux. Years ago, I had a (then old) decrepit Sony Vaio running Windoze 7 that couldn't get out of its own way, much less play anything, then I switched to Linux Mint and was playing FNV in no time. Take the leap, man!
I will take a leap once I get identical performance on it. At the moment of writing, all the games I try are working, but in games where I'd have > 60 FPS on Windows, on Linux I'd have about 40 and below.
Running the game is one thing, but playing the game is what matters. Sadly, due to my pretty dated hardware, I'm still not ready to switch to it full-time.
About 2 years ago I switched to it for my work and couldn't be happier. Not only is it light on resources, but everything is so easy and simple to do. Why search the web to download an installer package when you can just install it with a single command in terminal?
In a nutshell, I'm doing everything on Linux nowadays. Except when I want to play games, or if I'd need to modify a VS solution - in those two cases I'm booting to Windows.
I had such crashes long before Disk Cache Enabler is out, and it was traced to be a bug of Buffout 4 (confirmed) when you enable the BA2limit option (the one that allows you to load infinite ba2 archives). This is a TL;DR for me and I don't know if you have discussed about this but the more the better.
I've read about that on some Discord server (can't remember which one exactly)... So I wrote myself a Python script for counting and comparing!
I do have BA2 Archive limit 'fix' enabled in Buffout 4, but I haven't reached the limit yet. I disabled the archive limit, and still experienced crashes.
I don't have enough time to troubleshoot it any further as I just want to play the game after a day's work. Maybe the issue is unique to my machine? Maybe it affects other players running the same hardware/system? I don't know.
All I know is that once I disabled Disk Cache Enabler, my game stopped crashing. I've literally spent about 20 real-world minutes just roaming around the area (Covenant) and purposely tried to break something in order to crash the game - it didn't crash.
The plugin has not been updated since I originally posted the issue so I believe it's not solved yet. I'm not going to try it again as my load order is pretty much identical to the one I had when I initially posted this issue.
Do you experience CTDs near Covenant? Are you running the game on HDD or SSD? Which OS do you use?
I've gone by Covenant more than couple dozen times with zero CTDs. Could be conflicts with another mod, could be something unique to your setup, who knows. It works for me, so something is off with your setup if Disk Cache Enabler isn't working for you.
Setup: Steam / Vortex / FO4 downgraded NextGen (OldGen F4SE v0.6.23); OS: Windows 11; OS Drive: SSD PCIe 3.0/3.0 NVMe v1.4 M.2; Drive with Fallout 4 on it: SSD PCIe 3.0/4.0 NVMe v2.0 M.2;
And for those unaware, Buffout 4's BA2limit option is incompatible with Backported Archive2 Support System, so no one should be using it anyways if they want their downgraded NextGen Fallout 4 to work. I recommend using the open source version of Buffout 4 anyways, as it has more features and is more compatible recently.
You're right - gave it a shot yesterday and the crashes don't happen on my end anymore. I said that my current load order is very similar to the one I had when I initially posted this, and that's mostly true, but there are some differences.
The biggest ones are the addition of America Rising 2 and I've switched from old Mutant Menagerie to the newer Life Finds A Way. Back in October 2023, I crashed whenever I attempted to get near Covenant. However, as of July 2024, these crashes no longer happen.
I did, however, upgrade my machine a bit - I went from 16GB to 32GB of memory (upgraded primarily because of my work), and I think that plays a huge role as well.
I'm not sure how it's possible, but when I have this enabled I get the default main menu music rather than the music Classically Fallout Main Menu adds. Maybe the music is cached in some weird way that this overrides accidentally?
That's not from this, that's from the menu replacer. If you go to the files for classically fallout man menu, you should see a .wxm file, this is the music. Change the extension from .wxm to .wav and it should work perfectly. I did this and have had no issues.
I was getting an Infinite load screen too and after searching through 235 mods I had downloaded, I figured out MCM Booster was my culprit (MCM Booster needs an update for NG). If you are running MCM Booster and NG, track the mod for future updates and delete it. If you are not running MCM Booster, you might want to run through your mods and disable until your loading screens want to stop being buttholes...
I use Disk Cache as well and I am NOT getting an infinite load screen from this, however, it DOES need an update to work for NG if you are running FO4 NG like I am. I hope this helps someone. I also know that Transfer Settlements is a non starter as well for NG. I wasn't trying to update my FO4 but I screwed up. I CANNOT go back bc I have personal mods I made that uses CC that I want to keep. So, I have been running checks with MULTIPLE mods. Hopefully me being stuck on NG might end up benefitting others. I have been spending DAYS checking so much stuff I have not been able to play yet. If you have a question, ask. I'll answer if I can or test something if I can.
By far one of the most useful mods out there, should be in top category! My laptop kept heating up like a mad machine running Fallout 4 with over 200 mods active and performance kept decreasing over time as my machine couldn't keep up burning all the fuel, with this mod enabled I've already noticed major improvements to performance especially in long runs making the game run smooth like butter with 24gb ram and 4gb vram, and my Laptop heats less by half the amount
309 comments
-
1
-
2
-
3
- ...
-
14
-
JumpThanks
because either it has better alternative or something else, not because it doesnt load
TL;DR: This mod seems to be responsible for CTD's regarding XAudio2_7.dll.
What happened?
I was exploring the Commonwealth and wanted to visit Covenant for random trading. As I was approaching the Covenant area from the lake, my game started crashing. All the crashlogs were identical to one another, and all of them mentioned the same issue - the XAudio2_7.dll fail (audio driver crash).
How I tried to fix the issue:
I followed the recommended actions from Buffout 4's Dictionary. The document in question suggests the following possible solutions that sadly didn't work on my system:
1) Install DirectX Runtimes June 2010 - I already had the said Runtimes installed; but even after uninstalling and installing them again, the issue was still present.
2) Disable Touch Keyboard and Handwriting Services, then restart PC - the services in question have been disabled on my system for as long as I can remember. I had these services disabled even before I had Fallout 4 installed.
3) Run PowerShell as administrator, enter regsvr32 and sfc /scannow commands, and restart PC - after running both commands, I received a message that there were no errors. I rebooted the machine anyways and, sadly, the outcome was the same .
I attempted to solve the issue myself by placing the XAudio2_7.dll into the game's root directory (where Fallout4.exe is) - that too didn't work and I still experienced Audio crashes.
My next attempt was adding the following argument for Fallout 4 in Steam:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%
Sadly, the argument trick didn't do it either.
Desperate for answers, I went through my download history and noticed that the only mod I've added since my last playtime is this one. I disabled it, and the crashing stopped.
Conclusion
Disk Cache Enabler (DCE) is outstanding piece of work! It improves performance a lot on HDDs (not sure about SSDs). As much as I'd like to keep it in my load order, I cannot. With it, my game runs much smoother and the stuttering is pretty much gone. However, I don't want to sacrifice stability for performance.
Fallout 4 is very wonky game (even Vanilla). I want to keep the risk of CTDs to a minimum.
Still though, massive kudos for creating and sharing it! Hopefully DCE works better and without issues on other people's systems!
Endorsed nonetheless! Really hoping you can do something about this, but I 100% understand if there's nothing you can do.
Take care and keep up the great work!
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%It's interesting that you're running into this crash in the first place. I'm a Linux user myself, running the GOG version of Fallout 4 under WINE. I had some trouble with Fallout 4 crashing on launch and at random intervals in-game due to xaudio2_7 related errors until I specifically added it as a native override in my winecfg settings. Since then, I've had complete stability with my installation, including using this Disk Cache Enabler plugin.
All this to say: the xaudio library is a strange piece of work indeed! It's possible that recent updates to Windows have caused it to become problematic when dealing with Fallout 4.
At any rate, thanks for providing this information and potential fix for those who may be specifically affected by it.
I know that
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%
is meant for Proton - I was hesitant at first but someone over at Discord suggested that it helped them solve their audio issues. They didn't say whether they use GNU/Linux or Windows, and as soon as I've seen winedlloverrides I knew it'd be something wine-related, but gave it a shot nonetheless (when you're desperate to play the damn' game, you really are desperate lol).Regarding the xaudio library - yeah, it's very strange. I did get a new update to Windows - KB5001716 but I doubt it's related to crashes. Don't know, I'll have to test things out a bit more.
Either way, glad to see a fellow FOSS enjoyer! I managed to set up Fallout 4 on my machine quite easily, but due to the age and specs of my machine the performance is... not that great; hence I'm sticking with Windows for now.
Have a good one, comrade!
Thank goodness it has been replicated by others.
As has been mentioned before, I'm also occasionally getting infinite black loading screens when entering interior cells. There doesn't seem to be any rhyme or reason to it, other than it occurring after roughly an hour of playtime.
Don't take this the wrong way, but I'm glad I'm not the only one with crashing near Covenant with Disk Cache Enabler.
Running the game is one thing, but playing the game is what matters. Sadly, due to my pretty dated hardware, I'm still not ready to switch to it full-time.
About 2 years ago I switched to it for my work and couldn't be happier. Not only is it light on resources, but everything is so easy and simple to do. Why search the web to download an installer package when you can just install it with a single command in terminal?
In a nutshell, I'm doing everything on Linux nowadays. Except when I want to play games, or if I'd need to modify a VS solution - in those two cases I'm booting to Windows.
This is a TL;DR for me and I don't know if you have discussed about this but the more the better.
I do have BA2 Archive limit 'fix' enabled in Buffout 4, but I haven't reached the limit yet. I disabled the archive limit, and still experienced crashes.
I don't have enough time to troubleshoot it any further as I just want to play the game after a day's work. Maybe the issue is unique to my machine? Maybe it affects other players running the same hardware/system? I don't know.
All I know is that once I disabled Disk Cache Enabler, my game stopped crashing. I've literally spent about 20 real-world minutes just roaming around the area (Covenant) and purposely tried to break something in order to crash the game - it didn't crash.
Do you experience CTDs near Covenant? Are you running the game on HDD or SSD? Which OS do you use?
Setup: Steam / Vortex / FO4 downgraded NextGen (OldGen F4SE v0.6.23);
OS: Windows 11; OS Drive: SSD PCIe 3.0/3.0 NVMe v1.4 M.2;
Drive with Fallout 4 on it: SSD PCIe 3.0/4.0 NVMe v2.0 M.2;
And for those unaware, Buffout 4's BA2limit option is incompatible with Backported Archive2 Support System, so no one should be using it anyways if they want their downgraded NextGen Fallout 4 to work. I recommend using the open source version of Buffout 4 anyways, as it has more features and is more compatible recently.
The biggest ones are the addition of America Rising 2 and I've switched from old Mutant Menagerie to the newer Life Finds A Way. Back in October 2023, I crashed whenever I attempted to get near Covenant. However, as of July 2024, these crashes no longer happen.
I did, however, upgrade my machine a bit - I went from 16GB to 32GB of memory (upgraded primarily because of my work), and I think that plays a huge role as well.
Uninstalled it for now will try a few hours without it.
I use Disk Cache as well and I am NOT getting an infinite load screen from this, however, it DOES need an update to work for NG if you are running FO4 NG like I am. I hope this helps someone. I also know that Transfer Settlements is a non starter as well for NG. I wasn't trying to update my FO4 but I screwed up. I CANNOT go back bc I have personal mods I made that uses CC that I want to keep. So, I have been running checks with MULTIPLE mods. Hopefully me being stuck on NG might end up benefitting others. I have been spending DAYS checking so much stuff I have not been able to play yet. If you have a question, ask. I'll answer if I can or test something if I can.
-
1
-
2
-
3
- ...
-
14
-
Jump