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
Executing the reboot item causes the screen to be corrupted until the return to dashboard occurs (looks likely to be uninitialized data).
I assume this is because of the use of exit() rather than explicitly launching w/ no executable path. If XboxDev/nxdk/pull/501 gets merged, this can probably be solved by changing the exit to XLaunchXBE(nullptr).
Calling XReboot() also fixes the graphical corruption but that's a full reboot instead of a quick one, which probably isn't desirable for users of bios loaders like Phoenix.
The text was updated successfully, but these errors were encountered:
Looks like I'm wrong about using an explicit HalQuickRebootRoutine; I still see the same corruption after patching 501 and calling XLaunchXBE on my v1.0 XBOX.
Digging around a bit, I think the issue is the lack of a PersistDisplay equivalent to store the framebuffer.
It looks like XVideoInit is already persisting the framebuffer though, so it's not immediately clear to me why the screen doesn't simply freeze.
Executing the
reboot
item causes the screen to be corrupted until the return to dashboard occurs (looks likely to be uninitialized data).I assume this is because of the use of
exit()
rather than explicitly launching w/ no executable path. If XboxDev/nxdk/pull/501 gets merged, this can probably be solved by changing the exit toXLaunchXBE(nullptr)
.Calling
XReboot()
also fixes the graphical corruption but that's a full reboot instead of a quick one, which probably isn't desirable for users of bios loaders like Phoenix.The text was updated successfully, but these errors were encountered: