Thanks, that helped me track down the problem.
I've got a fix that'll go in the next fix drop for 4.25 (around 4.26 release, so hopefully soon).
A workaround that _might_ work until then is to add a "wad" property, so it forces the parser down the classic map path...