Linux / Steam Deck Error: Insufficient free space on the drive to unpack archives, 8GB is required at least.
Solution: - Move 'Fallout New Vegas' folder from '../steamapps/common' to '/home/deck' - Run Protontricks and select a game other than Fallout New Vegas. Because you moved the the Fallout New Vegas folder, Protontricks will error if you choose Fallout New Vegas - Select the default wineprefix, Run winecfg, 'Drives' tab, Add a new drive that is not C, D, E or Z. set its path to '/home/deck', Select Ok and then exit Protontricks - Run Flatseal and select Protontricks. In the 'Filesystem' > 'Other files' section, Add a folder and set it to '/home/deck', Exit Flatseal - Run FNV BSA Decompressor.exe and select the same game that you used earlier in the Protontricks launcher that is not Fallout New Vegas - Select Browse and use the new drive letter that you added in My Computer and select the 'Fallout New Vegas' folder - Select Decompress and let the tool finish. The completion screen might look messed up but you can close it once it is done. - Move the 'Fallout New Vegas' folder from '/home/deck' back to the '../steamapps/common' folder you originally moved it from.
If you're not on Steam Deck and have Protontricks installed as a native package and not via Flatpak, you can copy the folder instead of moving it (which lets you select the FNV prefix for convenience’s sake) and skip the Flatseal step, then you can delete the '../steamapps/common/Fallout New Vegas' folder and move the copied folder back.
if you're as dumb as me you should know that before running the tool you must first move all the files inside the "FNV BSA Decompressor..." folder into your base game folder (ex:...\steamapps\common\Fallout New Vegas).
Extract the archive and run FNV BSA Decompressor.exe.
The Fallout: New Vegas and Decompressed Archives paths should be filled by default (Root folder and Data folder respectively). If they aren't, close the program and re-run your game launcher to generate the required registry key. The EGS release of the game does not create any keys! You need to select the game folder manually!
Click Decompress, wait for the process the finish, then exit the program once finished.
This is from Viva New Vegas' guide. Chances are, he's probably got the EGS version. Mine is Steam version and it automatically inputs the file location for me when running the decompressor. I'll put my file directory in case somebody is confused, but it will not be the exact copy for everyone since I moved the steam folder out of program files.
Do you need ultimate edition in order to run this mod? When I click to decompress it gives me an error saying that the dead money dlc sounds file doesn't exist...
FNV BSA Decompressor.exe Application Error 0x000007b on Win 10 64bit
I am trying to run FNV 1.4.0.525(a) from GOG on a standard laptop Windows 10 64bit machine. Installation is outside Windows system folders.
The game itself is running without any visible problems. It seems to be a conflict between decompressor and Windows.
I tried running Decompressor with compatibility setting to Windows 7 and running it as an admin. Neither helped.
I can unpack .bsa with other tools and set .bsa Invalidation in Fallout.ini but can someone provide a guide how to manually do all the other fixes the decompressor does:
Quoting from description:
"Simple tool to decompress the FNV BSA's and repack them without zlib to increase performance on modern systems. Additionally, it transcodes all sound effects in .ogg format to .wav so they function in the game. It also extracts any mp3 files to loose files because they will not play when in a BSA."
Okay, tried to use today and just a heads up that if you are going to bother breaking the software on purpose when the game is installed in Program Files you will get a lot fewer complaints by also making sure to check that the game isn't also located in the Steam folder within Program Files.
While there are a number of security protections on a typical folder in Program Files, Steam has made sure to undo absolutely all of them within its install folder. It is actually kind of ridiculous the extent to which they have done this and how it surely provides numerous opportunities for privilege escalation, but that is besides the point.
The point is that for Steam to not ask even unprivileged users when installing games it needs the exact same permissions modding typically. This is why so may people are downright perplexed by the responses about potentially having issues with installing games in Program Files. Many of us have just been using Steam for all of our games for so long now and have thus never had permission problems with mods.
Anyway I don't need help with this, thankfully the checks as is can be circumvented by just making a link to the folder installation folder so that the path doesn't have Program Files in it. I just wanted to try and help out the situation here because it bothers me when we live in a stupid reality where things are measurably worse than they could be for no reason whatsoever.
For reference if the message had simply told me that it didn't work because of permission issues I would have moved the game. The current "it don't work" popup is poorly written that I had to look into it to be sure what to do next(note that the user doesn't know what folders will work if you just tell them that one particular one doesn't, for all I know it could be printing this error by looking at folder permissions or something smart like that).
Also note there are simple robust solutions to users not reading warnings, like telling the user the workaround in the warning in a way that users have no choice but to read. If the popup had told me I had to run the program from the command line with the flag "--I-think-I-am-smarter-than-the-developer-and-when-things-dont-work-I-will-know-it-is-because-I-did-this-and-I-should-just-reinstall-the-game-elsewhere" then your bases would be pretty covered(with slightly more work you can also make me type it in if you want to avoid having copy and paste as an option, but no need to do that unless forced).
It's ridiculous that the program refuses to continue, when it's not even necessary with Steam's permission modifications. Judging by YouTube comments, thousands of people have gotten halfway through modding lists only to get stuck at this error and have to start over.
For anyone who does not know, you can bypass the check by running cmd.exe as administrator and running command: mklink /d "C:\Fallout New Vegas" "C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas"
Then you can enter these paths in BSA Decompressor:
Path to installationC:\Fallout New VegasDecompressed archivesC:\Fallout New Vegas\Data
You will see the program works just fine with no permission modifications, like stephenrhamilton said.
An alternative option that doesn't require the command line is to just move the Fallout New Vegas folder to your desktop, run the program, and then move it back. That could rarely cause issues with some mod managers like Vortex, but it's probably fine.
Leaving something behind for those in need. Tried to run this tool on enplczru version. It won't work because FNV BSA Decompressor is configured to work with basic english version of the game only. Description is ignoring that small detail. Either way if one is blocked with "Sharing violation" warning or stuff about missing misc.bsa then it might be just that. My solution was to fool decompressor; just renamed "Fallout New Vegas enplczru" into "Fallout New Vegas" and it worked. Well it has to - because that's the main difference between Basic, PCR or RU - folder name.
Lucy’s right. FO3 modding is almost completely dead, and TTW/FNV modding has come out with a ton of really cool stuff recently. It’s very easy to play TTW and just ignore anything FNV related, if you just want to play FO3.
Stay away from Fallout 3 modding! I did this for months until at some point I only had memory leaks and the game no longer ran. I then switched to TTW, although I was reluctant for a long time because I didn't want to lose my modding progress. and now I have no stress at all. That was the best decision I've made in a long time. I can only strongly recommend it.
Yo,i needed help with the decompressor, im trying to run it but it seems to get stuck at 90%.
Edit: Results that my "problem" wasnt a problem at all, it just becomes reaaaaally slow at 90% download, and then again at like 99%, but gonna leave this here for other unpatient people like me.
Note for Steam Deck users: If you have another Wine program to open .exe files (Q4Wine like myself) make certain you are opening the decompressor with ProtonTricks. In regards to the step that says Run FNV BSA Decompressor.exe and select the same game that you used earlier in the Protontricks launcher that is not Fallout New Vegas.
What if you have libogg.dll and OGG Vorbis Libraries files : libvorbis.dll and libvorbisfile.dll, do we just delete the libogg.dll and keep libvorbis.dll and libvorbifille.dll so it would be the same as the update?
789 comments
Insufficient free space on the drive to unpack archives, 8GB is required at least.
Solution:
- Move 'Fallout New Vegas' folder from '../steamapps/common' to '/home/deck'
- Run Protontricks and select a game other than Fallout New Vegas. Because you moved the the Fallout New Vegas folder, Protontricks will error if you choose Fallout New Vegas
- Select the default wineprefix, Run winecfg, 'Drives' tab, Add a new drive that is not C, D, E or Z. set its path to '/home/deck', Select Ok and then exit Protontricks
- Run Flatseal and select Protontricks. In the 'Filesystem' > 'Other files' section, Add a folder and set it to '/home/deck', Exit Flatseal
- Run FNV BSA Decompressor.exe and select the same game that you used earlier in the Protontricks launcher that is not Fallout New Vegas
- Select Browse and use the new drive letter that you added in My Computer and select the 'Fallout New Vegas' folder
- Select Decompress and let the tool finish. The completion screen might look messed up but you can close it once it is done.
- Move the 'Fallout New Vegas' folder from '/home/deck' back to the '../steamapps/common' folder you originally moved it from.
Thank you zoidbiscuit.
This is occurring when I try to decompress after following the steps above. Anybody have any idea what I did wrong?
The EGS release of the game does not create any keys! You need to select the game folder manually!
This is from Viva New Vegas' guide. Chances are, he's probably got the EGS version. Mine is Steam version and it automatically inputs the file location for me when running the decompressor. I'll put my file directory in case somebody is confused, but it will not be the exact copy for everyone since I moved the steam folder out of program files.
"Simple tool to decompress the FNV BSA's and repack them without zlib to increase performance on modern systems.
Additionally, it transcodes all sound effects in .ogg format to .wav so they function in the game.
It also extracts any mp3 files to loose files because they will not play when in a BSA."
Much appreciated
While there are a number of security protections on a typical folder in Program Files, Steam has made sure to undo absolutely all of them within its install folder. It is actually kind of ridiculous the extent to which they have done this and how it surely provides numerous opportunities for privilege escalation, but that is besides the point.
The point is that for Steam to not ask even unprivileged users when installing games it needs the exact same permissions modding typically. This is why so may people are downright perplexed by the responses about potentially having issues with installing games in Program Files. Many of us have just been using Steam for all of our games for so long now and have thus never had permission problems with mods.
Anyway I don't need help with this, thankfully the checks as is can be circumvented by just making a link to the folder installation folder so that the path doesn't have Program Files in it. I just wanted to try and help out the situation here because it bothers me when we live in a stupid reality where things are measurably worse than they could be for no reason whatsoever.
For reference if the message had simply told me that it didn't work because of permission issues I would have moved the game. The current "it don't work" popup is poorly written that I had to look into it to be sure what to do next(note that the user doesn't know what folders will work if you just tell them that one particular one doesn't, for all I know it could be printing this error by looking at folder permissions or something smart like that).
Also note there are simple robust solutions to users not reading warnings, like telling the user the workaround in the warning in a way that users have no choice but to read. If the popup had told me I had to run the program from the command line with the flag "--I-think-I-am-smarter-than-the-developer-and-when-things-dont-work-I-will-know-it-is-because-I-did-this-and-I-should-just-reinstall-the-game-elsewhere" then your bases would be pretty covered(with slightly more work you can also make me type it in if you want to avoid having copy and paste as an option, but no need to do that unless forced).
For anyone who does not know, you can bypass the check by running cmd.exe as administrator and running command:
mklink /d "C:\Fallout New Vegas" "C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas"
Then you can enter these paths in BSA Decompressor:
Path to installation
C:\Fallout New VegasDecompressed archivesC:\Fallout New Vegas\Data
You will see the program works just fine with no permission modifications, like stephenrhamilton said.
An alternative option that doesn't require the command line is to just move the Fallout New Vegas folder to your desktop, run the program, and then move it back. That could rarely cause issues with some mod managers like Vortex, but it's probably fine.
Stay away from Fallout 3 modding! I did this for months until at some point I only had memory leaks and the game no longer ran. I then switched to TTW, although I was reluctant for a long time because I didn't want to lose my modding progress. and now I have no stress at all. That was the best decision I've made in a long time. I can only strongly recommend it.
Edit: Results that my "problem" wasnt a problem at all, it just becomes reaaaaally slow at 90% download, and then again at like 99%, but gonna leave this here for other unpatient people like me.
1) is the decompressed BSA bigger or smaller filesize than the original?
2) will this work for fallout 3 and/or tes4 BSA?