Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Titles show with incorrect size and do not install #171

Open
Rumblebelly5 opened this issue Jan 23, 2025 · 11 comments
Open

Titles show with incorrect size and do not install #171

Rumblebelly5 opened this issue Jan 23, 2025 · 11 comments
Labels
waiting for info Issue is waiting for info from users

Comments

@Rumblebelly5
Copy link

When pulling NSPs in Tinfoil, size is show incorrectly and title does not install

@a1ex4
Copy link
Owner

a1ex4 commented Jan 29, 2025

What do you mean it does not install, the file is not downloaded or is failing to be installed after download?

@a1ex4 a1ex4 added the waiting for info Issue is waiting for info from users label Jan 29, 2025
@Rumblebelly5
Copy link
Author

it appears to download the title, but does not install to my switch. I verified the NSP with NXFileViewer to be original before adding it to OwnFoil. It downloads too fast for the size, so it appears to be just downloading the file size that is showing in TinFoil

@a1ex4
Copy link
Owner

a1ex4 commented Jan 29, 2025

Do you have an example file where this happens, the actual vs displayed size? Is it a multicontent file?

@Rumblebelly5
Copy link
Author

Rumblebelly5 commented Jan 29, 2025

LoZ Echoes of Wisdom, NSP is 5.8G File currently shows as 304M in TinFoil

When I pull the file up on NXViewer it shows as original when checked and does not show as a multi content file.

Im not sure how much this matters, but I have it installed on a RPI3 running by itself, not in docker

@a1ex4
Copy link
Owner

a1ex4 commented Jan 29, 2025

It must have been a file that was incorrectly identified then, is there maybe another file that's 304M in the library?

@Rumblebelly5
Copy link
Author

its possible, how would I check that? how could I correct it?

@a1ex4
Copy link
Owner

a1ex4 commented Jan 29, 2025

You can check the size of the other files, I don't think you could directly correct it since it sounds like a bug / error in the identification.

@Rumblebelly5
Copy link
Author

There are a couple DLCs that are that size

@Rumblebelly5
Copy link
Author

Rumblebelly5 commented Jan 30, 2025

Just as an update, I was able to confirm that it has to be pulling the wrong info in. I separated the file and the update into its own folder and rescanned the library with just that folder and it installed just fine. I separated the DB file and opened it and found some inconsistencies with the way its populating the file location information in the DB.

How can i be of further assistance in this?

@a1ex4
Copy link
Owner

a1ex4 commented Feb 4, 2025

What do you mean by "inconsistencies with the way its populating the file location information in the DB"? Did you configure the console keys for identification?

@Rumblebelly5
Copy link
Author

The the file location information from one item to the next is in consistant in that it will have he whole path that I enter in the settings menu and have a seperate entery for the additional sub folders (ie: DLC or Update) and in other enteries it will have the subfolders listed in the location field.

I managed to fix most of the issues by delelting the console keys and jsut using the naming schema to create the database. Im still thinking about editing the database myself, but was wondering how the next version was coming along first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for info Issue is waiting for info from users
Projects
None yet
Development

No branches or pull requests

2 participants