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

fix padding #4

Merged
merged 1 commit into from
Feb 1, 2024
Merged

fix padding #4

merged 1 commit into from
Feb 1, 2024

Conversation

trembon
Copy link
Owner

@trembon trembon commented Feb 1, 2024

should fix giwty#104

credits to: giwty#104 (comment)

@trembon trembon merged commit cbb6820 into master Feb 1, 2024
@trembon trembon deleted the fix-key-area-key branch February 1, 2024 20:32
@firebat20
Copy link

I am currently using the lastest test build. I am still get the error. "failed to read NSP [reason: missing Key_area_key[key_area_key_application_0f]]". Let me know if there is any more information you need.

@trembon
Copy link
Owner Author

trembon commented Feb 14, 2024

@firebat20 are you using the latest prod.keys? the one supplied in this repo will not work and will be removed soon
also, if the issue still persist i would need to know what game/update/dlc you are having problem with so i can test this on my side, so please open up an issue with this information if that is the case

@firebat20
Copy link

Yes, I have the most recent prod with fw 17.0. I have attached a csv of a couple of the errors. I have more in another scan.

errors.csv

@trembon
Copy link
Owner Author

trembon commented Feb 16, 2024

@firebat20 i'm only able to find one of these games as NSP and I have no problem processing those files. Could it be that you have had them processed from XCI to NSP and in that way made them unreadable?

@firebat20
Copy link

Thanks for looking into it. I have to check the source file, that might be the reason it is not working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Doesn't seem to use latest Key updates
2 participants