For viewports 1920-width-and-up, rendering 3d scenes in the browser always seems to be sluggish, even with optimizations. Hardware (CPU, GPU) and browser (WebGL support) are all factors. In any case, there's a noticeable improvement in perceived 3d animation "smoothness" when the <canvas> area becomes smaller than x (e.g. 1024px), regardless of the viewport.
Proposal: For large-viewports, perhaps the dice rolling area should be constrained such that the <canvas> never exceeds a limit of width. In doing this, we'd have to present a stylized visual "box" to the user so they understand dice rolling occurs only within. Secondly, it would be nice to have a way to toggle the containment between full-page and the box-container. Perhaps a subtle icon in the top-right of the box?
For viewports 1920-width-and-up, rendering 3d scenes in the browser always seems to be sluggish, even with optimizations. Hardware (CPU, GPU) and browser (WebGL support) are all factors. In any case, there's a noticeable improvement in perceived 3d animation "smoothness" when the
<canvas>area becomes smaller than x (e.g. 1024px), regardless of the viewport.Proposal: For large-viewports, perhaps the dice rolling area should be constrained such that the
<canvas>never exceeds a limit of width. In doing this, we'd have to present a stylized visual "box" to the user so they understand dice rolling occurs only within. Secondly, it would be nice to have a way to toggle the containment between full-page and the box-container. Perhaps a subtle icon in the top-right of the box?