Hello,
For a while i'm using dolphin to test my code/prg before running on the retail.
I'm also using an official devkit and from the code point of view, devkit and retail targets are quite similar .. but ok you know that guys.
Anyway, i've noticed a strange behavior on the dolphin's side related to texture updates while the same code is executed on the retail and works properly.
Say, i'm updating a 1024x1024 (dst) with many 256x64 blocks (src), in this case only half part of the texture is only updated while data are copied in the entire 1024x1024 area. Modifying the src texture size doesn't change anything while reducing the dst size to src size (256x64) is OK.
Thus, i'm suspecting a bad cache management or something as the problem is only occuring with dolphin and *not* on retail nor on devkit even if libs are != but the algo and functionalities are the same.
note: the bug affects every tex formats.
For a while i'm using dolphin to test my code/prg before running on the retail.
I'm also using an official devkit and from the code point of view, devkit and retail targets are quite similar .. but ok you know that guys.
Anyway, i've noticed a strange behavior on the dolphin's side related to texture updates while the same code is executed on the retail and works properly.
Say, i'm updating a 1024x1024 (dst) with many 256x64 blocks (src), in this case only half part of the texture is only updated while data are copied in the entire 1024x1024 area. Modifying the src texture size doesn't change anything while reducing the dst size to src size (256x64) is OK.
Thus, i'm suspecting a bad cache management or something as the problem is only occuring with dolphin and *not* on retail nor on devkit even if libs are != but the algo and functionalities are the same.
note: the bug affects every tex formats.
