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

[CAEdevice]

Here is the TalnoRacing TR19 for this season's challenge. I was not able to run any CFD, so this is a best guess gut feel design. But I had a lot of fun modelling a sleek looking beast.

Nice, clean, quite similar to mine, but more aggressive. Congratulations!

[machin]

Here is the TalnoRacing TR19 for this season's challenge. I was not able to run any CFD, so this is a best guess gut feel design. But I had a lot of fun modelling a sleek looking beast.

https://i284.photobucket.com/albums/ll3 ... xekzlu.jpg

Nice! The first proper car reveal!

[rjsa]

Code: Select all

lRef        3.4;

to

Code: Select all

lRef        1.0;

Then you can run the case.

This is for the fast option only, right?

[CAEdevice]

Code: Select all

lRef        3.4;

to

Code: Select all

lRef        1.0;

Then you can run the case.

This is for the fast option only, right?

I think it is necessary only for the standard template: the "fast" set up includes the correct value of lRef by default (Windows version).

[rjsa]

I ‘ve gone through the file and the occurrences of lRef read 1 here. Will check again.

Did rake get axed?

[rjsa]

Yeah, 3.4. I,ve seen lRef 1 somewhere, must have set a fast by mistake while messing around.

[CAEdevice]

I ‘ve gone through the file and the occurrences of lRef read 1 here. Will check again.

Did rake get axed?

No it didn't. It is called "pitch" in the MFlow GUI (don't forget to hit "apply")

[rjsa]

I ‘ve gone through the file and the occurrences of lRef read 1 here. Will check again.

Did rake get axed?

No it didn't. It is called "pitch" in the MFlow GUI (don't forget to hit "apply")

Negative angles, right?

[CAEdevice]

I ‘ve gone through the file and the occurrences of lRef read 1 here. Will check again.

Did rake get axed?

No it didn't. It is called "pitch" in the MFlow GUI (don't forget to hit "apply")

Negative angles, right?

yes, range from -1° to 0° (nose down)

[LVDH]

I ‘ve gone through the file and the occurrences of lRef read 1 here. Will check again.

Did rake get axed?

No it didn't. It is called "pitch" in the MFlow GUI (don't forget to hit "apply")

Negative angles, right?

MFlow should correct it if you do something illegal while having an MVRC template selected.


I have been working pretty hard on a new MFlow release (not only because of your reported bugs) but still cannot package it up for Windows. So there will simply be no new release for the race. This means you have to deal with two bugs.

Depending on what MVRC template you use, the value for lRef is wrong in the system/forceCoeffs file. After building a simulation and before running it, you have to open the file with a text editor and change the value from 3.4 to 1.0. This issue affects the calculation of the CoP.
The second bug is related to the force values on the single parts, you find in the report. These values are all offset by the porous drag of your HX. Essentially they are simply all wrong. The total forces on the car are calculated correctly, though.

[jjn9128]

It would be amazing having you as a competitor. Why don't you try with a couple of races?

Go on then


Not going to be able to test it though... think I have all the parts in the right places. How is suspension affected with rake? As it's just rotating about the front axle the floor will be moving further from the ground!?

[CAEdevice]

It would be amazing having you as a competitor. Why don't you try with a couple of races?

Go on then
https://drive.google.com/file/d/1nGDXkz ... sp=sharing

Not going to be able to test it though... think I have all the parts in the right places. How is suspension affected with rake? As it's just rotating about the front axle the floor will be moving further from the ground!?

Congratulations! This car is one step above mine about modeling: it reminds me one car of a past challenge that was almost dominant.

[CAEdevice]

What happens if the engine inlet surface is a bit larger than then the duct and it overlaps it by 1-2 mm?
I have the suspect that I have problems when exporting the STL and the surfaces deos not perfectly join.

[LVDH]

Scaling these kind of surfaces up so they intersect surrounding geometry is a very good idea. You have to make sure that the remaining surface meetings the requirements on surface area.

[CAEdevice]

Scaling these kind of surfaces up so they intersect surrounding geometry is a very good idea. You have to make sure that the remaining surface meetings the requirements on surface area.

No problem, the remaining surface is much larger then required.