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

SIEdit crashes when opening JUKEBOX.SI #12

Open
MatiLol251 opened this issue Feb 19, 2024 · 6 comments
Open

SIEdit crashes when opening JUKEBOX.SI #12

MatiLol251 opened this issue Feb 19, 2024 · 6 comments

Comments

@MatiLol251
Copy link

MatiLol251 commented Feb 19, 2024

When i open JUKEBOX.SI, SIEdit does nothing at all, before it closes itself.
I load it using "Open" and "View SI File" and none of that works
The weirdest part is that if i open files such as "NOCD.SI" or "INTRO.SI" the app doesn't crash and can visualize the data correctly
Now i wonder why that doesn't happen with "JUKEBOX.SI"..
(Edit: i used libweaver build that appears in the "releases" tab)

@itsmattkc
Copy link
Collaborator

I can't recreate this on my end - my JUKEBOX.SI opens fine.

Can you share what version/language of LEGO Island you're using? Or alternatively, send your JUKEBOX.SI file in some way?

@MatiLol251
Copy link
Author

it's the spanish version

@MatiLol251
Copy link
Author

MatiLol251 commented Feb 19, 2024

maybe it's the fact that the voice samples are in higher quality than the english version. unfortunately, that means that the file is 91mb. No joke

@itsmattkc
Copy link
Collaborator

Confirmed the Spanish JUKEBOX.SI crashes libweaver. Will look into a fix for this.

@foxtacles
Copy link
Member

foxtacles commented Apr 8, 2024

I've investigated this issue a couple weeks back and we've found that the issue is in fact that the Spanish JUKEBOX.SI is corrupted. At file offset 0x2be0000, a split chunk is expected, but instead one can find a block of 2048 zero bytes. This trips up SIEdit, as well as the original game (the race theme gets stuck):

LEGO.2024-03-13.06-18-24.mp4

It would be possible to make SIEdit more "lenient" to accomodate for this faulty file though if we want to work around it.

@MatiLol251
Copy link
Author

Yes, I heard that tripping, but i thought it was part of the original release so I didn't think anything of it.

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

3 participants