The RED engine now enables the user to dynamically update a cube map.  This can replace ray traced reflections at a lower cost for all real-time applications.

Looking for better performances, both for rasterization & ray tracing is what our customers expect from a middleware supplier like Redway3d.  In Redsdk 1.4, numerous functionalities have been optimized, like the memory footprint of ray traced shadows and rendering materials.  In the same way, the scalability of the RED engine has also been increased.  Redsdk users will notice a 5% to 30% speed increase on large model assemblies (100K+ objects).

Redsdk now offers a built-in memory leak tracker and analysis tool.  New RED engine classes have been created to get a complete map of all memory resources created & used by the RED engine, sorted by category (Ray Tracer, Images [2D, 3D, cube, composites, read back], shapes [ with & without transforms], Materials, Shaders, Cluster, Strings ...). Redsdk users can now better debug their application, by finding the graphics resources which have been managed incorrectly.

Redsdk now offers its own standalone test suite, which can be used by any RED engine user to test & certify hardware platforms.  The RED engine test suite not only validate the RED engine functionalities but also their execution time.  The RED engine test suite generates a HTML report which provides a summary of the tests, resulting of a per pixel comparison between the grabbed images during execution time and pictures of reference.

http://www.redway3d.com/