> While this is a vague response, the dev's might enlighten you on what's fully
> involved - but the gist of what we've always been told is that the way MAME handles
> vector graphics has to be completely re-written and it would be a long complicated
> process that no one really wants to do (at least at this point). While that doesn't
> explain what needs to be done, it sounds like something they're not eager to do
> because of all the work that will be involved
basically MAME drivers attempt to snapshot a position in time and call it a frame (there are various hacks in the drivers for this) while real vector monitors don't have such a concept so the timing of the data fed to them is what is important.
MAME needs some much more complex code to simulate the lines, and determine which are visible based on how recently they were written, how bright they were based on how long the beam stayed in one place etc.
That's the dumbed down version anyhow. The code in MAME right now is closer to trying to port the games in a 'convenient for PC users' way, rather than emulate the behaviour of the monitors.