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
Xbox is annoying about resource alignment and is insistent on it being a magic number - we get it right at first but it doesn't always stick; FNA3D hits it after setting our second dummy texture data:
Got a better explanation: While we realign source data to match Xbox's needs, it turns out it also cares about slices being aligned too. So this increment ends up breaking the rule after slice 0:
Xbox is annoying about resource alignment and is insistent on it being a magic number - we get it right at first but it doesn't always stick; FNA3D hits it after setting our second dummy texture data:
https://github.com/FNA-XNA/FNA3D/blob/master/src/FNA3D_Driver_SDL.c#L4472
Pretty sure we had this right at one point but resource management has probably changed a lot since our last Xbox checkup.
The text was updated successfully, but these errors were encountered: