I make a race game.
I made this video for concept confirmation.
(not hardware scroll)
5 Likes
This is great! Reminds me of Road Rash!
MAKE THIS HAPPEN! F1 race for gameboy 
one of my faves!
Game images 
6 Likes
OLED direct rendering Test
Direct: uses 7,214 bytes (25%)
Normal: uses 7,750 bytes (27%)
Sample code
https://dl.dropboxusercontent.com/u/21132353/Race160727.zip
2 Likes
OLED Partial drawing test
-
Sample code
https://github.com/emutyworks/GameDevSample/tree/master/PartialDrawingTest -
Reference documents
SSD1306 128 x 64 Dot Matrix OLED/PLED Segment/Common Driver with Controller
http://www.eimodule.com/download/SSD1306-OLED-Controller.pdf -
Explanation of the sample code.
1 Like
OLED Scroll test
-
Sample code
https://github.com/emutyworks/GameDevSample/tree/master/Scroll -
Reference documents
SSD1306 128 x 64 Dot Matrix OLED/PLED Segment/Common Driver with Controller
http://www.eimodule.com/download/SSD1306-OLED-Controller.pdf -
Explanation of the sample code
3 Likes
We did some tests for using hardware scroll. It’s a cool function! But actually doing the same thing in the software is just as fast, or faster even.
The question that may not be answered, does it use less memory space? Are there other advantage to doing it this way?
Thank you for information.
I only confirm its setting method now.
I judge whether it is convenient after incorporating it in a game.
Sounds like a cool game 
1 Like
The big problem with hardware anything is you can’t update the school WHILE the hardware modes are engaged… hardware scroll where you could update the screen inbetween frames might have uses… hardware scroll where they screen must be static the entire time is much less helpful for anything.