There is a problem with decompressing the original data
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- tooling
Research direction
The report names the ExeFS and RomFS folders and the romfs.bin file that the setup step writes when it extracts the user's original data folder. Start by finding where that extraction happens and which of these outputs the game actually reads at runtime. Done means the duplicate copies are no longer written, the game still launches from the remaining data, and the maintainers have agreed which copy to keep.
Written by the indexing model from the issue text.
Description
Before you start
- I'm on the latest release, and the bug still happens there.
- I searched the existing issues and this one isn't reported yet.
Savage Wind version
0.4.1-alpha.4 (latest)
Game version
1.9.0
Your PC
win 11 26h2, rtx5060, 621.01, AMD R5 9600x
Where in the game
Game Setup Issue
What happened, and how to make it happen again
When you specify the original data folder, unnecessary disk space is used during the extraction process.
The only data required to run the game are the RomFS and ExeFS, which contain the necessary game data. The extracted folder contains ExeFS, RomFS, and romfs.bin, but these files all contain identical data.
Inside the ExeFS folder, there are duplicate files, excluding the executable information files and the RomFS folder and romfs.bin. Only one of the two should be kept.
Storage has become so expensive these days that I think it's better to avoid wasting disk space on unnecessary duplicate data.
Settings
No response
savagewind.log
It's not an in-game issue
Before sending
- This report contains no game files, keys, firmware, generated game code, save files or links to copies of the game.
- Dominant language
- C
- Stars
- 811
- Forks
- 37
- Avg merge
- 17m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Revivedx/SavageWindRecomp
-
aspect ratio 16:10Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Revivedx/SavageWindRecomp#402 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Revivedx/SavageWindRecomp#404 · 2 comments ·
Maintainers usually reply within 1 day
-
font is not workOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Revivedx/SavageWindRecomp#403 ·
Maintainers usually reply within 1 day
-
Support DLSSOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Revivedx/SavageWindRecomp#401 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Revivedx/SavageWindRecomp#400 ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
examples/dnsdoctor: cleanup.sh stops at the first missing piece of a setup.sh that did not finishOpenseverity: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
luainkernel/lunatik#2263 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
vercel-labs/scriptc#2910 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
darktable-org/darktable#22939 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
espressif/idf-extra-components#903 ·
Maintainers usually reply within 1 day
-
os: input_password leaves terminal echo disabled when reading failsPossibly taken @davlgd claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day