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

SaintCoinach.Cmd "rawexd": "Export of QuestDefineClient failed: Unable to read beyond the end of the stream." #135

Open
Sophira opened this issue Jan 19, 2023 · 4 comments

Comments

@Sophira
Copy link

Sophira commented Jan 19, 2023

Since FFXIV Patch 6.3 (game version 2022.12.23.0000.0000), I've been getting an error from SaintCoinach.Cmd when I use the rawexd command: "Export of QuestDefineClient failed: Unable to read beyond the end of the stream.":

C:\saintcoinach>SaintCoinach.Cmd.exe "C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn"
Game version: 2023.01.11.0000.0000
Definition version: 2023.01.11.0000.0000
SaintCoinach.Cmd (Version 0.1.0.0)
> rawexd
Export of QuestDefineClient failed: Unable to read beyond the end of the stream.
6687 files exported, 1 failed

I first discovered this behaviour on Linux with WINE, but before reporting I verified that it also occurs on a regular Windows 10 installation on a different computer - and that's where the transcript above is from.

I'm using the latest binary release of SaintCoinach as of the time of writing (based on commit bdd2ef2).

Prior to patch 6.3, this was working without any issues, so it's quite recent.

If you need any more information, please let me know!

@Sulca-dev
Copy link

I have the exact same error with "exd" and "sql" commands, changing langage ("en" or "fr") doesn't help.

@e-huff
Copy link

e-huff commented Feb 13, 2023

This looks like a bug in XivString.Decode, but the issue seems to be intermittent. I was trying to debug the issue, but it disappeared after 5 or so attempts. I'll try again later today to see if I can replicate the issue.

@IcarusTwine
Copy link
Contributor

Cause of the issue:
Header file exist for the the file, (exh exists)
Data file does not exist (exd does not exist)
I personally don't know c very well so I cannot fix this, however we are not missing out on much as there is no actual data there.

@Sulca-dev
Copy link

My real problem with this bug is that it stops the sql command unlike the exd command which ignores the file.
I don't know if it possible to make sql treatment skip missing data files ?

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

No branches or pull requests

4 participants