Set the shape before setting a record
Pick a window large enough to distinguish the companion from nearby branches and to read the controls comfortably. An upright window is a useful starting point when moving from phone play to desktop. You can then adjust size without simultaneously learning a much wider course view.
The game measures the actual stage, including the window that holds it when using Float. A browser sidebar or a very short window can change that available area even when the monitor itself has not changed.
Understand the visible difference
ORBIT uses a logical field height and calculates field width from the visible aspect ratio. Making a window wider can expose more upcoming gates. Enlarging both dimensions in proportion mainly changes display size; changing the proportions changes the view of the course.
For practice notes, record a simple description such as upright phone, narrow desktop or wide desktop. There is no built-in cross-device normalization of these viewing conditions. Similar shapes make your own timing comparisons easier to interpret.
Handle an awkward resize
Resizing is not an instruction to end or restart the run. If you drag a window edge during play, be prepared for the forest to keep moving. Make substantial layout changes between attempts, when you can inspect the result without also managing a branch crossing.
If the forest becomes clipped or blank after resizing, note the original and new shapes. Restore a normal window size and check again before reloading. If the problem persists, report whether you were in a regular tab, an installed app or Float; that distinction helps identify which stage was being measured.