Game3 is our first 3D game, and a warm-up on using
Scene to load and manage 3D objects.
Your goal is to start with a fork of the game3 base code and develop a new game which uses a Scene with animated transformations.
Animation of transformations may be automatic or under player control. They may be of a hierarchy (e.g. a robot arm) or simply of the scene's camera. Remember, however, that your game will still need a goal; a snow globe is not a game. Note, also, that there is no pre-supplied physics or collision detection code!
Remember that our Resources section has links to places to get various 3D assets. If you include assets that you did not create, be sure that this use is compatible with the license of the assets, and record where you got them in your README.md.
Answer roll call with a no-more-than-two-sentence summary of what you are making. A good structure for this game is to provide a point of reference and highlight the main difference in your game. (E.g. "I'm making a hidden picture game in 3D.")
Place a check-out of your game repository into your game3 folder on AFS (see below).
We have design roll call to make sure you are thinking about what you are going to code up. Your roll-call design is non-binding -- the game you turn in does not need to match it. Remember that one way to get out of the box is to go below the bottom of the barrel.
For this assignment you should first get the base code working on your system, and then modify it to implement your new game. More detailed steps:
README.mdto document your project; replace
screenshot.pngwith a screenshot of your game.