Pixelboy #1 Posted April 28, 2012 I could test this myself, but I'm thinking I can get clearer information by simply asking here. I would like to know what happens exactly when screen_off() is used. Does the screen turn black until screen_on() is called? Or is the current graphic display just frozen on the TV screen? Quote Share this post Link to post Share on other sites
hardhat #2 Posted April 28, 2012 The screen_off() stops displaying everything except for the background colour. So that way when you are massively updating the graphics tables you don't see flashes of garbage displayed while the screen is updated. Quote Share this post Link to post Share on other sites
Pixelboy #3 Posted April 28, 2012 The screen_off() stops displaying everything except for the background colour. So that way when you are massively updating the graphics tables you don't see flashes of garbage displayed while the screen is updated. Yeah, I know. But what I wanted to know is what I would see on the screen if I made intensive graphical rendering that would require a couple of NMI cycles before calling screen_on() to display the results. You've pretty much answered my question, so thanks. Quote Share this post Link to post Share on other sites
hardhat #4 Posted April 30, 2012 Just the background colour and nothing else. Quote Share this post Link to post Share on other sites
Pixelboy #5 Posted April 30, 2012 By the way, does the VDP stop sending a NMI to the CPU every 60th of a second while it is disabled this way? Quote Share this post Link to post Share on other sites
hardhat #6 Posted May 3, 2012 They are independent flags so I would expect the NMIs to continue as usual, but I haven't specifically done that in a while. Quote Share this post Link to post Share on other sites