-
Notifications
You must be signed in to change notification settings - Fork 6
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
Source compiled 1st_read.bin results in crash during openMenu execution #50
Comments
got something like this here, I can compile it, run it with card manager and save changes, but console sucks on sega logo |
I haven't made any further progress on this, but I was working on SAROO and had similar issues. Turned out that running the latest toolchain wasn't compatible with the project. You might try downgrading KOS to at least 3 years ago. |
hey! just downloaded the latest build source code (from 2021 08 dec) and also the megavolt fork, but in both cases it keeps getting me larger files, and im getting crashes and stucks at sega logo. am I building it wrong? |
ARG VER="gcc-9"
FROM haydenkow/dcdev-kos-toolchain:${VER}```
on the Dockerfile we already got a version gcc-9 from 3 years ago setted |
Digging through megavolt85 fork, I found that he has a KOS patch in root directory. May be related? |
Describe the bug
Upon launching openMenu on both real hardware and emulator, the application crashes when using 1st_read.bin compiled from source.
I have KOS toolchain installed and I can successfully build individual homebrew applications and launch them on both emulator and hardware.
If I swap back in your release 1st_read.bin, then it works as expected. Any idea as to what I could be doing wrong when generating the 1st_read.bin? I haven't made any source code changes. I've tried on both macOS and ubuntu without success.
To Reproduce
Steps to reproduce the behavior:
master
branchExpected behavior
openMenu launches with compiled image the same as release image.
Screenshots
Flycast log:
Desktop (please complete the following information):
Additional context
issue on my fork: savaughn#1
The text was updated successfully, but these errors were encountered: