embedded-graphics: How to properly use the framebuffer #108
-
Hello! I'm trying to make a simple 2D demo right now before I do anything else with this, just to get familiar with it. I didn't want to touch GX or writing C bindings to e.g. grrlib, so I'm using the embedded-graphics demo as a starting point. I haven't been able to find much concrete info about video in libogc on Google. :-( My question is: How do I properly handle the two aspect ratios, and NTSC vs PAL? From my experimentation, I believe NTSC (as expected) uses only the first 480 lines of the framebuffer. Positioning things past y=480 does not show up on the screen. Does this mean that PAL will simply extend the amount of lines used to 576? That wouldn't make sense, since the framebuffer seems to be limited to 528 lines. Finally, how would widescreen work if I only have 640 horizontal pixels? Thank you in advance for any help! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You will want to change the render config handed to the
The 576 lines include under/overscan areas usually hidden by most crts so its uses 528 lines as a roughly safe area.
As a warning some things just currently don't work with the embedded-graphics examples: Not working with a circle: #43 |
Beta Was this translation helpful? Give feedback.
On Pal it does extend to 528 lines.
To get the preferred format you would need to do something like this