SUPER STAR LIVE

Where it actually stands

This page is generated from the project's own artifacts — 41 Wine trace logs, 13 captured frames and a diffed client tree. Where something is not yet true, it says so.

The crash, measured

18 of 41 runs ended in an unhandled page fault. The addresses cluster into 4 sites, and the same build reaches those sites on some runs and survives them on others.

Two of the four sites dereference a pointer that is only 1 or 0x48 bytes away from null. That is the signature of uninitialised pointer use inside the client, not of a missing or corrupt asset — the same archives render fine on the runs that survive. What triggers it is not yet known; we have deliberately not written a cause we cannot show.

A note on a red herring we chased and dropped: Wine also logs a DRI3 error, but it appears in only 5 of the 18 faulting runs and 2 of the clean ones, so it does not explain the crashes.

Verbatim from the logs

Unedited lines out of the trace files, one per distinct failure.

Every run we have

All 41 recorded runs, oldest first. "No crash line" means exactly that — no fault, exception or abort was logged, which includes runs the harness killed on a timeout while the client was still alive.

What the renderer actually draws

Every frame below is cropped to exactly the client's own 1024×720 window — no desktop, no Wine chrome, nothing outside what the game itself put on screen. Captions describe only what is visible in the frame.

The client tree

2.98 GB in place under client/offline/. The retail reference tree is 2.85 GB; the growth over retail is our own added files, not new game content.

What the offline copy adds

The patched tree measures 2.98 GB against retail's 2.85 GB — 127.7 MB larger. Every byte of that growth is accounted for by 15 files that do not exist in the retail tree, and all of them are ours:

127.6 MB of added files against a measured 127.7 MB tree delta. Eight of those files are same-size (9,818,112-byte) copies of the client executable, staged while testing patches, plus one captured backtrace and one small audio config. No new game content, no added music or charts.

What we changed, and why

Every bypass is small, reversible and written down. Nothing here edits the retail tree.

-NoneNetwork
1

-Packing
1

-UsedDebugKey
0

-ActiveVisibleUIKey
0

-Location
SG

-DumpServerIP
[address withheld]

-RoomType
2

python3 tools/site-build.py    # reads artifacts/ + client/ -> website/data/facts.json
python3 tools/render-site.py   # facts.json + frames.json -> index.html

What happens next

1. Pin the crash. Reproduce it under a debugger and get a backtrace, so the two near-null dereferences become a named function instead of an address.
2. Get a socket on the wire. Stand up a loopback listener, point the client at it, and capture the first bytes it sends to the login port — the real protocol evidence this project does not have yet.
3. Answer login and the channel list. Enough of a shim for the client to reach the lobby, then the song select, then a single chart.
4. One song, offline. The finish line: boot, log in, pick one track, hear it play and see a score at the end.

Nothing on this page claims to be further along than that.