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

[janci_kp]

I would say that any winglets, or anything like you had last year. We can keep the winglets in chassis area because managing the separations around radiator inlet can be somewhat tricky. But for engine cover - sidepods I’d implement some kind of tangency and continuity rule.

[Qvist designs]

I have published a race schedule for 2026, rules and CAD files.
As I was so swamped in work, there is nothing very spectacular, for the first races, we will pretty much continue like we did last year.
I am working on a new version for MFlow, which should be a bit faster, more reliable post-processing and you should be able to use it on cloudHPC. I am looking forward to get this released in the next days.
There are also to small things to sort out before I can send out an invitation email. I hope that will be a matter of some two or three days.

You guys also requested a change in how we count championship points. I am open to this, so bang out some suggestions.

HI, i have some suggestions regarding the new regulation boxes based on the official fia boxes that would not include any removal of aria except the old mirror stay.

You can see the changes in the imaged linked bellow.
https://imgur.com/a/MwfKYjz

The suggestions include:
- New mirror rear stay instead of the one that go all the way to the floor
- Extended floor corner forward
- Add the forward cube under chassis that some real teams use and could open up for more possibilities (maybe make less wide)
- Wider tail box for potential freedom of tail airo
- New bigger shark fin that is used in the final 2026 regulations for more accuracy (minimum surface could stay same)
- A obligated T-cam everyone use for more accurate look to a f1 car and it can have a reference surface on the under face of the camera that need to be obscured by any bodywork (except t-cam bodywork) so it dont float

[LVDH]

Hi guys,

sorry for the very slow communication here. It seems the entire MVRC staff has very little spare time since a while. At least there is a new version of the CAD files and a new MFlow.
I tried to optimize the run times and memory usage, but it seems like we were already doing rather well. When using OF v2512 there is a new setting though. It is called early stop and is deactivated by default for now. You can turn it on, it will end the simulation when certain convergence criteria is met.
I hope this is no too big surprise (I think I mentioned it last year in the old thread) but for 2026, we will use OpenFOAM v2512! I hope this is OK for our Windows users. I think last year someone was able to write a short guide on how to run OF v2412 on Windows. So I hope, if there are questions, we can get the Windows people through this.

Also I like the ideas. I was never too sure about the cameras. I think on top of our cars it would not look very cool, but the ones ahead of the front suspension would be a factor for realism. So if someone can provide STEP files, I am open to add them to the mandatory parts.

[AlexTitaneGP]

Hi guys,

sorry for the very slow communication here. It seems the entire MVRC staff has very little spare time since a while. At least there is a new version of the CAD files and a new MFlow.
I tried to optimize the run times and memory usage, but it seems like we were already doing rather well. When using OF v2512 there is a new setting though. It is called early stop and is deactivated by default for now. You can turn it on, it will end the simulation when certain convergence criteria is met.
I hope this is no too big surprise (I think I mentioned it last year in the old thread) but for 2026, we will use OpenFOAM v2512! I hope this is OK for our Windows users. I think last year someone was able to write a short guide on how to run OF v2412 on Windows. So I hope, if there are questions, we can get the Windows people through this.

Also I like the ideas. I was never too sure about the cameras. I think on top of our cars it would not look very cool, but the ones ahead of the front suspension would be a factor for realism. So if someone can provide STEP files, I am open to add them to the mandatory parts.

Hi everyone,

thank you for the update, could you describe rougly what are the CAD updates from the last CAD uploaded (V5.0 if I remember) ?

many thanks in advance

best regards

Alex

[erdosg]

Hi guys,

sorry for the very slow communication here. It seems the entire MVRC staff has very little spare time since a while. At least there is a new version of the CAD files and a new MFlow.
I tried to optimize the run times and memory usage, but it seems like we were already doing rather well. When using OF v2512 there is a new setting though. It is called early stop and is deactivated by default for now. You can turn it on, it will end the simulation when certain convergence criteria is met.
I hope this is no too big surprise (I think I mentioned it last year in the old thread) but for 2026, we will use OpenFOAM v2512! I hope this is OK for our Windows users. I think last year someone was able to write a short guide on how to run OF v2412 on Windows. So I hope, if there are questions, we can get the Windows people through this.

Also I like the ideas. I was never too sure about the cameras. I think on top of our cars it would not look very cool, but the ones ahead of the front suspension would be a factor for realism. So if someone can provide STEP files, I am open to add them to the mandatory parts.

Hi everyone,

thank you for the update, could you describe rougly what are the CAD updates from the last CAD uploaded (V5.0 if I remember) ?

many thanks in advance

best regards

Alex

Hi all, I have found following:
-RV_Tail_V02 --> added design volume (broader on the sides of the volume)
-RV_Sidepods_EngCover_V02 --> added design volume (fin can be extended in +Z in almost entire length)
-MAND_Wheel_* wheels corrected, now all 4 is at correct position (but no geo change other than that)
Can anyone confirm, or did I miss something important?

[erdosg]

Hi guys,

sorry for the very slow communication here. It seems the entire MVRC staff has very little spare time since a while. At least there is a new version of the CAD files and a new MFlow.
I tried to optimize the run times and memory usage, but it seems like we were already doing rather well. When using OF v2512 there is a new setting though. It is called early stop and is deactivated by default for now. You can turn it on, it will end the simulation when certain convergence criteria is met.
I hope this is no too big surprise (I think I mentioned it last year in the old thread) but for 2026, we will use OpenFOAM v2512! I hope this is OK for our Windows users. I think last year someone was able to write a short guide on how to run OF v2412 on Windows. So I hope, if there are questions, we can get the Windows people through this.

Also I like the ideas. I was never too sure about the cameras. I think on top of our cars it would not look very cool, but the ones ahead of the front suspension would be a factor for realism. So if someone can provide STEP files, I am open to add them to the mandatory parts.

