Welp, there's a problem...
Those files are part of the Wii U OS and modifying them will break the signature and cause a brick, and vWii cannot be launched from redNAND. Although there's a chance that modifying only the vWii-specific files won't cause a brick, it's still too risky.
However, it looks like /storage_slc/title/00050010/10004000/code/deint.txt (00050010-10004000 being cafe2wii; "\r\n" line endings) contains some parameters for the "deinterlacer", but I have no idea what it actually does (I only know it's used by nn_cmpt.rpl) nor if it's safe to edit.
I'd need the help of an experience developer who knows a way to redirect and reload (or patch in memory) the Wii U OS files after entering "CFW", while still being able to launch vWii.
EDIT: I'd patch the function 0x2002A88 in nn_cmpt.rpl, before it loads the DMCU firmware.
EDIT2: I think I'll try patching it with WUPS.
Those files are part of the Wii U OS and modifying them will break the signature and cause a brick, and vWii cannot be launched from redNAND. Although there's a chance that modifying only the vWii-specific files won't cause a brick, it's still too risky.
However, it looks like /storage_slc/title/00050010/10004000/code/deint.txt (00050010-10004000 being cafe2wii; "\r\n" line endings) contains some parameters for the "deinterlacer", but I have no idea what it actually does (I only know it's used by nn_cmpt.rpl) nor if it's safe to edit.
I'd need the help of an experience developer who knows a way to redirect and reload (or patch in memory) the Wii U OS files after entering "CFW", while still being able to launch vWii.
EDIT: I'd patch the function 0x2002A88 in nn_cmpt.rpl, before it loads the DMCU firmware.
EDIT2: I think I'll try patching it with WUPS.
That's nothing.A while ago, I read on this forum that both GBA on 3DS and Wii on Wii U had ~10 ms of input lag, but I can't seem to find the post.
Last edited by nastys,