There used to be a problem with saving layouts where if you had your Windows display settings "Scale" set to anything but 100% the Players would all open in the wrong sizes. While this bug is fixed for the save layout function, it is not fixed for when a player is created with the mutation PlayerCreate in the API.
For reference here is what the 'swap feeds button' mentioned does with the mutation PlayerCreate:
The important bit is that it gives the new player the bounds information of the old player but then the player ends up a different size when the Windows scale option in display settings is not set to 100%. See image:
Here is how it was figured out that it is similar to (or the same as) the saving layouts bug:
In short, it works correctly again when the Windows setting is turned to 100%.
There used to be a problem with saving layouts where if you had your Windows display settings "Scale" set to anything but 100% the Players would all open in the wrong sizes. While this bug is fixed for the save layout function, it is not fixed for when a player is created with the mutation PlayerCreate in the API.
Here is what happens:
For reference here is what the 'swap feeds button' mentioned does with the mutation PlayerCreate:
Here is how it was figured out that it is similar to (or the same as) the saving layouts bug:
Why it's still annoying: