News

Continuing on from the upgrades introduced in R2, the engineering team have been redesigning major parts of Bright Engine’s rendering system. Plenty of redundant code has been removed, and significant chunks of the CPU-sided code have been rewritten to be both more memory efficient and reduce GPU idling.

It’s been two months of an architectural overhaul for the Bright Engine render pipeline. The engineering team have been making substantial changes to how the engine draws the scene, resulting in significant performance boosts without loss of graphical fidelity. Let’s dive under the hood to see what’s changed.

After months of programming, the time has come again to show off what our engineering team has been up to. A lot of under-the-hood architecture has been rewritten, drastically reducing memory usage and improving frame rate. Meanwhile, a brand new UI system and editor have emerged. This is more of a technical update than a visual, so pretty pictures will make a return next time.

Over the past few months, our engineers have been coding away, and now it’s time to show off what they’ve been up to. This update is the first of several to bring Open-World support to Bright Engine, starting with various performance improvements, as well as the long-awaited Asset Brush Toolkit. Beyond this, shadows have also received some much-needed attention, and another round of bugs has been squished.

It’s been a long time since the last update, but rest assured, we’ve been working hard. This update aimed to make substantial improvements to the engine’s existing systems, namely landscapes. The entire terrain system and dynamic foliage have been completely rewritten to allow for far greater flexibility and quality with the introduction of tessellation!