twisol / comp465_project Goto Github PK

The user should be able to select between five different views of the Ruber system. Two of these will be fixed relative to the Ruber barycentric basis, while the others will be fixed relative to the Warbird, Unum, and Duo.

The user should be able to cycle through these views by pressing v.

We need a model to represent missile objects, whether fired by the Warbird or by a missile defense site. This model must contain both geometry and color information.

The model must fit within a 25-unit bounding sphere.

Barnes already wrote one of these here - we just have to integrate it into our codebase.

On every time step, we need to update the position of the orbiting bodies in the Ruber system. The Warbirds are (apparently) exempt from this, as they are somehow able to maintain a fixed position with respect to a static orthonormal basis centered on the Ruber solar body. (This would break all of physics in the real world.)

Depends on #7.

Information about the simulation should be shown in the window title. Such information includes:

• Ammo counts for any entity capable of firing missiles
• Simulation updates per second
• Frames drawn per second
• Current camera view

Example title:

Warbird  7   Unum 5   Secundus 0  U/S 25  F/S  321  View Duo

The Ruber system should be modeled as a set of objects, each associated with an object which it is positioned relative to and an orbital velocity.

This is the "static" picture of the simulation, corresponding to the representation of simulated objects and their properties. The "dynamic" picture, covered by #3, concerns how the properties of the simulated objects change over time.

We need a model to represent the Warbird in our simulation of the Ruber system. Both geometry and color data will be used for this model - the color will not be set programmatically.

The Warbird can look like pretty much anything, as long as it's clearly a flying thing of some sort. It could be a TIE fighter, Samus' gunship, an origami plane - anything.

The model must fit within a 100-unit-radius bounding sphere.

To display the Ruber system properly, we need to create a model for each of the orbital bodies in the Ruber system. The geometry for each model can be the same - a simple sphere shape suffices - but the colors should differ.

Every triangle in a model can have its own color, so you can draw continents and seas onto either or both of the planets, if you so desire.

• Ruber (star, 2000 units radius)
• Unum (planet, 200 units radius)
• Duo (planet, 400 units radius)
• Primus (moon, 100 units radius)
• Secundus (moon, 150 units radius)

We need to provide some documentation on the architecture of our code, as well as information on which features we've implemented.

Additional things to note include:

• Extra camera (ship camera) for better viewing of the ship and missile models
• Added time rates
  • Extra time rate (50x)

Please edit this message to add further items as needed.

A rendering traversal should be designed which can pass each object in the Ruber system to the renderer after resolving its chain of reference objects (e.g. Secundus -> Duo -> Ruber -> System barycenter).