Repository navigation
set-game-view-size reports success under the Device Simulator without changing anything, and its persistent side effect is undocumented #3410
Description
Environment
- Windows 11, Unity 6000.6.4f1
- uloop package 3.21.1, dispatcher 3.13.1, project runner 3.12.2
Problem 1: success reported when nothing changed
When the Play Mode view is the Device Simulator, uloop set-game-view-size --width 1280 --height 720 does not change the resolution but returns:
"PreviousWidth": 2360, "PreviousHeight": 1640,
"CurrentWidth": 2360, "CurrentHeight": 1640,
"Changed": false,
"Message": "Game View rendering resolution changed from 2360x1640 to 2360x1640.",
"Success": true
An agent reading Success: true and a "changed" message assumes the size was applied.
Expected: when the Device Simulator is the Play Mode view, return Success: false (or a clear warning) saying the Game View size does not apply there, and suggest game-view-mode --to GameView or picking a device instead.
Problem 2: the persistent side effect is not documented
In the Game View, the command adds a custom size named uloop <w>x<h> and selects it. Later calls reuse that single entry rather than adding more. The entry is saved to the user-wide GameViewSizes.asset (%APPDATA%\Unity\Editor-5.x\Preferences\ on Windows), so it outlives the session and shows up in every project. The previous selection is not restored.
This seems to come from PlayModeWindow.SetCustomRenderingResolution. The problem is that nothing tells the agent the state is left behind. Removing it requires reflection on internal types (GameViewSizes, GameView.selectedSizeIndex).
Expected: the agent can tell that this state is left behind and how to undo it.
Activity
[-]set-game-view-size reports success under the Device Simulator without changing anything, and its persistent side effect is undocumented[/-][+]`set-game-view-size` reports success under the Device Simulator without changing anything, and its persistent side effect is undocumented[/+]hatayama commentedon Oct 29, 2026
Thank you for the clear report and the exact reproduction. Both points are fixed in #3412 and released today in Unity package 3.21.2:
uloop set-game-view-size --width/--heightnow fails withSuccess: falseand changes nothing, instead of letting Unity log "does not support custom resolution". Runuloop game-view-mode --to GameViewfirst, or pick a device withuloop game-view-mode --device <name>to change the simulated screen size.--resetflag removes theuloop (WxH)entry this tool adds from every platform group of the user-wideGameViewSizes.asset, saves the list, and restores the size that was selected before. Only the entry named exactlyuloopis touched; a user entry such asuloop-phoneis left alone. Setting a second size updates that same entry instead of adding another one.Updating the package is enough for this one; no CLI update is needed.