You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't figured out why, but it seems like printing to the console sometimes isn't written to whatever buffer Luma uses when it takes a screenshot. It would be nice if we can work around this, since taking screenshots is one of the few ways available to share debug state of a hardware device.
The text was updated successfully, but these errors were encountered:
This is more of a problem with libctru than with ctru-rs, I don't even know how much we can tamper with it. We can just search around for any documentation of this issue.
To be honest, I'm not sure what was different in this one... I just took a normal Luma screenshot with the code shown in that PR, as far as I remember. I thought originally maybe wide mode had something to do with it, or perhaps the lack of flushing / flipping buffers in the busy loop at the end of the test runners? I can try experimenting to see what makes it work or not.
I haven't figured out why, but it seems like printing to the console sometimes isn't written to whatever buffer Luma uses when it takes a screenshot. It would be nice if we can work around this, since taking screenshots is one of the few ways available to share debug state of a hardware device.
The text was updated successfully, but these errors were encountered: