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

[Dodgy_Malaka_69]

I've attached the top view of the ref vol of chassis and EC. For the sidepod ref vol(blue color); if its not allowed to cross the blue region, then the sidepod wont be attached to the body and I dont think we're always supposed to stay on the edge of the chassis ref vol.

I'm guessing EC ref vol was kept at that place to prevent the overlap with chassis ref vol and we can connect it to the body through the ref vol?

https://imgur.com/a/3y4hhml

[yinlad]

I've attached the top view of the ref vol of chassis and EC. For the sidepod ref vol(blue color); if its not allowed to cross the blue region, then the sidepod wont be attached to the body and I dont think we're always supposed to stay on the edge of the chassis ref vol.

I'm guessing EC ref vol was kept at that place to prevent the overlap with chassis ref vol and we can connect it to the body through the ref vol?

https://imgur.com/a/3y4hhml

I thought all of these volumes had been combined in the latest files package, but in any case the separated volumes for the bodywork doesn't mean parts can't cross their boundary.


Such restrictions would be covered in the rules if a part has to be fully contained within a specific volume or have a certain number of sections

[Dodgy_Malaka_69]

I've attached the top view of the ref vol of chassis and EC. For the sidepod ref vol(blue color); if its not allowed to cross the blue region, then the sidepod wont be attached to the body and I dont think we're always supposed to stay on the edge of the chassis ref vol.

I'm guessing EC ref vol was kept at that place to prevent the overlap with chassis ref vol and we can connect it to the body through the ref vol?

https://imgur.com/a/3y4hhml

I thought all of these volumes had been combined in the latest files package, but in any case the separated volumes for the bodywork doesn't mean parts can't cross their boundary.


Such restrictions would be covered in the rules if a part has to be fully contained within a specific volume or have a certain number of sections

I have been using the latest file folder, the V05 one. Anyways, thanks for the confirmation!

[AlexTitaneGP]

Ok, so I can answer two lines of questions at once.
Please use the newest MFlow version. It does not only support newer OF versions and a bit nicer post-processing but has additions needed for MVRC 2025. This includes meshing these critical areas on the floor a bit more refined. So, please use it and let me know if you are happy with the mesh. The cool thing about newer OF versions is that we could increase mesh resolution in the entire floor area without blowing up the mesh too much, as it is possible to refine into only one direction. I have never tried this out though, but looks rather simple.
The races will be conducted with OFv2412. Now, you can still use the blueCFD version that is based on OF 5. Somebody asked about OFv2303. I am pretty sure that this does not work and MFlow tells you so.
To install OFv2412, the instructions on the OF page are pretty clear:
https://develop.openfoam.com/Developmen ... ed/windows
I recommend option 1.
And from what I can tell (sadly currently not test), in WSL2, installing graphical applications should work as well.
So, if you guys can confirm to me, you can get the graphical stuff working as well, you can use the MFlow Linux version in WSL2. Then MFlow for Windows is dead, which will open up much more development time for MFlow for useful features. Windows compatibility really eats a lot of my time.

Regarding the radius rule, we are getting there. It will be for race 2 though.

Hi Everyone,

just to let you know that I will not attend this year challenge due to the "windows is dead" topic. I fully understand that it's very time consuming to support several OS however the modeling tool I'm using is windows based, and I really dont see myself switching from one to another to developp that car (at least for now, perhaps I'll invest in another computer in the near future).

I had few wings and a dedicated floor for this year but the car was definitely not ready (significant balance issue, and I was not succeding to extract performance from those diffuser strakes + old chassis and bodywork).

thank you guys for organising that challenge, I'll still follow closely your cars and results !

Alex

[spacehead3]

just to let you know that I will not attend this year challenge due to the "windows is dead" topic. I fully understand that it's very time consuming to support several OS however the modeling tool I'm using is windows based

I think you misunderstood, you don't need to change your CAD software. Its just Mflow that Andre is proposing to end windows support. It took me about an hour to download and setup a virtual Linux machine within windows to run the new version of Mflow, the instructions are pretty straightforward. And up to this point I've just been using the old version of Mflow for windows, so that's always an option if you don't want to bother with Linux at all.

[AlexTitaneGP]

I think you misunderstood, you don't need to change your CAD software. Its just Mflow that Andre is proposing to end windows support. It took me about an hour to download and setup a virtual Linux machine within windows to run the new version of Mflow, the instructions are pretty straightforward. And up to this point I've just been using the old version of Mflow for windows, so that's always an option if you don't want to bother with Linux at all.

mmm I didn't though about using a VM which makes perfect sense ! I'm really bad at those IT stuff but I'll give it a try ! thank you. Is there any recommended linux distribution to use ?

[spacehead3]

mmm I didn't though about using a VM which makes perfect sense ! I'm really bad at those IT stuff but I'll give it a try ! thank you. Is there any recommended linux distribution to use ?

See Andre's post on the previous page, I just followed the instructions in the link