Z (I'll start here).
Take your earlier Kipling quote regards words, knaves and fools and apply it to what you've quoted of mine.
There are two events. Design and Presentation. Complete different purposes and yes, there is some degree of interrelation, no more than needing to accelerate out of a corner doesn't obliterate the need for an acceleration event.
We are asked, as judges, to do our best to extract relevant information from students in design. Our job is easier if it can be presented well, and at the other end its difficult if the students concerned are mute or intent on presenting something other than their design (which actually happened twice this event). Either way, we do the job.
The remarks on presentation are made as they affect team culture. Monash certain occupied the top end. At the other we had teams that really didn't give a rat's about the event, and guess what, it showed in the integrity of their design. The clock ticks on 15 minutes all the same. If we get a team looking like junkyard dogs and talking smack that can explain a 100% design, that's what they'll get. Yet to happen.
On design ownership, if a team puts a year of work into a design and when it comes time to bear it to scrutiny has someone present it that doesn't own it, doesn't understand it as well, isn't passionate about it - which ironically happens usually because teams believe it's better to have someone 'who presents well' do the design event - then guess what, we can't award points just because it looks awesome if the person trying to tell us why doesn't have a legitimate clue about it (twice at this and last year's event in my section). We will fumble through language barriers in addition to all shades of social awkward to search for understanding.
The best Design Event aero presentation last year scored 10%. The worst tied for top place.
Design judges are professionals from an industry that prides itself on an ability to assess much in an impartial, scientific manner.
Your statistics are unfounded shit. That's a technical term. Don't teach anytime soon.
Well guess what, you're in complete luck. Design Event is about the design of the car itself. Your hysteria about what you think the design judges are or aren't, there's a lower noise floor in the static events than the dynamic events. If a great design is going to shine anywhere, these are easy points.
Wow. Where to start.
I'm sorry that you believe R% is the only "most overwhelming factor in improving the performance of these cars" you see. There are, in fact, many.
Appreciably it'll come as a complete shock to you, however the 15 minutes allocated per team is to judge the design. Not:
To educate students,
To interfere in a faculty's educational program or principles,
To cater for the wide gamut of student levels within any given FSAE team,
To understand a university's drivers for competing in the competition and how this affects educational goals,
To gauge the quality of the student(s) concerned,
To make decisions on the best means of delivering relevant knowledge,
To devise and deliver a means of testing the understanding of such knowledge,
To devise a feedback program in learning to ensure the knowledge was applied and further learned from in a correct manner...
...or the myriad other things that constitute the professional delivery of education... which you seem to have little concept of, and have confused for what design judges actually do in the Design Event.
Those wanting a formal education pay for it and receive it in a learning institution. To participate in FSAE, competitors must be linked to one. Many universities internationally use FSAE as a project-based learning vehicle, and some have even in part devised degree programs around it in part. Design judges and the design event exist to competitively evaluate the net work of educational processes and programs at a variety of learning institutions as applied in a project-based learning environment. The event does not exist to replace formal education: it is a complement. Sure, some universities make a better fist of closing that loop better than others, and have greater success accordingly, and have used that success to drive further uptake of their degree programs.
What the hell do you reasonably expect, in as complex an engineering system as a car, a third-hand individual to impart in fifteen minutes?
If a small boy can understand it, the problem is not the complexity or obscurity of the knowledge. If you've posted it here ad nauseum, the problem isn't a paucity of the knowledge.
At the other end - I don't make any attempt to compress many years of experience in my field into some sort of a quarter-hour knowledge enema. Teams that have sought out my advice do so over many sessions and many hours each, which starts a journey. One uni asked for an hour after their dynamic events and got it. Those involved left with more questions despite more understanding. I don't give fish because it's a crap way to teach anything.
What journey student teams take to trade of many complex factors to design a car - starting with what information is considered, how it is considered, where any why choices and compromises are made - is their own learning experience. It doesn't end at the end of competition.
If you want to see a formula where lessons passed on year-on-year are absorbed cumulatively in the endless pursuit of competitive performance, go watch F1. That's not what Formula SAE is for. Students are free to absorb or ignore information from any source and do with it what they will. They're allowed to make highly original breakthroughs and mistakes in equal measure. We judge how and why it comes together.
We provide feedback as a starting point. There is much that can be done around the immediacy and the transparency of that feedback, though that feedback is not and will never be a set of definitive answers able to be used in a formulaic context. If we gave all the answers, it'd not be a student competition set in a learning environment. Deal with it.
The most a student will get out of me is a suggestion, if I'm asked for suggestions outside of the design event to this end, to consider where any why CoG should be. That there might be better answer than what a team might currently run. Do I know more? Can I formulate a process to give a specific answer? Sure. Couldn't I pass that onto the student in question? Only if I'd completely missed the point of the competition.
It takes a particular kind of agenda to take such a comment and interpret it as you have. Your attitude - promoting some sort of combative relationship with industry seniors - is not something I'd suggest students seek to emulate.