[MVRC] Mantium Virtual Racecar Challenge 2026 (Grand Prix Cars)

[LVDH]

Ok,
so just adding Barcelona to the new MVRC Timing app took longer than expected, but now it is here:

https://mvrc-2026-lts.streamlit.app/

This is what we will be using for this season. In the next few days, I will make some modifications to the code though, so lap times will change. Most likely, I will activate the energy management of qualifying. What do you guys think about this?

Very soon, I will finally release a new MFlow.

And here is the calendar for 2026:

• 30.08.2026: Prologue - Barcelona

• 18.10.2026: GP Japan - Suzuka

• 29.11.2026: GP Monaco - Monte Carlo

• 10.01.2027: GP Italy - Monza

What do you think on how we should reward good performance in the prologue? I am thinking about 3-2-1 points for the fastest three.

[CAEdevice]

3-2-1 would be ok for me

[erdosg]

Ok,
so just adding Barcelona to the new MVRC Timing app took longer than expected, but now it is here:
https://mvrc-2026-lts.streamlit.app/
This is what we will be using for this season. In the next few days, I will make some modifications to the code though, so lap times will change. Most likely, I will activate the energy management of qualifying. What do you guys think about this?

Wow, this looks super cool, really next level!
My first observations (obviously before the tuning)
-Currently the new driver seem to like a bit more front aero balance, that is for sure OK, every driver has a different taste, maybe the new guy is nordic.
-But he's a bit too quick, too! Maybe a "mu_weather" at 0.80 or so could be a cheap way to tune laptimes to realistic level in Barcelona, current designs beat F1 by good 6-7 s or so.
Or are there more drastic steps to be expected in the calculation method before we start to adjust the designs?

What do you think on how we should reward good performance in the prologue? I am thinking about 3-2-1 points for the fastest three.

I am not sure, how much this 3-2-1 points would change the championship results - I would either suggest no points (really a public test to check all systems are OK) or sprint race scoring (8-7-6-5-4-3-2-1) so that more teams receive meaningful points that may influence championship results. How about others?

[Ft5fTL]

Ok,
so just adding Barcelona to the new MVRC Timing app took longer than expected, but now it is here:

https://mvrc-2026-lts.streamlit.app/

This is what we will be using for this season. In the next few days, I will make some modifications to the code though, so lap times will change. Most likely, I will activate the energy management of qualifying. What do you guys think about this?

Very soon, I will finally release a new MFlow.

And here is the calendar for 2026:

• 30.08.2026: Prologue - Barcelona

• 18.10.2026: GP Japan - Suzuka

• 29.11.2026: GP Monaco - Monte Carlo

• 10.01.2027: GP Italy - Monza

What do you think on how we should reward good performance in the prologue? I am thinking about 3-2-1 points for the fastest three.

Timing app looks fantastic very nice job.

3-2-1 is sounds ok to me too.

[LVDH]

Hi guys, I was traveling and asked someone to post about the new MFlow version, which did not seem to have happened....
So, there is a new one, I hope it now works for everyone.

[CAEdevice]

Hi guys, I was traveling and asked someone to post about the new MFlow version, which did not seem to have happened....
So, there is a new one, I hope it now works for everyone.

Sorry, my fault. I had a few unexpected issues.
While we’re at it, which version of OF will be used for MVRC 2026?

[erdosg]

Hi guys, I was traveling and asked someone to post about the new MFlow version, which did not seem to have happened....
So, there is a new one, I hope it now works for everyone.

For me, it works fine - issue with previous version now gone FYI tried with same input folder of latest design, for me result was almost identical

Sorry, my fault. I had a few unexpected issues.
While we’re at it, which version of OF will be used for MVRC 2026?

I think earlier read on this thread that v2512 will be used

[AlexTitaneGP]

Hi everyone,

thank you for the new MFlow and the new timing app ! nice work, will it be the one used to "race" next week ?

regarding the new MFlow, I'm probably doing something wrong, but when I try though wsl to run the Mflow app (after downloading / unzipping etc.... and typing ./Mflow in the Mantium directory, I get the following error :


No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)
Falling back to using screens root_visual.
2026-08-20 23:52:44.553 ( 1.559s) [ E5C22080]vtkXOpenGLRenderWindow.:651 ERR| vtkXOpenGLRenderWindow (0x15b47d20): Cannot create GLX context. Aborting.
Aborted (core dumped)

I must say I do not fully understand what's happenning, every other version (2506 2509 2605) are launching the Mflow app fine

many thanks in advance for your help

regards

Alex

[CAEdevice]

Hi everyone,

thank you for the new MFlow and the new timing app ! nice work, will it be the one used to "race" next week ?

regarding the new MFlow, I'm probably doing something wrong, but when I try though wsl to run the Mflow app (after downloading / unzipping etc.... and typing ./Mflow in the Mantium directory, I get the following error :


No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)
Falling back to using screens root_visual.
2026-08-20 23:52:44.553 ( 1.559s) [ E5C22080]vtkXOpenGLRenderWindow.:651 ERR| vtkXOpenGLRenderWindow (0x15b47d20): Cannot create GLX context. Aborting.
Aborted (core dumped)

I must say I do not fully understand what's happenning, every other version (2506 2509 2605) are launching the Mflow app fine

many thanks in advance for your help

regards

Alex

At the moment, I’ve found this solution (Linux version of MFlow): I use version 2608 for the calculations, but I run the post-processing with last year’s version, 2506.

[AlexTitaneGP]

Hi Matteo,

thank you for your answer, unfortunately, I'm having this message when launching the MFlow app to create / build the case, so I do not have a runned case to post process...

Alex

[LVDH]

I have sent out the invitation email for the prologue event. I hope everyone who is signed up receives it, if not, please let me know.
To sort out the technical issues, I have to go into my office next Tuesday, so we have to wait for that...