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
When using HalQuickRebootRoutine with a NULLszLaunchPath and a dwLaunchDataType of LDT_NONE (0xFFFFFFFF) there is a brief period of graphical corruption before the dashboard is displayed.
XVideoInit looks like it's doing reasonable things with respect to setting AvSetSavedDataAddress to the framebuffer so I'm not sure what is causing this.
I do not see this corruption when doing a trivial launch of another nxdk-built XBE on the same data storage.
I confirmed that I can grab the framebuffer via XVideoGetFB, memset it, flush it, and see the change reflected briefly before it's replaced by corruption.
is what triggers the problem (if I comment out the lines unpersisting and freeing the previous FB the issue goes away).
I'm not sure if this is an indication that AvSetSavedDataAddress is somehow not working or if the kernel/dashboard/... just blindly uses the memory at 0x80061000 as the framebuffer when initializing the dashboard.
When using
HalQuickRebootRoutine
with aNULL
szLaunchPath
and adwLaunchDataType
ofLDT_NONE
(0xFFFFFFFF
) there is a brief period of graphical corruption before the dashboard is displayed.XVideoInit
looks like it's doing reasonable things with respect to settingAvSetSavedDataAddress
to the framebuffer so I'm not sure what is causing this.XVideoGetFB
, memset it, flush it, and see the change reflected briefly before it's replaced by corruption.The text was updated successfully, but these errors were encountered: