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

Crash Error: Loading the PS4 Memory.dat folder. #18

Closed
Aeramis opened this issue Oct 4, 2020 · 5 comments
Closed

Crash Error: Loading the PS4 Memory.dat folder. #18

Aeramis opened this issue Oct 4, 2020 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@Aeramis
Copy link

Aeramis commented Oct 4, 2020

Here you go. Honestly, I think I must be doing something wrong and it isn't the program. Right now when I load the program it is auto linked to the Steam save I have. So maybe that is the issue.

report.zip

@cengelha cengelha self-assigned this Oct 5, 2020
@cengelha
Copy link
Member

cengelha commented Oct 5, 2020

No that hasn't anything to do with the Steam path.

Do you use SaveWizard or SaveMounter?
Could it be that you modified your memory.dat manually before? The report says that there is more data than expected so I assume it read more bytes than the json part actually has which could happen if the metadata at the beginning of the file doesn't match the actual data.

Would you attach your memory.dat here? Then I can anaylse it to be sure what happens.

@Aeramis
Copy link
Author

Aeramis commented Oct 5, 2020

Ahh.. That might be the issue, I was using a modified dat file. Let me get my save loaded in the game and then save via game again. I'll let you know.

@Aeramis
Copy link
Author

Aeramis commented Oct 5, 2020

Ok, I am able to get it to load in the program. I can't seem to save it though as it crashes. Does the memory.dat need to be in a specific folder?

I added a few things to the save, also, I noticed that some of item products have a higher amount for Max Amount. For example, Atlas Stones show Max Amount of 10 when it should only be 5 per stack.

Here is the report.
report.zip

@cengelha
Copy link
Member

cengelha commented Oct 5, 2020

No, no specific folder necessary. It's now the same bug as in #20 and will be fixed in the next release.

About the stacks: Don't know but maybe HG changed it in Origins for the stones (they definitely did for some items). The next planned release (see roadmap will cleanup a lot of the current mess and if it's not the right stack size now, it will be then.

@cengelha cengelha added the bug Something isn't working label Oct 5, 2020
@Aeramis
Copy link
Author

Aeramis commented Oct 7, 2020

Just checking up to see how progress is going?

@cengelha cengelha closed this as completed Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants