![]() ![]() It looks weird, and it costs a few seconds each picture, and it would be really great to fix this. However, the photo stays on screen for too long before transitioning to the fairy cutscene. Some emulators this doesn't work on the one I use it does. (6) Proper photos - When the camera is used to capture a fairy, a photo will appear on screen for a few seconds to show what you just took a picture of. A fun test of this is to watch the intro demo - if it desynchs and DK falls into the water, it is probably because lag isn't emulated correctly. It is certainly good enough to do a TAS, although any improvements here would be welcome. The emulator I use is pretty good, but not perfect about this. (5) Accurate lag emulation - Lag is SUPER IMPORTANT in DK64 and serves as the basis for how many tricks work. This is supposedly related to graphical spiking. It turns out this isn't important for any%, but it would be a nice fix for, say, a low optimization tool assisted demonstration (LOTAD) of 101%. The version of Bizhawk I use seems much better about this than, say, project64, (especially with regard to random grab boosts) but there are still several places where I need to go out of my way to avoid mysterious teleports while climbing trees. However, on emulator, sometimes this will happen randomly with no prompting. (4) Fixed random tree warping / telegrab - There is a glitch in the game where after a technique called tag barrel storage, if you grab a tree or climb a ledge you can teleport to another location. Apparently some emulators are better than Bizhawk in this regard, but I have't verified this myself. If graphical spiking was just one or two frames every 30 seconds that would be acceptable, but in a lot of areas there are more spiked frames than unspiked frames. It invites the viewer to question the validity of the run and distracts the knowledgeable viewer from what is going on. This isn't an absolutely essential fix, but it is extremely distracting sometimes, especially with Tiny. (3) Fixed graphical spiking - This doesn't have to be 100% fixed, but with the version of Bizhawk I use it can get really bad in certain areas ( for example ). Not all emulators do though, but this is absolutely essential to basically any route in this game. (2) Proper saving - The version of Bizhawk I have has this and maybe some of the newer main versions do too. Here are features that I think an emulator needs to have: #Awesomemusic donkeykong fullI currently use a modified version of BizHawk made by Cronikeys for my YouTube channel, but I've been delaying working on a full game TAS until emulation some day improves. There is no emulator that can currently do everything needed to make what I consider an acceptable TAS of the game. On a scale from 1 - 10 the game's accuracy is at like a 6 for bizhawk (7 for my branch of mupen-rr) and my goal is to get that closer to an 8 before a TAS is started. TLDR: The full route of DK64 is tasable now (now as in right now). The solutions to a few of these have already been found, so they just need to be rolled into Bizhawk. That route is completable now, but I insist to anyone reading that you hold off on optimizing any TAS until I fix some of the physics issues (vines/trees teleporting you out of bounds, improper lag emulation, and intro/cutscene demos desyncing). He has more experience with the game so he'll be a better judge of accuracy than me for specific tricks.ĪFAIK Ringrush will be doing an Any% run for tasvideos without prior sram. ![]() Mupen64plus has updated since it branched into Bizhawk (in lay terms, Bizhawk is using an old n64 emulator "core") so I'll eitherĪ) be updating Bizhawk to latest M64P (more complicated than it sounds), orĢ) legitimizing the "Bizhawk" branch of M64P and fixing issues parallel to the m64p teamĪlso, Isotarge (realtime runner) is working with me on the emulator. My next plan is to tackle physics issues. A couple hours ago I fixed saving in Bizhawk for DK64 (it was a minor fix), so full-route 'theory runs' are doable now. I've been working on the emulator again for the BK crew (hyperresonance) and thought I'd kill two birds with one stone by addressing some of the DK64 issues. I am planning a few short, unoptimized demonstrations of some routes and tricks that a full TAS would use, so maybe expect those in the next few weeks. In an unrelated note, I do have an emulator that runs the game reasonably well and has TAS tools (although lacks reset recording and thus cannot do a full game run). variety of emulator issues (most notably no version emulates lag properly and has reset recording). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |