Studio Settings controls live input, display, sound and tool state; persistence and system-service effects are handled elsewhere. The Japanese Ugoku Memo-Chou Viewer is a separate standard-DS application. Its Wi-Fi setup is valuable comparative evidence but should not be treated as Studio's own Settings implementation. [1][2]
Settings effects
Mapped V2 operations alter a logical key map, display selectors, a four-entry sound override context and player gain. The audio-enable effect sets a particular SDK player gain to either 0 or 127. An advanced-tool reset clears a settings flag, enables both drawing layers, restores saved tool indices and enters the normal pen-selection path. These are specific service effects, not a complete reconstruction of every Settings screen. [1]
Viewer Wi-Fi path
The Viewer enters its own synchronous callback loop for connection setup, using its own resources and access-point choices before returning display control to the Viewer. Use it to understand how the utility works, and label these findings as Viewer-specific. Applying its exact input geometry or result handling to a Studio region without a separate Studio trace would overstate the result. [1]
Test conditions
When a setting seems to persist, check both immediate live state and the saved profile after a restart. When it seems to change sound, inspect the sequence routing context as well as final gain. A visible toggle does not alone establish the service call that followed it. [1][2]
Mapped Settings effects
| Action | Observed effect in the studied V2 builds |
|---|---|
| Change handedness | Updates a flag and the logical key map; the flag resides at a different byte in US than JP/EU. |
| Enable audio | Sets a particular SDK sound player's gain to either 0 or 127. |
| Change display selection | Marks the associated display-state bytes dirty so later presentation work can apply the change. |
| Reset advanced tools | Re-enables both layers, restores three saved tool indices and enters the usual pen-selection path. |
These are service-level effects. They do not by themselves tell us how the Settings page was drawn, when the profile file was written or how the final audio mix sounded on a console. [1]
Why the Viewer is a useful comparison
The separate Viewer starts its Wi-Fi utility by handing it a work area and letting the utility run its own callback loop. The utility handles display, input, sound and temporary resources until it exits and returns control to the Viewer. Its menu distinguishes stored connection profiles, empty slots and setup methods, and it uses different touch timing from Studio's graph widgets. A developer can compare this lifecycle with Studio's client, but should not copy the Viewer's hitboxes or profile offsets into a Studio implementation without a Studio trace. [1]