noname
No offence taken, I didn't read your comments as such.
F1 teams presently do a lot of simulations and analysis of new concepts in CFD. The time required to do this means it's usually quicker to, once a concept shows promise in CFD, throw a few variations on the theme into the tunnel and tweak it for performance at a wide variety of ride positions. CFD can't do this. One of the crucial bits in Wirth's approach has to be managing the simulation of a concept at various key ride positions chosen as a discretization of key track scenarios, such that it's as effective as intended no matter what the car's doing on track. Typical CFD is done at one, or a few ride positions. Any more is generally viewed as time consuming when the same thing in a tunnel is over very quickly; possibly one of Wirth's key innovations is a new approach to managing as much with CAE tools only. Maybe they're wind tunnel testing somewhere and not telling anyone. Who knows.
horse
Fluent isn't bad and they're not the only team to use it (many very fast teams do too). It's not the fastest or most flexible code, but know how to use it and it does the job. Very few teams use anything revolutionary.
Not as if CFD designs the car? In some cases I might disagree here... it's not an impossibility but the class of solvers required aren't commercial. They're in-house and fcking complicated to develop. Judging by the cars, not all teams have them (far from it).