Honestly can't remember... So far as I know, there were 3 main points in picking the display at that stage of development:
- Implementation time - we were now still fixing major bugs after we'd intended to release, this needed to be something that was going to work quickly.
- Permissions - I see now that Kreuger+ can be used without any need for permissions, but when looking at display types we couldn't use them if we weren't going to be able to get permission to do so (where required) in the next day or so.
- Compatibility with other vehicles - almost every bus uses different types of matrix, but we hoped to use one that was at least somewhat compatible with another bus...
As it happened, we were able to use the Busfanat matrix with Mobitech fonts - this was the same as the one in the B9TL, so we knew it worked, Rhys had some knowledge of it, it was compatible with the same HOFs (except where overflow is a thing) and we had permission for it, so it went in.
I do have some WIP scripts for a Hanover Deric+ and signs which work somewhat similarly to the Krüger signs, with the intention that they'd have as much of the real functionality as is possible both practically and without degradation to performance (my initial tests into scrolling text resulted in scrolling text, but also in dropping an empty maps frame-rate from 200+ down to about 30...), but they weren't (and still aren't) ready to be put into the bus, so they didn't make it in. Given the CC0 nature of Krüger+ and my investigation into it hinting at some similarities with what I want to do, I might borrow some code and perhaps make the system compatible with Krüger+ HOF files.