rFactor 2 March Roadmap - VR, Performance and Cars!

Paul Jeffrey

Premium
rF2 March Development Roadmap 10.jpg

New cars, tracks, improvements and performance to name just a few highlights from the March rFactor 2 Development Roadmap!

Firstly please accept my apologies for the recent lack of new articles / delayed news releases. Sadly I've been somewhat unwell for a little while (nothing in the least bit serious) and it has sapped any sort of strength, energy and commitment right out of my system. Normally RD and sim racing come first, but after a prolonged period of time adhering to this self imposed rule I've simply burnt out, so please forgive me, and rest assured that thanks to the miracle of modern medicine, I'm almost back to full strength! :)

Ok so excuses aside, let's talk about some news...

Studio 397 have once again kept up the tradition of publishing a very late in the month 'Development Roadmap' that shines a light on the progress of PC racing simulation rFactor 2. This month, the Dutch development team have informed the world of the upcoming LMP3 classification prototype, some major Zandvoort track improvements, a little known new track and plenty of improvements to performance and VR, March roadmap time sounds like another positive news release for fans of the rFactor 2 simulation...

So please see below the latest Studio 397 rFactor 2 roadmap below:

And work goes on!… We continue to relentlessly hammer away at the new features and content mentioned in the previous roadmaps. And yes, you’ll be happy to know that this month is no exception: we will still manage to bring you some ‘new’ things to look forward to.

We know how much you all enjoy these road maps, with anticipation of the things to come, and we are just as anxious to share them with you. Keeping you informed of our broad development goals is part of our whole outlook. For us communication is key to making sure we stay on the mark and never get out ahead of our userbase. So as things begin to take shape and features mature, we do our best to show you the progression and previews as soon as we possibly can. Although these are not ‘deadlines’, they should give a you good idea of the things you need to get excited about.

Performance
The graphics optimizations we mentioned in previous roadmaps are still very much ongoing and current. We are investing a considerable amount of resources to get this done. Graphical improvements and optimizations are key to future proofing the rFactor 2 graphics engine. With that in mind, we are taking our time to methodically test each optimization pass to make sure everything stays put and is in working order, and that is why it’s taking a little longer than originally planned. Thanks to our very focused group of dedicated testers who are looking at each area, we are moving forward at a steady pace. We hope to get it out to you ASAP!

VR
And speaking of specifics, VR is one area where we know we need to improve performance, and these optimizations are showing very promising increases in stability and overall framerate.

Triple Screen – Multiview
“Multiview” has to render three separate viewpoints and because of this, it’s inherently more taxing on any system. You’ll be happy to know we have worked on some very specific optimizations that will positively affect multiview performance

Content
After releasing the KartSim pack earlier this week, we wanted to reassure you that we also have new free content coming up:

March 761
We have a solid commitment to historic racing and we hope you find rFactor 2 a good place to experience some of the great cars of the past. With that we are pleased to announce that we will be releasing the March 761 soon for free. Not just that, we have also updated the Brabham BT44 for some excellent head-to-head racing.

rF2 March Development Roadmap 1.jpg
rF2 March Development Roadmap 2.jpg


Botniaring
Finnish fans! We have a new track on the horizon. Introducing the Botniaring, located in Southern Ostrobothnia, Jurva, Finland aka Perkeleville (big grin) The track is perfect for our upcoming Tatuus cars as well as many others.

Zandvoort
We have a number of updates to the Zandvoort track that is currently in beta. While we were building the track, it was being repaved and our 0.20 version showed a version of the track as it was then: about three quarters done, with some old asphalt in the final sector. Since then, repaving has been finished and the Audi S curve was remodeled for the DTM races. On top of that we added a lot of detail, for example in the pit area, and at the same time optimized the track. We’re almost ready to put the track through final testing, so we hope to bring you this new version soon!

rF2 March Development Roadmap 4.jpg
rF2 March Development Roadmap 5.jpg
rF2 March Development Roadmap 6.jpg
rF2 March Development Roadmap 7.jpg


Oreca 07 LMP2
After all these free updates above, we are also proud to announce another car that will be part of a new upcoming pack – say hi to the super successful Oreca 07 LMP2! Used across all major endurance series the Oreca LMP2 almost won outright at Le Mans last year with Jackie Chan Racing DC.

rF2 March Development Roadmap 9.jpg
rF2 March Development Roadmap 10.jpg


UI
Most of our focus on the UI in the last months has been to include all of the current base features and test them to make sure they function properly. On the surface this might seem like an easy task, but it involves a lot of repeated clicking and trying: the UI is a complex matrix of interdependences that we need to carefully unravel to better understand and improve. So before really jumping in to conquer the new features, we needed a solid base.

As this first phase begins to wrap up and we have a stable functioning UI, our focus is shifting to those specific things that really need to be more user friendly, existing features that were either hidden or not readily visible enough to find and use. Two current examples of this are custom teams/skins and driver swaps.

Using custom skins in the current UI, although functional, has always been a bit obtuse and not straight forward for the average user. We saw a couple of ways to improve this going forward. One is to offer a simpler way to get your skin in game, and avoid the need to alt-tab or even exit rFactor 2, just to see your skin on the car. We’re still playing with a few ways to make this less fiddly. Next, custom ‘team’ creation needs to be more direct and easier to achieve. This involves thinking like a new user and making smart dialogs and using correct terminology, that way there’s no doubts about how naming or hierarchy.

