My question is - At what point can RNG intensive sections of a game be considered "Good Enough"? Do I need to use my "Optimized" day 1 solution as opposed to my Non-Optimized "Swag" start, even though the SWAG start gives me a better RNG sequence on day 2? Without help from someone in terms of RAM watch or RNG reverse engineering, spending another 100 hours trying to brute force a solution that /Might/ be faster than what I have doesn't sound like an effective use of my time considering I have another 1.5-2.0 hours of gameplay I need to do frame inputs on.
Question about the category tag "Uses a game restart sequence": Does this include pressing reset at the very beginning to skip the intro?
Golf has 21 courses, but you can only play 18 in one game - the "Special" holes are isolated from the others. Would it be better to have a "Golf, 18-hole game" and "Golf, Special course" category, or to slam them both into a larger category?
When first booting up the game, you're usually forced to play through an altered version of the Skydiving game mode before you can do anything else. The game doesn't even count it towards your progress - in an All Sports TAS, you would still have to play through it again later. Given the inconvenience of this, would it be acceptable to just have a verification movie attached for some TASes so that they don't have to do this?
Stage Start End Time
1 1079 1271 192
2 2095 2347 252
3 3253 3513 260
4 4375 4551 176
5 5627 5983 356
6 6942 7314 372
7 8262 9026 764
8 10108 10424 316
9 11290 11702 412
10 12584 12888 304
11 13841 14369 528
12 15326 15974 648
13 16978 17722 744
14 18721 19469 748
15 20325 20853 528Stage Start End Time
1 1026 1218 192
2 2025 2277 252
3 3166 3426 260
4 4271 4447 176
5 5506 5862 356
6 6807 7179 372
7 8110 8874 764
8 9941 10261 320
9 11110 11522 412
10 12387 12691 304
11 13627 14155 528
12 15095 15743 648
13 16730 17474 744
14 18457 19205 748
15 20044 20572 528A new movie may involve emulation accuracy improvements. Always ensure the new movie has gameplay improvements. If the new timesavers can be applied to the old movie, they count as improvements. If new timesavers only become possible due to accuracy improvements, they are also valid. But if the only difference is in slightly different timing of otherwise identical events, it's not an improvement, but only a resynchronization.
Would it help if I ran that console verify script on both versions of the run and post results here?
Game Boy/ Game Boy Color Console Verification Pipeline with new halt bug accuracy Needed - A Game Boy Player and Game Boy Interface (GBI). An SD Media Launcher, modchip, or some other method is needed to load GBI and the input movie. These methods are -only- used to load the GBI homebrew software and interact with the Game Boy Player, they do not in any way modify the behavior of the official Game Boy Player hardware. Use BizHawk 2.3.1 Write your TAS using the Gambatte core and use this LUA script to dump the inputs to a file that GBI can use. There are some indications that it is faster and more accurate than the GBHawk core at the moment. https://pastebin.com/NbTRNePD Alternatively, write your TAS using the GBHawk core and use this LUA script. https://pastebin.com/GD0ZTJYe rename your timestamp output to yourmoviename.txt and optionally gzip it put the movie file on an SD card with GBI or GBI-HF, both inside a folder named GBI (for example E:\GBI\gbihf.dol and E:\GBI\yourmoviename.txt.gz) create a CLI file in the same directory name gbi.cli or gbihf.cli respectively to pass your input movie to GBI, the cli should contain an argument --movie=yourmoviename.txt.gz along with any other arguments that you use to tune GBI. Run GBI or GBI-HF from the SD card. I do this using Swiss, which I rename to autoexec.dol and place on the root of the FAT16 formatted SDHC SD card. From swiss it's easy to choose which version of GBI to load to load other homebrew. Watch as GBI plays back your console-accurate TAS! Credit to Extrems, AlyoshaTAS, and Gifvex for their help with getting console verification to where it is.