-
-
Notifications
You must be signed in to change notification settings - Fork 124
Add VRAM Tile Data diagram for layout of sprites and BG/WIN #283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This is explained elsewhere. Besides, it should be formatted either as a table, or as a SVG. |
|
Sorry, it sounds like I worded this too harshly. I think a diagram would be useful, I just think not in this form. Should we re-open this PR for improvement? |
|
If someone else is up for re-making the diagram, sure. I'm not motivated enough to do an SVG. :) |
|
I dunno, that's open to debate; I think a table is more accessible, but we could put more info in a SVG. Perhaps noting VRAM bank 1 as well, and arrows indicating what selects the "block"? |
|
I was just suggesting that alternative in case we wanted to add extra info / color-code the diagram, etc. |
|
The ascii table is easy to convert to a markdown table. Although pure markdown doesn't seem to support colspan=2 for a shared BG/WIN Tiles header, which might look better.
Or...
|
We can use HTML tables with no issues in pandocs, maybe that way you can put |
|
Sure (copied from the markdown output). I looked around to see if there were special css styles that should be applied for tables but looks like the defaults cover it- is that correct?
|
|||||||||||||||||||||||||
Looks good to me! We can use this version |
A simple diagram companion to the text. It might help people conceptualize how the tile vram is arranged. This came out of a conversation where someone was trying to understand it.