the engine does not parse filename extensions (at least for models). If the qc specifies foo.mdl then the engine expects there to be a file with the actual filename of foo.mdl
If the foo.mdl file actually contains md3 data (and the engine supports the md3 format) then all is well.
Of course, your exporter probably requires that you explicitly state the extension as .md3 or something stupid, in which case you can either change your qc to use an .md3 extension instead, or just rename the file to .mdl in explorer so that it still matches.
If the foo.mdl file actually contains md3 data (and the engine supports the md3 format) then all is well.
Of course, your exporter probably requires that you explicitly state the extension as .md3 or something stupid, in which case you can either change your qc to use an .md3 extension instead, or just rename the file to .mdl in explorer so that it still matches.
Comment