Yeah, I suspect that what happened is that 3.0 has revamped the font files to use unicode, so if you re-use the player fonts in VFDlib, the 3.0 fonts won't work. The solution would be, as you said, to upgrade VFDlib to support both possible font sets and autodetect which is present. We need only to know the spec for the new font files, and I've already placed a request for this with The Guys. They're pretty busy with some Real Life deadlines right at the moment, so I wouldn't expect a reply immediately.

There's no chance that someone could simply look at the new font files and reverse-engineer the spec, is there? Maybe it's as simple as "the file format is the same, you just have a larger unicode index instead of an 8-bit index"?