Driver swaps are another area that works in the current UI, but is complicated to use in practice: having to close rF2 and navigate through somewhat hidden menus is not ideal and prone to user error, and having to assign keys to perform simple actions is a bit overkill. So the new way to do a driver swap is simple. When you join a server, we will ask you if you want to drive a car or join as as a spectator. When you choose the latter and click drive, you’ll get a pop up list of names to choose from, click select and you’re ready to drive once your team mate pits – simple as that!


rF2 March Development Roadmap 11.jpg


Competition
The competition structure continues to take shape, and just like the UI we are focusing on the ground work. This means dealing with and squishing any bugs related to the day to day functioning of the competition structure itself. Competitions, as you may know, can span many weeks with multiple events and sessions. It’s therefore important that each code change is throughly tested for reliability and stability. By basing this on the cloud technology of our parent company Luminis we ensure the system will be very scalable, and it is certainly our intention to end up with an open system that can also be used by the many existing leagues out there.

We hope to show you more real soon!

Community
When we did the paint competition a few months ago, we were overwhelmed by the large amount of high quality entries. Encouraged by this, we concluded we wanted to do more of these competitions to showcase the many talented painters in our community. That said, assembling all these skins into packs proved to be a lot of work, so after discussing various options we decided to build some automation to more easily generate new cars, their skins, and all data and preview images associated with them. That is the reason the GT3 skins took us longer, but we’re confident we can release them next week.


rFactor 2 is available exclusively for PC from Steam now.

Check out the rFactor 2 sub forum here at RaceDepartment for all the latest news and discussion with regards to the simulation. You can take part in lively debates with fellow rFactor 2 fans and take part in some great Club and League racing events..! Head over to the forum now and share the love this simulation so very much deserves...

Like what you see here at RaceDepartment? Don't forget to like, subscribe and follow us on social media!

RaceDepartment YouTube
RaceDepartment Twitter
RaceDepartment Facebook
RaceDepartment Twitch
RaceDepartment Instagram

Happy with the contents from the March development roadmap? What are you looking forward to the most? Let us know in the comments section below!
 
Last edited:
So why has it looked perfect untill the falls creator update is applied?

Did you check in add/remove your Nvidia driver was not "updated" actually downgraded .... mine were even though "don't download drivers" was ticked
Clever Microsoft :rolleyes:

You won't know unless you have used a gmotor2 sim that use config.exe ( GTL/GTR2/rF/AMS etc)
Also you will lose any Nvidia Inspector profiles you activated

Delete all nvidia entries reboot and setup your normal driver ticking box "clean install" whatever

It can also replace DirectX and VBasic depending on what/versions you have installed

Is well recognized bug for rF2
https://forum.studio-397.com/index....0-removes-runtimes-after-major-updates.58239/

P.S. I extract nvidia drivers before setup and delete all folders bar Drivers, NV12 and physx
Run custom install, then you don't get more folders on C:\ for nvidia stuff you never ticked
 
Last edited:
Did you check in add/remove your Nvidia driver was not "updated" actually downgraded .... mine were even though "don't download drivers" was ticked
Clever Microsoft :rolleyes:

You won't know unless you have used a gmotor2 sim that use config.exe ( GTL/GTR2/rF/AMS etc)
Also you will lose any Nvidia Inspector profiles you activated

Delete all nvidia entries reboot and setup your normal driver ticking box "clean install" whatever

It can also replace DirectX and VBasic depending on what/versions you have installed

Is well recognized bug for rF2
https://forum.studio-397.com/index....0-removes-runtimes-after-major-updates.58239/

P.S. I extract nvidia drivers before setup and delete all folders bar Drivers, NV12 and physx
Run custom install, then you don't get more folders on C:\ for nvidia stuff you never ticked

I actually reinstalled a new clean windows 10 latest edition, the final thing i did was the Nvidia driver install, so that's as clean as can be:) I can get it to all look half reasonable but was definitely better prior to creator coming along:)
For me even raceroom shadows look like crap now! I don't get it.
If someone who thinks their AA is working well can recommend the version of a nvidia driver they are using with the creators update then i will give that a go.
 
I wonder if Reiza and Studio 397 are annoyed with Nvidia and/or Microsoft? It's not easy being a software developer.

Of all the tweaks to solve the AA problem, the best I've found (from the Reiza forum) is to disable full screen optimizations in the compatibility tab for ams.exe. Maybe the same will work for rFactor2.
 
Since I found the sweet spot of graphics configuration for my triple-screen setup, I keep playing rF2 more and more. I still get some FPS drops with some combination of car and track but it's still quite playable. I'm a happy customer :)
 
I wonder if Reiza and Studio 397 are annoyed with Nvidia and/or Microsoft? It's not easy being a software developer.

Of all the tweaks to solve the AA problem, the best I've found (from the Reiza forum) is to disable full screen optimizations in the compatibility tab for ams.exe. Maybe the same will work for rFactor2.

There is no AA problem with rF2, at least not with DX11. rF2 DX11 uses new types of AA methods, Reiza and other rF1 based games methods from ten years ago, which is probably why the issues arouse with W10 update. LOD clamp is also no longer necessary unless tracks are built using bad LOD bias values (a problem of old rF1 tracks mainly).
 
Back
Top