Just a technical note: for each game I think it's definitely worth patching all found vfilters, and upload all their offsets to the cloud. So I will put all of MaeseJesus's data into the cloud, not just the ones which we think the game uses.
The reason is because there could be some cases where the game sets a different vfilter depending on whether the console is outputting 480i vs 480p, or perhaps different parts of the game set different filters. It also eliminates the issue of having to do a lot of trial-and-error to find the one the game uses, before it can be added to the cloud.
USB Loaders are then free to patch all offsets stored in the cloud, or even use their own rules about which filters they think are worth patching or not. In any case, more data in the cloud is better than less data.
Also just a progress update on the tool development: I've completed the main 'find vfilters' function and tested it quite rigorously, inserting dummy data into .dols and checking the threshold for false positive is being met. The GUI has been completed too, so I can now begin working on the main 'patch file' function. This is the scariest one because it must not make any mistakes, otherwise the consequences could be potentially disastrous. eg. writing some wrong bytes might happen to be some instruction for writing some data to sysNAND and brick the console! However it's fairly easy to test for corruption as in HxD we can use Analysis > Data Comparison > Compare vs the original file and make sure it only patched exactly what we told it to.
The reason is because there could be some cases where the game sets a different vfilter depending on whether the console is outputting 480i vs 480p, or perhaps different parts of the game set different filters. It also eliminates the issue of having to do a lot of trial-and-error to find the one the game uses, before it can be added to the cloud.
USB Loaders are then free to patch all offsets stored in the cloud, or even use their own rules about which filters they think are worth patching or not. In any case, more data in the cloud is better than less data.
Also just a progress update on the tool development: I've completed the main 'find vfilters' function and tested it quite rigorously, inserting dummy data into .dols and checking the threshold for false positive is being met. The GUI has been completed too, so I can now begin working on the main 'patch file' function. This is the scariest one because it must not make any mistakes, otherwise the consequences could be potentially disastrous. eg. writing some wrong bytes might happen to be some instruction for writing some data to sysNAND and brick the console! However it's fairly easy to test for corruption as in HxD we can use Analysis > Data Comparison > Compare vs the original file and make sure it only patched exactly what we told it to.
Last edited by NoobletCheese,