I am making some assumptions here since I have not seen this in the documentation.
You are loading some functions as standard into the 2K of shared ram that allow the 6809 and Vectrex hardware to act as a display list processor.
You turn the basic display into an optimized instruction list that call on board ROM calls in the 8K space the internal Rom has to do the drawing, and read controller status into the shared ram per hardware frame.
You can change these shared ram updates dependent on how fast the 6809 can do the draw commands. And you idle the 6909 the rest of the time.
Is there a rule of thumb of how many vectors you can fit into the 2K and still make them run in one frame? That would seem to be the way to run it, and the calculate the frame rate and the music rates back from that.
Does that make sense?
-Cecil
You are loading some functions as standard into the 2K of shared ram that allow the 6809 and Vectrex hardware to act as a display list processor.
You turn the basic display into an optimized instruction list that call on board ROM calls in the 8K space the internal Rom has to do the drawing, and read controller status into the shared ram per hardware frame.
You can change these shared ram updates dependent on how fast the 6809 can do the draw commands. And you idle the 6909 the rest of the time.
Is there a rule of thumb of how many vectors you can fit into the 2K and still make them run in one frame? That would seem to be the way to run it, and the calculate the frame rate and the music rates back from that.
Does that make sense?
-Cecil