No normal mapping in this demo.
The engine directly loads 3D World Studio files.
I am doing this right from the ground up. The command set is really powerful, with a lot of real-time intersection stuff and smart updating of objects.
For example, the PointVisible() command accepts an optional parameter that indicates whether the routine should test the line-of-sight with brushes, meshes, and/or terrain. It will first test brushes, since they are more likely to cause a hit. Meshes are tested against only if their bounding box intersects the line-of-sight.
Dynamic lights can be created and deleted on-the-fly, with optional styles like strobe, flicker, pulse, etc. If the light stays still and the objects that get lit stay still, the shadow volumes only need to be calculated once. Of course, if either the light or object moves, the shadow volumes are recalculated automatically.
The engine directly loads 3D World Studio files.
I am doing this right from the ground up. The command set is really powerful, with a lot of real-time intersection stuff and smart updating of objects.
For example, the PointVisible() command accepts an optional parameter that indicates whether the routine should test the line-of-sight with brushes, meshes, and/or terrain. It will first test brushes, since they are more likely to cause a hit. Meshes are tested against only if their bounding box intersects the line-of-sight.
Dynamic lights can be created and deleted on-the-fly, with optional styles like strobe, flicker, pulse, etc. If the light stays still and the objects that get lit stay still, the shadow volumes only need to be calculated once. Of course, if either the light or object moves, the shadow volumes are recalculated automatically.