Put 3D boards in ViewportFrames

[ecurtiss]

Currently, the 3D boards are rendered as parts in workspace. Instead, I think we should parent each 3D board to its own ViewportFrame and have the ViewportFrame viewable as a SurfaceGui on a part.

Benefits

• Moveable boards: The surface part can be moved while the board can remain stationary in the ViewportFrame.
• FPS won't drop when viewed side-on: See Part-based boards render slow when viewed side-on #14
• Slideshow boards: In order to have slideshows that can be written on, we can put multiple boards in a ViewportFrame and move the camera to change slides.

Drawbacks

• The resolution of ViewportFrames decreases as your camera gets nearer to them. I will update this post with image when I have time.

[blinkybool]

This will happen when Ethan hosts #code on a sail boat.

[ecurtiss]

Distant metaboards are lag bombs that contribute to having a constant 2-3 million tris on-screen in TRS. Viewport boards have free LOD.