Hi,
for windows users, the guide is on page 13 of last year's forum - for me v2512 works just fine on WSL with same method, and early termination seems a cool option to have!
Though, I have some issue using the newer MFlow releases (with WSL based OF). Specifically the porous media is not working. Everything works fine with deck generated in an older release (v2504a_win is the only I have), but it does not work with decks generated with new ones (v2605_win, v2509_win) from exact same input_files folder. I have tried to narrow down the differences (applying the changes one-by-one) -- I believe somehow the fUpdate with fvOptions and fvOptions_off is not working quite right, and when it is added, the porosity region is not generated.
In the solver log, the model generated by the old release has an additional message:

Code: Select all

Selecting finite volume options type explicitPorositySource
    Source: porosity_HX_2
 [...]
Porosity region porosity_HX_2:
    selecting model: DarcyForchheimer
    creating porous zone: HX_2
[..]

not present in the log with the deck generated with newer release. The latter deck has a warning at each time step:

Code: Select all

--> FOAM Warning : 
    From virtual void Foam::functionObjects::forces::calcForcesMoments()
    in file forces/forces.C at line 753
    Porosity effects requested, but no porosity models found in the database

so likely the porosity region has not been defined - maybe do you guys have any hint, what could be the reason?

[LVDH]

Hi all, I have found following:
-RV_Tail_V02 --> added design volume (broader on the sides of the volume)
-RV_Sidepods_EngCover_V02 --> added design volume (fin can be extended in +Z in almost entire length)
-MAND_Wheel_* wheels corrected, now all 4 is at correct position (but no geo change other than that)
Can anyone confirm, or did I miss something important?

I think also some parts were renamed (mostly removing wrong "Mand_" prefixes).

Hi,
for windows users, the guide is on page 13 of last year's forum - for me v2512 works just fine on WSL with same method, and early termination seems a cool option to have!

Thanks for the info. Very helpful!

Though, I have some issue using the newer MFlow releases (with WSL based OF). Specifically the porous media is not working. Everything works fine with deck generated in an older release (v2504a_win is the only I have), but it does not work with decks generated with new ones (v2605_win, v2509_win) from exact same input_files folder. I have tried to narrow down the differences (applying the changes one-by-one) -- I believe somehow the fUpdate with fvOptions and fvOptions_off is not working quite right, and when it is added, the porosity region is not generated.
In the solver log, the model generated by the old release has an additional message:

Code: Select all

Selecting finite volume options type explicitPorositySource
    Source: porosity_HX_2
 [...]
Porosity region porosity_HX_2:
    selecting model: DarcyForchheimer
    creating porous zone: HX_2
[..]

not present in the log with the deck generated with newer release. The latter deck has a warning at each time step:

Code: Select all

--> FOAM Warning : 
    From virtual void Foam::functionObjects::forces::calcForcesMoments()
    in file forces/forces.C at line 753
    Porosity effects requested, but no porosity models found in the database

so likely the porosity region has not been defined - maybe do you guys have any hint, what could be the reason?

I cannot reproduce this. Can you please send me your case?

[Ft5fTL]

The latter deck has a warning at each time step:

Code: Select all

--> FOAM Warning : 
    From virtual void Foam::functionObjects::forces::calcForcesMoments()
    in file forces/forces.C at line 753
    Porosity effects requested, but no porosity models found in the database

I have the same problem on linux mint. Also I'm not getting the num_cfd_results.txt or any force numbers on the html file.

[LVDH]

But did you keep the case running and no forces then show up? Maybe you can send me your case.

[janci_kp]

Hi all, I have found following:
-RV_Tail_V02 --> added design volume (broader on the sides of the volume)
-RV_Sidepods_EngCover_V02 --> added design volume (fin can be extended in +Z in almost entire length)
-MAND_Wheel_* wheels corrected, now all 4 is at correct position (but no geo change other than that)
Can anyone confirm, or did I miss something important?

I think also some parts were renamed (mostly removing wrong "Mand_" prefixes).

Hi,
for windows users, the guide is on page 13 of last year's forum - for me v2512 works just fine on WSL with same method, and early termination seems a cool option to have!

Thanks for the info. Very helpful!

Though, I have some issue using the newer MFlow releases (with WSL based OF). Specifically the porous media is not working. Everything works fine with deck generated in an older release (v2504a_win is the only I have), but it does not work with decks generated with new ones (v2605_win, v2509_win) from exact same input_files folder. I have tried to narrow down the differences (applying the changes one-by-one) -- I believe somehow the fUpdate with fvOptions and fvOptions_off is not working quite right, and when it is added, the porosity region is not generated.
In the solver log, the model generated by the old release has an additional message:

Code: Select all

Selecting finite volume options type explicitPorositySource
    Source: porosity_HX_2
 [...]
Porosity region porosity_HX_2:
    selecting model: DarcyForchheimer
    creating porous zone: HX_2
[..]

not present in the log with the deck generated with newer release. The latter deck has a warning at each time step:

Code: Select all

--> FOAM Warning : 
    From virtual void Foam::functionObjects::forces::calcForcesMoments()
    in file forces/forces.C at line 753
    Porosity effects requested, but no porosity models found in the database

so likely the porosity region has not been defined - maybe do you guys have any hint, what could be the reason?

I cannot reproduce this. Can you please send me your case?

For the tail vomume you can add "Exhaust Winglet", similiar to the ones used by almost all the teams. But after adding them in the latest version of MntiumFlow (2605) I had positive exhauste pressure. On the version 2403a (the one I used before because that one was working on windows) I still have negative exhaust pressure. My question is if the possitve exhaust pressure results a penalty or DSQ or can be accepted without any consequences. Thanks.