Skip to content

CTR Native Beta 5

Pre-release
Pre-release

Choose a tag to compare

@aalhendi aalhendi released this 19 Jun 17:05
· 44 commits to master since this release

CTR Native Beta 5

Fifth playtest beta for CTR Native.

What's New

  • Fixed purple token count in adventure pause menu.
  • Fixed audio volume scaling to match PSX hardware.
  • Fixed vehicle slope speed limiting.
  • Fixed empty bot rank slot crash. Pickup bot scheduling no longer crashes when end-of-race rank slots are empty (demo mode, certain battle configurations).
  • Fixed MIPS integer semantics across vehicle physics.
  • Fixed retail GTE state preservation for wobble effects.
  • Typed audio state machines.
  • Fixed note pointer types. SongSeq.firstNote/currNote
  • Continued source cleanup.

Platform

  • Windows x86
  • Linux x86, 32-bit executable
  • Requires an OpenGL 3.3 capable GPU/driver

Linux Notes

The Linux build is not fully static. SDL3 is linked statically, but the system
OpenGL/Mesa, windowing, audio, and glibc runtime come from the host OS.

This Linux build requires:

  • x86_64 Linux capable of running 32-bit/i386 binaries
  • 32-bit glibc runtime
  • 32-bit OpenGL/Mesa or vendor OpenGL driver
  • 32-bit X11 or Wayland runtime libraries
  • 32-bit ALSA/PulseAudio/PipeWire runtime libraries

It may require glibc 2.38 or newer.

Assets

Game assets are not included.

Create an assets/ folder next to ctr_native / ctr_native.exe and provide
extracted NTSC-U retail CTR assets:

  assets/
    BIGFILE.BIG
    SOUNDS/KART.HWL
    TEST.STR
    XA/
      ENG.XNF
      ENG/EXTRA/S00.XA ... S05.XA
      ENG/GAME/S00.XA ... S20.XA
      MUSIC/S00.XA ... S01.XA

Bug Reports

Run with:

  ctr_native --record

When reporting a bug, send the generated folder under:

  debug/reports/

Include the whole report folder, especially:

  input.ctrreplay
  state.ctrstates
  memcard.seed
  ctr-native.log

For Linux launch failures, also include:

  ldd ./ctr_native

Known Notes

  • This is a beta/playtest build.
  • Linux binaries remain experimental and may need distro-specific testing.
  • Replays are debugging tools and may still have limitations.