Over the course of this month we have released a few hotfixes for our fresh 1110 build whilst our team has been working on many of the features we’ve been talking about in the last few roadmaps. We also went to Zandvoort during the Jumbo Racing Days to showcase some of our content to the huge crowds that came to see several racing series and of course appearances from Max Verstappen, Daniel Ricciardo and David Coulthard.
This month we released the much anticipated performance upgrades. Judging from the feedback we got, build 1110 has provided most, if not all people a significant improvement. On top of those improvements, we also added several new features, one of which was a refinement of our tyre model, which Michael explained extensively in his blog. In the last couple of weeks we’ve been monitoring our forums and other channels to resolve any remaining issues. As promised, we also intend to address some remaining issues with our rainy conditions. In VR the performance is still relatively low, and viewed from external TV cameras the raindrops, when zoomed in, look too big. Both issues are still on our list for a future update.
It’s live! In the last couple of roadmap updates, we’ve made it no secret that we have been working hard on a set of performance upgrades. We’ve taken our time to get it right and took advantage of the DirectX 11 API as much as possible. Our focus was on performance, while keeping the actual look of the game the same. All of this centers around a concept called “frame time”, which is the time it takes to completely render a single frame to your screen(s). Obviously we want that time to be as low as possible, but we also want it to be as constant as possible as only the combination of both leads to a smooth display. In general there are three things that influence this: your video card (GPU), the processor you have (CPU) and the bus between them and their memory. Optimizing performance means looking at all three, and we’ll go into more detail on how we did that below.