Skip to content

When booting up the game it crashes #3

Closed

Description

@dasuke216-lab

Release

1.0.3

Problem

Crash or console shutdown

What happened?

when booting up the game, after a minute or so of black screen it shuts down the console

Log

logs.zip

Checks

  • I'm using an unmodified release and my own supported Ocarina of Time ROM.
  • I searched the existing issues for this problem.

Activity

  1. becaring commented on Nov 8, 2026

    @becaring
    Owner

    Thanks for the logs, they showed a real bug. When 3Shipsty hit an error during startup, showing the error message crashed the game, so you got a black screen and then the console shut off. 1.0.4 fixes that: https://github.com/becaring/3Shipsty/releases/tag/v1.0.4

    Your log stops at the step where the game looks for your ROM. The error it was trying to show was most likely “No ROM archives found”, which means it didn’t find a ROM it recognizes beside 3Shipsty.xex. With 1.0.4 you’ll see the message on screen, and logs\startup-fault.txt records it.

    After you update, please check:

    The ROM is in the same folder as 3Shipsty.xex, not in a subfolder, and ends in .z64, .n64 or .v64.
    It’s one of the versions listed in supportedHashes.json.
    If it still doesn’t start, attach the new logs folder here.

  2. dasuke216-lab commented on Nov 8, 2026

    @dasuke216-lab
    Author

    logs.zip

    I have updated to 1.0.4.
    I have checked that the rom is in the same folder as 3Shipsty.xex and ends in .z64, .n64 or .v64.

    I have checked that the ROMS I used are the versions listed in supportedHashes.json which are:

    1. "name": "NTSC 1.0 (US)",
      "sha1": "ad69c91157f6705e8ab06c79fe08aad47bb57ba7"
      and
    2. "name": "NTSC 1.2 (US)",
      "sha1": "41b3bdc48d98c48529219919015a1af22f5057c2"

    This image below is what pop up when first boot after updating

    Image

    Then this video below is after deleting oot.o2r and boot it up again. To note, this also happened when I first tried 1.0.3.

    IMG_8070.mov
  3. maurohoj commented on Nov 8, 2026

    @maurohoj

    same problem here...

  4. becaring commented on Nov 8, 2026

    @becaring
    Owner

    Thanks for the logs. They showed the crash happens while the game data is being built from your ROM, on the first launch. When it crashed, it left a half-written oot.o2r behind, and that’s what the “incompatible SoH version” message was about.

    1.0.5 fixes both: https://github.com/becaring/3Shipsty/releases/tag/v1.0.5

    Copy the new 3Shipsty folder over your old one and launch it. You don’t need to delete anything, because it removes the broken oot.o2r and builds it again by itself. If the crash happens again, it restarts and does a slower build that avoids it. The first launch may take about a minute.

    If it still fails, please zip the logs folder beside 3Shipsty.xex and attach it here.

  5. maurohoj commented on Nov 8, 2026

    @maurohoj

    now, i'm with this problem. My rom is compatible with SHA-1 41b3bdc48d98c48529219919015a1af22f5057c2.
    Using 1.0.5v

    Image
  6. becaring commented on Nov 8, 2026

    @becaring
    Owner

    Please attach your logs, @maurohoj

  7. dasuke216-lab commented on Nov 8, 2026

    @dasuke216-lab
    Author
  8. becaring commented on Nov 8, 2026

    @becaring
    Owner

    Thanks. Looking into this now.

  9. becaring commented on Nov 8, 2026

    @becaring
    Owner

    Thanks for the logs, they pinpointed it. The part that builds oot.o2r from your ROM used a text format the Xbox 360’s C runtime doesn’t support, and the console treats that as a fatal error. My test console runs a debug monitor that skips past it, which is why it never showed up in testing. It wasn’t your ROM, your setup, or anything you did.

    1.0.6 should fix it: https://github.com/becaring/3Shipsty/releases/tag/v1.0.6

    If it still fails, attach the logs folder again.

  10. dasuke216-lab commented on Nov 8, 2026

    @dasuke216-lab
    Author

    It finally works thank you. Tested on boss rush on a boss n running at 60 fps. So far no problems.

  11. becaring commented on Nov 8, 2026

    @becaring
    Owner

    Wonderful! Closing this now, be sure to reopen or make a new issue if needed. Have fun :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions