If tasvideos.org used a similar design, then there could be two possibilities: One possibility would be to not use tabs, and instead list all the TASes for that game as a list (in a reasonable order, starting with "any%", followed by "100%" if it has one, and so on). The other possibility would be to use tabs for each category, and show the entire publication history of that category in its tab. This kind of design would easily allow us to get rid of the principle of keeping the number of categories for a single game minimal (which I think is rather unnecessary).
Takanawa's movie is quite a bit faster... although I can't seem to get it to sync on BizHawk. So maybe I should cancel this submission and we should publish his?
(Actually, they patched out some glitches in the PAL version, but none of the ones that are beneficial in any current category)
ALWAYS make sure to backup your progress! There is a chance that BizHawk will crash suddenly because of the script.
There was a problem with luainterface (the pre 2.0 lua) that occasionally causes memory leaks. If it still happens please report it.
Also, thanks for posting the script!
If we do this, then all released versions of a game should be treated as its own "platform" too, meaning a game could have any% for NTSC 1.0U, NTSC 1.1U, NTSC 1.0J, PAL E, PAL A etc + all ports to other systems, including virtual console-ROMs where these are new builds.
How to cheat Blue Rescue Team: *Start Treecko *Learn Bullet Seed *Learn Agility *Learn Bullet Seed two more times *Link all of them together *Oneshot every boss in the game
Also this is what happens if I restarted a chapter after playing back the movie without following the steps in the first post of the submission:It gives me a glitched amount of ammo, all weapons, all maps, all valid entrances for said maps (including glitched ones) and all items. Saving and resetting at this state won't save it. Also it allows the map screen to scroll to the courtyard and basement, even though that normally isn't allowed.
Why the crap does Bronycon have a Nicholas Cage Appreciation Panel?
Link appears dead. But did you had fun?
This warning will now popup over and over, even if you press "continue". I had to use task manager to close BizHawk.
The warning text was:
https://pastebin.com/D84Wn0b9
This was tried on the interim build, and happened because I misclicked and selected a bk2 file instead.
Before translating articles on the site some of the original english pages may need a rewrite, most of these are not up to date with the current TASing standards, are to specifically bounded to one emulator or don't explain the content very well to newbies. I checked Articles -> Movies -> Movies Making http://tasvideos.org/LuaScripting.html and subpages: Only hold information for mostly FCEUX, SNES9x and DeSmuME. http://tasvideos.org/MemorySearch.html: Only an example for the easiest one, but not for the more difficult ones. http://tasvideos.org/EmulatorResources/RamWatch.html: Too emulator specific. http://tasvideos.org/LiveStreams.html: Outdated content. http://tasvideos.org/TASTutorial.html: Dead links and one outdated content in "Various TAS process demonstrations"
Also, to follow this idea, we need something like a Translation module, to show available languages for each page, as well as the language you are currently on. The way it is done now, the WelcomeToTasVideos page has a small header, in plaintext, linking to other languages; but this will get tedious to update if much more languages are added, since you will need to edit that header for every single page translation as well.
Write an Interpreter for the GameCube/Wii Rendering Pipeline within Shaders and Run it on the Host Graphics Card Sometimes, one of the best ways to solve an impossible problem is to change your perspective. No matter what we tried, there was no way to compile specialized shaders as fast as games could change configurations. But what if we don't have to rely on specialized shaders? The crazy idea was born to emulate the rendering pipeline itself with an interpreter that runs directly on the GPU as a set of monsterous flexible shaders. If we compile these massive shaders on game start, whenever a game configures Flipper/Hollywood to render something, these "uber shaders" would configure themselves and render it without needing any new shaders. Theoretically, this would solve shader compilation stuttering by avoiding compilation altogether.
Dude, seriously? You're counting the people in support and not even bothering to count how many people oppose? Ever heard of "due diligence"? :D This game pretty obviously fails point two, three, and four on your list.
Many PAL games have different physics in some way, as the character is often sped up to "match" the speed of NTSC. Other examples are Super Mario World and A Link to the Past. How different do the versions have to be for them to be "two different games"? Are the differences themselves enough, or do they have to be faster than the NTSC strats? I personally see no real difference in SMB compared to Super Mario World, where you could do several tricks and timesavers in the PAL version that are not possible in NTSC. The only thing is that the PAL run will still has a slower finish time. So if this SMB run will be published because it has different physics, then so should PAL ALttP and SMW and so on.
Also it would be cool to see a sentence or 2 in the publication description about how PAL usually loses a lot of time over NTSC. For example Sonic, Metroid and nearly every SMS game take 20% longer on PAL. But some games like Mario adjust the physics to compensate, which in this case causes more glitches. This would hopefully avoid confusion of people thinking that PAL is faster for every game, where in reality its usually at a huge disadvantage for most games.
