Stages come with 2D ‘cameras’ for projecting the drawings that you make in them onto the screen. A ‘2D’ camera has a translation, a rotation and a scale, and you can set these directly on any layer. While
FLines can contain 3d instructions, the third dimension is ignored (specifically: objects that are ‘further away’ in z do not get smaller).
What if you want to do 3D graphics? You can ask a layer to go into a 3D ‘mode’ that adds, on top of any 2D control that you might be exerting over a layer, a full 3D, perspective-correct camera:
Turning on 3D mode might yield little to no observable change in what you seen on the
Stage. But, now you can move the
layer.camera around. A 3D camera has three things: a position in space, a target that it is looking at, and a direction that’s up. We can modify these things with different calls to
… and so on. Autocomplete on
layer.camera is your friend.
Obviously these calls can be placed inside an animation loop. For example:
If you have been working through the tutorials on this site diligently you’ll have seen code such as:
These are snippets of code that manipulate positions of things (including the positions of inside pieces of
FLines). Most of this site is dedicated to drawing things in 2D, so all of these operations operate on the ‘x’ and ‘y’ dimensions. But for VR it makes sense to manipulate things in 3D. Thus:
The crucial point here is to get full 3d rotations scales and transformations you should use
Recent versions of Field install a keyboard controlled camera. This camera works if you have selected the stage (that is, it’s surrounded by both the black (selected) and blue (keyboard focus) outlines:
Here are the controls (note, on a mac laptop you’ll have to use fn-arrow up and fn-arrow down for page up and page down respectively).
Keys with shift pressed don’t move the target of the camera:
Keys without shift pressed do move the target of the camera:
Finally a four special things:
Once you have found the perfect angle on something (perhaps by using the keyboard controls above) you might want to save this camera position for later use. One way, of course, to do this would be to do things like:
And then copy and paste the resulting values into code like:
Yawn! A better way is to use the
This call saves the state of the camera to a new variable called
_.camera1. This way you can write:
_.camera1 is saved with the Field document — it’s conceptually part of the box as much as the code (and the shader code, and the box’s name and position etc.). You can have as many of these as you like. If you try to
remember the same name twice, you’ll get an error. If you really want to overwrite, use
overwrite instead. If you want to expose
_.camera1 to other boxes, check out the documentation on properties in general.
Finally, a quick call to interpolate between two camera positions. While this is still technically an area with research to be done in it (that is: figuring out the kinds of interface between creative and aesthetic movements between camera poses and the math) Field provides a simple and often effective interpolator between camera positions. Try:
For a camera position that’s 25% of the way between
_.camera2. Animate that using a loop and
_t() and you are off to the races!.