The four studied Studio builds are related but not interchangeable. Japanese V1 predates the V2 releases and has different implementation details in its PPM serialiser and application paths. Japanese, American and European V2 builds also differ in addresses, offsets and resource breadth. [1]
What to record in a finding
Always identify build, processor module, virtual address or file offset, and validation scope. A matching output across two builds is useful evidence but does not establish every surrounding branch. The separate Japanese Viewer is a reference for comparison, not a substitute for a Studio region. [1][2]
Regional analysis remains incomplete. The research guide points to open comparative work rather than claiming a single universal binary map. [1]
Japanese V1 versus V2
Japanese V1 is an earlier implementation, not just a translated V2. It has a different online send-state path, a shorter PPM serialiser and no mapped V2 mode-9 branch in that serialiser. It writes the recorded audio lengths directly, while V2 rounds them to even numbers. It also stores some messages and resources differently. [1][2]
Three V2 builds
Japanese, American and European V2 share much of their behaviour, but executable addresses, field offsets, languages and NitroFS contents differ. The studied NitroFS counts are 26, 37 and 56 respectively. A function-address shift observed in one browser family is not a universal whole-program relocation rule. [1][2]
Path and identity traps
Directory names, title codes and filename comparisons can differ by build. A file that validates on one region does not thereby prove another region will accept its path. When documenting an FSID, filename or local list, state whether a field layout came from a public format description or an original function in a particular build. [1]
Comparative method
Compare the same action and fixture in each release. Record distinct call chains and state offsets even if the screen looks identical. The separate Japanese Viewer is a useful reference for embedded resources and network setup, but it is not a fifth regional Studio build. [1][2]