[MVRC] Mantium Virtual Racecar Challenge 2017

[CAEdevice]

No image here, Matteo.

Are you sure? Maybe it depends on Dropbox settings, you can try with this alternative links:

https://www.dropbox.com/s/wch8w8iqt2v0f ... 7.jpg?dl=1
https://www.dropbox.com/s/wch8w8iqt2v0f ... 7.jpg?dl=0
https://caedevice2014-my.sharepoint.com ... 3d761d17a2

[rjsa]

It's ok on the desktop, does not appear on the iPhone.

Very nice!

[rjsa]

I have been working on something but only matched the previous car's times so far:



Odds are I'll re run the old one.

[CAEdevice]

I have been working on something but only matched the previous car's times so far:

http://i.cubeupload.com/7YAQAq.png

Odds are I'll re run the old one.

I notice some developments, well done.

I was in the same situation a couple of months ago, but now I have a new area to develop. I will not have a big performance improvement for the next race (not enough time), but I am sure that these cars are far from being completely developed (df/dr ratio 8 is possibile... in 2018).

[machin]

Nope

Today I saw an animation with the new CAESES MVRC diffuser. It looks good and I gave it my thumbs up. It should be available for you guys very soon.

Will it be released before the last race? Or wait until afterwards?

[CAEdevice]

Is the deadline 3rd December or 10th?

I am not sure, has the official web site been updated?

[LVDH]

Yes, it has been updated a while ago. From the 26.11. to the third of Dec. But I forgot to send the usual email about the race being one week ahead. If you guys like, I can delay it for another week.

[CAEdevice]

Yes, it has been updated a while ago. From the 26.11. to the third of Dec. But I forgot to send the usual email about the race being one week ahead. If you guys like, I can delay it for another week.

No problem for me, the car is almost complete and I am so busy with another project (a gearbox) that I will run only another couple of simulations to fix a detail.

[rjsa]

I'll repeat the car from the two past races. I have something new as posted above but it isn't worth submitting.

[schwepes]

Yes, please. I was sure that race was postponed to 10.12. I will be ready for the next weekend. For this weekend I can only submit a car without even a single calculation... Or even not..

[AratzH]

I also thought it was postponed to Dec 10...
Also I have some issues with MantiumFlow. When I try to build the case it gets stuck in loading geometry 30%.
I have win10 pro version 1703
MFlow version released 10 11 2017
The case is located in a folder inside my documents, I have executed MFlow as admin, geometry is ok, or at least shows ok in the preview... Never had this error before.
Any ideas?

[variante]

I didn't answer before because it doesn't really make a difference for me, but I think the deadline should be postponed by one week. The new guys could take advantage -more effectively- of this round to make some experience for a more competitive 2018 season, while it won't make such a difference for the main teams since the championship is pretty much decided.

[LVDH]

Ok guys,
I talked to Chris and Richard and we will have the race delayed another week. It will be on the 10th!

An Email went out with the file submission link. As there are so many new names here, please make sure you got the email. If not, please let me know.

I also thought it was postponed to Dec 10...
Also I have some issues with MantiumFlow. When I try to build the case it gets stuck in loading geometry 30%.
I have win10 pro version 1703
MFlow version released 10 11 2017
The case is located in a folder inside my documents, I have executed MFlow as admin, geometry is ok, or at least shows ok in the preview... Never had this error before.
Any ideas?

Send me the case. Its probably an easy fix.

[LVDH]

I just received a cool email: The CAESES app has been updated:
https://www.caeses.com/products/caeses/ ... pp/racecar

[LVDH]

I also thought it was postponed to Dec 10...
Also I have some issues with MantiumFlow. When I try to build the case it gets stuck in loading geometry 30%.
I have win10 pro version 1703
MFlow version released 10 11 2017
The case is located in a folder inside my documents, I have executed MFlow as admin, geometry is ok, or at least shows ok in the preview... Never had this error before.
Any ideas?

I have more or less found the issue. The stl file format is not exactly a standard and your CAD tool seems to be exporting the files with some strange extra data. It could be the PIDs which now have non UTF-8 characters. I am not 100% sure what causes the issue. You can fix it though by using Paraview to export the stl files as ascii. Then it works. Did you change or update your CAD tool? Maybe you are just using strange characters in your PID names.