Link is up now (hopefully it'll stay that way too, but we have the Internet Archive upload too just in case): https://www.smbarena.com/public/hack?id=3726
Do the submission notes need another update to reflect that? Just making sure.
The setting 1000 FPS was an estimate about an order of magnitude higher than 60 FPS. See here https://youtu.be/VNhlWpIJJb4 for why this is an underestimation.
run500.exe!ADRIFT.frmRunner.SubmitCommand() Line 1626 C#
run500.exe!ADRIFT.frmRunner.txtInput_KeyDown(object sender = {Text = "Ø 6utfuyk"}, System.Windows.Forms.KeyEventArgs e = {KeyData = Enter}) Line 1549 C#
System.Windows.Forms.dll!System.Windows.Forms.Control.OnKeyDown(System.Windows.Forms.KeyEventArgs e) Line 12223 C#
System.Windows.Forms.dll!System.Windows.Forms.Control.ProcessKeyEventArgs(ref System.Windows.Forms.Message m = {System.Windows.Forms.Message}) Line 13238 C#
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref System.Windows.Forms.Message m = {System.Windows.Forms.Message}) Line 16006 C#
System.Windows.Forms.dll!System.Windows.Forms.RichTextBox.WndProc(ref System.Windows.Forms.Message m) Line 3867 C#
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 256, System.IntPtr wparam, System.IntPtr lparam) Line 761 C#
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows.Forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(System.IntPtr dwComponentID, int reason = -1, int pvLoopData = 0) Line 305 C#
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason = -1, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.ApplicationContext}) Line 1236 C#
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) Line 1152 C#
run500.exe!ADRIFT.frmRunner.Main() Line 552 C#In other words, if the DOS game doesn't have an option to turn vsync off it should only be TASed at the intended in-game framerate, no ifs ands or buts about it.
While a modern system that disables v-sync in ScummVM can play the game at the speeds/FPS this submission demonstrates, would a PC around the time that Loom was released be able to match this kind of speed running the game natively in DOS (not in a ScummVM emulator)? Was disabling v-sync even possible in the original game, or is that a functionality only introduced through use of ScummVM?
Hope it answered your question, I realize I just explained the "result" difference but not gameplay; it boil down to visiting different rooms and obtaining different relic. So if you put side by side "low level" and the jp 3kills, there will be gameplay or time difference, (edit: you can have a look at this wip to get an idea) this sound a bit vague but it is hard to quantify with precision; the first ~7min are very similar, one then goes cavern while the other go olrox/colloseum and backtrack to entrance, different way to obtain the bat, then in reverse castle one go colloseum the other olrox.
just for the sake of asking, what core I am suppose to use? nymashock or octoshock? is theres even a difference anymore?
ROM Hacks ROM hacks must not be overly obscure. If a hack is known to GoodTools, ROMhacking.net, SMW Central, or some other well-known database, that usually means its quality is decent and it won't be completely lost in the future.
- There must be a publicly and readily available download link to the hack's patch file on the web. It should be easily found through Google. Having to join an online community (for example on Discord) to get the file is not allowed.
I guess the only other in-progress run is 80 star, which is defined by no glitches in the castle, but will probably also avoid tunneling completely. The only likely submissions to use tunneling are improvements to 0 star.
I have difficulties to make decisions about obsoleting [2657] PSX Castlevania: Symphony of the Night "pacifist, low level" by ForgoneMoose in 21:08.62 I'll try to be specific; The pub movie does 5 kills (gaibon/slogra/doppleganger/venus/dracula), and use replay mode (dirty sram), the reason for this is to acquire the duplicator and make a long chain of Heart Refresh at the end to skip shaft boss, without that it would be 6 kills (and lot faster as well). Now im planning on using a different version of the game (the original jp release) that allow to skip shaft without the long chain of Heart Refresh due to a bug present only in this version, and reduce kills to 3 (doppleganger/sword master/dracula) because you dont need to kill anymore the venus. Because I dont need anymore the duplicator at the end, should I not use dirty sram? This does have multiple consequences in term of routing and/or speed, aside the duplicator use for skiping shaft, it enable to buy the shurikens (infinite uses) to kill dracula quicker or replinish mana. If I forgo sram usage, killing dracula will be notacibly slower, it will also force me to go trough at least 4 dialogues sequences, they can only be skip with replay mode and they ammount for several minutes (more than 5). I dont really believe having a pub with and without replay mode would make much sence (for a pacifist run anyway), the gameplay differences would be relativly small aside the extra time spent to kill dracula but there is some differences. That been sayd if it helps in the decision making, I could make a seperate movie for both options if thats the best course of action, but it is time consuming. Lastly, the current pub is labeled as "pacifist - low level", while my movie will have less kill, it will also have higher level/exp gain, does this mean the current pub could potentially been a seperate branch on its own? or should this sub-category "low level" just go away ? (just to be clear, this would mean theres room for obsoleting it with a 4 kills run on usa version). Any guidance will be much appreciated
Just giving some feedback as someone who care a lot about TASing, but is not too familiar with Pokemon: including a goal like this lumped in sort of compromises record-keeping as an any% run, given this is a separate goal, not a traditional mid-run speed-entertainment tradeoff or something similar. I do understand an idea of efficiency with a mostly redundant run, but I also think it's important to set a good precedent for future obsoletion and have a carefully considered run endpoint.
I found that the RNG address ($0379 WRAM) in Dirty Racing (Game Boy) will be set to a different initial value when starting in GB mode, in GBC mode or in GBA mode. The RNG value that can be achieved when starting in GBA mode will give the most favorable outcome. Is it ok to TAS this Game Boy game in GBA mode?
Backwards compatibility modes, such as running Game Boy games in Game Boy Advance mode, are allowed if a physical console (or the game) supports it, unless there significant glitches. For the purposes of Movie Rules we define significant glitches as audio, video, and/or gameplay-affecting glitches apparent to people unfamiliar with the game.
Hello. https://youtu.be/ClFSXWVz0i4?feature=shared Well, this is a TAS for X5 'Extreme Collect', and I thought of a route that should be faster. But that route would make me lose probably one power-up part, and to be exact, it's Matterex's. Would this route still be valid for Extreme Collect?
677227 frames (3:02:39.93)
I'm unsure if tunneling would be used in any future jumpless movies. Off the top of my head it wouldn't save time anywhere in jumpless any%, but it would be used in a potential maximum stars jumpless or 150 stars minimum jumps run, though that's not planned right now. The WIP 150 stars run is avoiding tunneling. So in general it's mostly avoided.
If this is accepted as a new branch, we propose "3 stars" to go along with the tradition of naming speedrun categories after star count. But it might be better to add in or replace it with "no tunneling".
Gameplay must be accurate to hardware If a game is not emulated well at all, it may not be accepted until it's emulated without significant glitches. For the purposes of Movie Rules we define significant glitches as audio, video, and/or gameplay-affecting glitches apparent to people unfamiliar with the game.