ritenseki
0ccf6b09f4
Two of this session's bugs had the same shape, and naming that shape is worth more than either fix: the wash lights whipping back and forth, and the billboards spinning. In both cases the data was fine — clip curves and serialized fields dumped clean and checked out — and what was wrong was behaviour we had inferred on behalf of a script that does not exist. So the default hypothesis for "this stage element moves when it shouldn't / doesn't move when it should / moves at the wrong rate" is now written down as: the original component is missing and something of ours is standing in for it. Not: the data was parsed wrong. That is justified by the ledger — 728 MonoBehaviour instances are still empty, AnimationObjectController alone accounting for 282, and every decision about what animates and when lived in those method bodies. Data is dumpable and has repeatedly proven correct; behaviour is the part we cannot retrieve. Two practical corollaries go with it: check what scripts an object carried and whether we have them ([StageScripts] plus the signature list) before suspecting the parser; and when standing in for a missing component, say in the source whose decisions you are making, and mark whether the rule came from bundle data or from watching reference footage. The latter is real evidence but not ground truth, and may not hold on another stage. The counter-example is recorded in the same breath so the rule does not become a reflex: the black light shafts were a data problem after all — every material carries a URP Lit property table whose opaque preset (_DstBlend = Zero) overrode the additive blend 14 of the 16 relevant shaders declare. That one was found by dumping, and the general lesson — a stale saved-property table can override render state, not just colour — now sits next to the existing warning about saved properties. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UzXXkLzVC8pNA3JjyUGMbq
Uma Viewer (2)
Unity application that makes it easy to view assets from Uma Musume: Pretty Derby.
| Version | Supported |
|---|---|
| JP (DMM) | ✅ |
| JP (Steam) | ✅ |
| KR | ✅ |
| Global | ✅ |
⚠️ 🌍 EN/Global users ⚠️
In UmaViewer, set WorkMode to Default and Region to Global in the 'Other' Settings tab.
Currently only the default work mode is supported - you need to download assets using the Download All button in the game's settings for the viewer to work.
Requirements/Installation
- Uma Musume: Pretty Derby with full data download is required to run the viewer.
- Depending on your version and update status, the game stores its data in different locations
- DMM/Steam Older installations : C:\Users\your_username\AppData\LocalLow\Cygames\umamusume(?)\
- DMM/Steam Fresh installations : ...\Umamusume installation directory\Umamusume_Data\Persistent(?)\
- In any case，confirm your file listing in target folder looks like this
- Target Folder\
- meta
- master\
- master.mdb
- dat\
- 2A\...
- 2B\...
- ...\...
- Target Folder\
- Download the most recent UmaViewer.zip file from Releases tab.
- Extract the archive anywhere, can be extracted over previous version.
- Run the UmaViewer.exe.
- UmaViewer will try to automatically detect the game data folder.
- If it fails or shows an error, go to Settings → Other → Change DataPath and manually select target folder.
- For Developers/Contributors
- Unity Hub with Unity Engine Version 2022.3.62f1 is recommended. It should be possible to run it on newer 2022.3.X versions.
- Clone or download and extract this repository.
- Import and Open the project in Unity Hub, missing files should be automatically repaired.
- Open the Assets/Scenes/Version2 scene.
- note: If there are errors in the console, JSON .NET For Unity may be required
Features
| ✓ - Working | / - Incomplete | x - Unsupported |
| Viewing main character models/animations | ✓ |
| Swapping costumes/animations between characters | ✓ |
| Viewing chibi models/animations | ✓ |
| Viewing mob (NPC) models | ✓ |
| Playing facial animations, custom sliders | ✓ |
| Cloth/Hair physics | ✓ |
| Playing Live Audio with Lyrics | ✓ |
| Exporting animations to MMD | ✓ |
| Recording animations (.gif), screenshots | ✓ |
| Viewing Props, Scenery, Live scenes | / |
| Exporting models | / |
All characters and animations are supported
Mobs / background characters as well
Mixing outfits and animations
Screenshot and .gif recording
and more
Also check out:
UmaChat by kagari - model viewer fork that lets you chat with Umas using AI + TTS
Special Thank to:
MarshmallowAndroid: UmaMusumeExplorer for acb/awb decoder.