Posts for FractalFusion

1 2
130 131
Posted: 2 days ago
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
By the way, I noticed in the input that the TAS starts with the code Right-A-Down-B-Left-A-Up-B was used at the beginning of the TAS to speed up the ball by 50%. I guess in-game codes are allowed now? (Also, what does "warpless" even mean?) Interesting that this game has "Left" and "Right" choices for the levels. Also the powerups break the game, as you can see in this TAS. Similarly to before, I made a 1080p60 encode with paddle controller input display: Link to video
Posted: 7 days ago
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Finally there is a TAS of Pokemon Black/White submitted to this site. (If you recall, Kaphotics made a TAS of Pokemon White in about 3h19m, almost 13 years ago, but refused to submit the TAS to this site.) Thanks for the submission info. I like the tricks in this run. Also, the RNG having such a complicated seeding algorithm is weird, but we're talking Game Freak here. I resent the fact that the game just has to throw evil team grunts at you over and over, and that's even with 6 of their "mandatory" battles skipped using dust clouds.
Posted: 14 days ago
(Edited: 14 days ago)
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
By the way, if you're wondering how I made the input display part of the encode (the left sidebar with the line-art paddle controller graphic), I generated the input display with a Lua script in BizHawk: 
local joystick_posy=550
local fire_posy=300

local controller={}

gui.clearGraphics("emucore")
gui.clearGraphics("client")
gui.use_surface("client")

function circlebyradius(cx, cy, radius, col1, col2)
	gui.drawEllipse(cx-radius, cy-radius, 2*radius, 2*radius, col1, col2)
end

gui.drawBox(0,0,256,224,0xFF000000,0xFF000000,"emucore")

while true do
	console.clear()
	gui.drawBox(0,0,256,700, nil, 0xFF000040)
	gui.drawBox(20,220,256-20,700-20)
	gui.drawLine(123,220,123,0)
	gui.drawLine(133,220,133,0)
	circlebyradius(128,joystick_posy,80, nil, 0xFF000060)
	
	local prev_value=controller.Paddle
	local prev_fire=controller.Fire
	if not prev_value then
		prev_value=80
		prev_fire=nil
	end
	controller=joypad.getwithmovie(1)
	
	local pangle=(math.pi/180 * (180.5+(prev_value-80)*160/80))
	local angle=(math.pi/180 * (180.5+(controller.Paddle-80)*160/80))
	
	gui.drawLine(128,joystick_posy,128-80*math.sin(pangle),joystick_posy+80*math.cos(pangle), 0x40FFFFFF)
	gui.drawLine(128,joystick_posy,128-80*math.sin(angle),joystick_posy+80*math.cos(angle))
	gui.drawBox(127,joystick_posy+3,129,joystick_posy+77,0x8000FF00,0x8000FF00)	
	if controller.Fire then
		circlebyradius(128,fire_posy,30, 0xFFFF0000, 0xFFFF0000)
	elseif prev_fire then
		circlebyradius(128,fire_posy,30, 0xFFFF0000, 0x70FF0000)
	else
		circlebyradius(128,fire_posy,30, 0xFFFF0000, 0x20FF0000)
	end
	
	emu.frameadvance()
end
Then (separately from a normal encode of the TAS) record AVI with the options "Capture OSD" and "Capture Lua" enabled and do some editing with something like AviSynth. I didn't explore all the Lua gui options so there might be a better way to set this up.
Posted: 14 days ago
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Submission Text wrote:
todo
no need, the video explains itself
Posted: 14 days ago
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
I like how the Arkanoid paddle controller actually improves the TAS. 1080p60 encode, with input display: Link to video I recommend viewing at 720p60 or above, since the "entertainment" effects don't show up on 30-fps settings.
Posted: 12/20/2024 7:42 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Hm, I've never tried buster-only before. Just note that if you have trouble with the RNG, you can use this Lua script: https://tasvideos.org/UserFiles/Info/638585240848962683 (change "local game=7" to "local game=1"). Other notes: * In general, wall dragging can be used for RNG manipulation. * If you need to manipulate Storm Eagle, you can wall drag along the right side of the platform. * Bospider: I found a file I made 10 years ago, if it helps: https://www.mediafire.com/file/r74xxonx492n4uc/bospider2.txt/file . Note that 0-crossing RNG values are rare. (Bospider is awful but you'll have to deal with it.)
Posted: 12/20/2024 7:15 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Thornstrom wrote:
Yes, one can edit it in post. But then it has to be re-encoded which means some quality loss, so it would be better to be able to remove it when it's generated.
As a regular AviSynth user, I generally only use lossless codecs prior to the final encoding run, so that there is no quality loss during editing. This is just a side note.
Posted: 10/26/2024 1:26 AM
(Edited: 10/26/2024 1:30 AM)
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
OmnipotentEntity wrote:
For this second one, find all solutions in the Reals, prove you have all of them.
Nice that this is a Diophantine problem in disguise. Since |cos(anything)|≤1 and |1/sin(anything)|≥1, the equality can only possibly be true if cos(88*pi2/x) = ±1 and sin(3x) = ±1. sin(3x) = ±1 when 3x = pi/2 + pi*n, or in other words, x = (1+2n)*pi/6. Note that sin(3x) = +1 when n is even, and -1 when n is odd. cos(88*pi2/x) = ±1 when 88*pi2/x = pi*m, or in other words, x = 88*pi/m. Note that cos(88*pi2/x) = +1 when m is even, and -1 when m is odd. So x is a solution if and only if x is both of the form 88*pi/m and of the form (1+2n)*pi/6, where m and n are either both even or both odd. So we have: 88*pi/m = (1+2n)*pi/6 88*6 = m*(1+2n) m*(1+2n) = 11*3*24 Since 1+2n is always odd, it follows that m is a multiple of 24, and so m and n are both even. Then 1+2n must be a divisor of 33 (positive or negative) that is 1 mod 4, and now we can list the possibilities for 1+2n: 1+2n = 33: n=16 and m=16, x=11*pi/2 1+2n = 11: no, not 1 mod 4 1+2n = 3: no, not 1 mod 4 1+2n = 1: n=0 and m=88*6, x=pi/6 1+2n = -1: no, not 1 mod 4 1+2n = -3: n=-2 and m=-88*2, x=-pi/2 1+2n = -11: n=-6 and m=-48, x=-11*pi/6 1+2n = -33: no, not 1 mod 4 So there are exactly four solutions for x: x=11*pi/2, x=pi/6, x=-pi/2, x=-11*pi/6.
Posted: 10/24/2024 7:03 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
OmnipotentEntity wrote:
Instead of solving explicitly for x, it's easier to square x + 1/x to get x^2 + 1/x^2 + 2 = 293. Notice that the goal formula reduces to x - 1/x, and if you square that you get x^2 + 1/x^2 - 2, which is 293 - 4 = 289 from our above formula. Then just take the square root of 289 = 17.
I did eventually get to answer=17 through some algebraic manipulation of my own, but this method works as well. Although I was thinking of why OmnipotentEntity had the multiple choice in the first place. I mean, I was very tempted to go with the following "solution": With some algebraic manipulation similar to before, logba + logab = sqrt(293) and the goal is to find logba - logab. But a>b>1, so logab is clearly between 0 and 1. That means the answer is between sqrt(293)-2 and sqrt(293), and the only number in the multiple choice list that fits is 17. Therefore the answer is 17.
Posted: 10/19/2024 9:47 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Comparison encode (1080p60) with previous publication: Link to video
Posted: 10/6/2024 9:39 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Link to video Sorry for the low-effort encode. I also threw in video of the previous version just for comparison purposes.
Posted: 10/5/2024 6:24 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Are there any plans to make a glitched version? That might be interesting.
Posted: 9/30/2024 7:31 PM
(Edited: 9/30/2024 7:47 PM)
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
MUGG wrote:
I noticed the lua console said "Message Cap reached, suppressing output" because of a long string that was outputted.
From my experience, that can definitely happen if you do too many console.write operations without emu.frameadvance(). The Lua console is not a good way of holding output long-term. Try output to file, something like: 
local f = io.open("results.txt","a")
    f:write( ... )
f:close()
(replace "..." with whatever string you want to output) Edit: The error happens if you use console.write 100 or more times in a row. You can make your output string first (use ".." (two dots) to concatenate the strings all together), then at the end use console.write on that string. Of course, if you are storing output that you want to view long-term, better to output to file as shown above.
Posted: 9/30/2024 5:29 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Samsara (from News feed) wrote:
It took until last month, two and a half years after Playground was drafted, for us to show those runs on game pages. We completely dropped the ball on it. Part of that I think was due to lack of interest across... Everyone on the site, really.
Considering that the news post this quote is from is the first and so far only news post to mention "Playground" at all... I wasn't even sure whether "Playground" was supposed to be taken seriously. It just came across as no one having any idea of what it was ultimately supposed to be.
Posted: 9/17/2024 6:51 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
McBobX wrote:
I think FractalFusion wasn't talking from a judgement perspective, it is just something I noticed as well, because yeah I do agree with the fact that MMX4-6 games don't have that long "Now Loading" for it to be accelerated. That said, I appreciated HappyLee's care about viewer pleasure, it is very nice!
Just to confirm, I wasn't talking from a judging perspective. I don't talk from judging perspectives anymore. It's fine, I have used speed edits in my encodes before. Just pointing out that most games don't really need speed edits; when watching TASes, viewers can normally skip over video as they so choose. I have done speed edits in my own encodes, but only very rarely (it does take a lot of work which I usually don't see as necessary) and only for one of two reasons: * The upload site has a restriction on video length (doesn't apply anymore), or * The TAS is exceptionally boring. (Fortunately, the vast majority of TASes don't fall in this category.) Also personally, if it's just a matter of loading screens, I'd prefer removing them all together over speeding them up.
Posted: 9/16/2024 8:45 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
I didn't know you could win by slipping on a banana peel. This TAS is funny. Did you know Mario can also beat SM64* stages just by slipping on a banana peel? See, look: Link to video
Posted: 9/16/2024 8:26 AM
(Edited: 9/16/2024 8:30 AM)
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
I don't think Mega Man X4 is the type of game that deserves "10x" speed edit on loading screens in an encode, but whatever.
Posted: 8/20/2024 1:59 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Interesting. Didn't know there was a thread from 18 years ago, and a working link to bsgen.zip (thanks Mr. Pwnage, if you are still on this site). Anyway, here's what I know so far: This site and this online generator have some more details about how the level generation works. There is also a detailed pastebin about the password-to-level algorithm. Note that each level has two possible passwords: a normal "Sonic 1 cart" code which auto-advances when you beat a level, and a "non-Sonic 1 cart" code which doesn't (associated with passwords you get from locking onto other carts). I have recently made a BizHawk 2.9.1 Lua script with functions that can do this conversion (password to level, level to password Sonic 1 and non-Sonic 1, level to stage and stage to level): https://tasvideos.org/UserFiles/Info/638595168763566191 ---- Possible goals that might be interesting (in case anyone wants to make a TAS in the future): * All symmetrical levels (124 levels long). Note this playthrough by Digital Duck. Note that symmetrical #125, #126, #127 is impossible. * Each of the 128 quadrants shows up at least once in some map (32 levels long). * Same as above, but no passwords (unknown number of levels required, maybe 70-80?)
Posted: 8/19/2024 10:24 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Nice TAS. I think this game has too many forced Team Plasma Grunt battles though.
Posted: 8/19/2024 10:12 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
GJTASer2018 wrote:
Assuming that the level order is not randomized, starting at the same starting point (i.e. power on of the locked on S&K + Sonic 1 cart) and playing until you reach a MAX level for the first time would be the better way to approach this goal ... it would be much more likely to be accepted and published
Nope, disagree here. It has no chance of being accepted. To be fair, the goal choice "Perfect MAX" is the real problem, as it can easily be argued that the game does not consider "Perfect MAX" to be completion (the game continues just as if you got some other "Perfect non-MAX", or "non-Perfect"), and doing a 20-minute TAS for the sole purpose of getting to the "Perfect MAX" scene doesn't really solve this problem.
DigitalDuck wrote:
For a goal choice somewhere between 20 seconds and a century, I did all symmetrical levels a couple of years back; playing through all 125 levels which use the same chunk in each quadrant (one of which is the level shown in this run). There are 128 chunks, but because of the way the levels are assigned there are no levels that are entirely made up of chunk #125, #126, or #127. This was the closest to a "100%" run I could come up with that doesn't have a runtime of several human lifespans.
Actually, I saw and then forgot about that Youtube video for some reason. "All symmetrical levels" sounds interesting as a concept even if it takes a couple hours (too bad about the missing #125, #126 and #127). Perhaps not restricting to symmetrical levels but allowing for each of the 128 quadrants to show up at least once might be interesting too; would be about 1/4 of the time (32 levels) and allow inclusion of #125 to #127. And of course the non-password version of this goal might be interesting too, though I can't tell off the top of my head what the optimal level route would be in this case. Maybe requires 70 to 80 levels? Probably these all sound better as a goal choice. Also, I didn't realize "procedural generation" was an actual term. Something new I learned.
Posted: 8/13/2024 9:18 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
I thought of Reading instead of Boardwalk, but the problem is the game has a 2-second delay whenever anyone lands on a railroad space. Otherwise I would have sent Ollie to Reading instead.
Posted: 8/13/2024 3:30 AM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Darkman425 wrote:
While normally regional choice isn't usually counted for/against TASes that otherwise have the same content, the way that Rush Search RNG frames are determined are by frame count. Due to the Rush Search cutscene glitches that can help speed up the game ...
Here's something interesting. The choice of region may even affect whether to do a particular Rush Search glitch or not. For example, the use of Rush Search before the Proto Man room is used to skip the cutscene of Proto Man talking before he attacks. On the Japanese version, this cutscene is much shorter, and it may even be faster to take the cutscene rather than use Rush Search to skip it!
Posted: 8/7/2024 8:17 PM
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
Oh? This doesn't obsolete the 4 CPU's run? Whatever. I saw at one point a post asking why it was not feasible to extend the 4 CPU strategy to 7 CPUs, but I'm not sure where the post went. The reason is that, after end of input, you'd need to manipulate 7*2 = 14 rolls, instead of 8. Considering that each odd roll has to be a double and each even roll has to be 2 or 3 (let's forget about back 3 spaces for now), extending it to 14 rolls would make it (1/6 * 1/12)^3 = 1 / 373248 as likely to occur compared to the 4 CPU strategy, and the 4 CPU strategy already has a (1/6 * 1/12)^4 = 1/26873856 chance of occurring. The back 3 space card made it approximately 3 times more likely. For reference, the estimated size of the search space used in the 4 CPU strategy was around 40000*256 = 10240000.
Posted: 8/6/2024 7:37 AM
(Edited: 8/6/2024 7:38 AM)
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
In case anyone will improve it in a future submission with better luck-manipulation (and other stuff), I'll leave some additional stuff here: * It might be possible to shave a frame or so from the intro stage Bass fight by ending with a charged shot. Very minor though. * In Freeze Man's stage, before entering the room with the H letter, it is actually faster to stand on the ice platform until it starts to break, so that when you exit the H letter room, you can drop directly down to the ladder below since the ice platform isn't there anymore. It can be seen in the following MM7 100% speedrun: https://www.speedrun.com/mm7/runs/m799kkey . * In order not to forget things like RNG addresses (which I forget easily since I apparently did not document this on a fixed page anywhere), I have created a very basic Lua script that monitors RNG in any Mega Man game that uses "MMX RNG", including MMX-X6, MM7 and R&F. You can download the script here: https://tasvideos.org/UserFiles/Info/638585240848962683 . Although this script does not display everything related to Rush Search, it should be useful for getting the RNG value to line up, especially the "R-2F" value displayed there as well. * In the MM7 thread, I added a few other things about MM7 and how Rush Search works (at least so I don't forget in the future). For more information, see https://tasvideos.org/Forum/Topics/257?CurrentPage=8&Highlight=530802#530802
Posted: 8/6/2024 7:35 AM
(Edited: 8/6/2024 5:29 PM)
Quote
FractalFusion
Editor, Experienced Forum User, Published Author, Expert player (2083)
Joined: 6/15/2005
Posts: 3289
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
In order not to forget things like RNG addresses (which I forget easily since I apparently did not document this on a fixed page anywhere), I have created a very basic Lua script that monitors RNG in any Mega Man game that uses "MMX RNG", including MMX-X6, MM7 and R&F. You can download the script here: https://tasvideos.org/UserFiles/Info/638585240848962683 . Although this script does not display everything related to Rush Search, it should be useful for getting the RNG value to line up, especially the "R-2F" value displayed there as well. * I'll add a few other things about MM7 and how Rush Search works (at least so I don't forget in the future). The RNG address is at 0xFA. The RNG subroutine in ROM is at 0xC1023D. There are two calls to RNG per frame which are not used (at ROM addresses 0xC00CD2 and 0xC10CB4). They occur before other RNG calls. When Rush Search is summoned, just before the tail wag animation, there is a call to the RNG at 0xC14B85: 
c14b85:  jsl  $c1023d   [c1023d]   A:6280 X:0074 Y:0002 S:012e D:0c80 DB:80 NvMXdizc V:260 H:210
...
c14b89:  and  #$03                 A:754e X:0074 Y:0002 S:012e D:0c80 DB:80 NvMXdizc V:260 H:305
c14b8b:  clc                       A:7502 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdizc V:260 H:308
c14b8c:  adc  #$03                 A:7502 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdizc V:260 H:311
c14b8e:  sta  $3a       [000cba]   A:7505 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdizc V:260 H:314
c14b90:  rts                       A:7505 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdizc V:260 H:320
This call takes the RNG value mod 4, and adds 3 to it, to get the number of Rush tail wags (from 3 to 6). Then after the tail wag animation has finished, the next frame gives two more RNG calls. One is for the item obtained: 
c14d38:  jsl  $c1023d   [c1023d]   A:ffff X:0003 Y:001e S:012c D:0c80 DB:80 NvMXdizc V:254 H:152
...
c14d3c:  cmp  #$ff                 A:5d65 X:0003 Y:001e S:012c D:0c80 DB:80 NvMXdizc V:254 H:246
c14d3e:  bne  $4d41     [c14d41]   A:5d65 X:0003 Y:001e S:012c D:0c80 DB:80 nvMXdizc V:254 H:249
c14d41:  ldx  #$00                 A:5d65 X:0003 Y:001e S:012c D:0c80 DB:80 nvMXdizc V:254 H:254
c14d43:  cmp  $a3e2,x   [80a3e2]   A:5d65 X:0000 Y:001e S:012c D:0c80 DB:80 nvMXdiZc V:254 H:257
c14d46:  bcc  $4d4b     [c14d4b]   A:5d65 X:0000 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:263
c14d48:  inx                       A:5d65 X:0000 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:266
c14d49:  bra  $4d43     [c14d43]   A:5d65 X:0001 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:269
c14d43:  cmp  $a3e2,x   [80a3e3]   A:5d65 X:0001 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:273
c14d46:  bcc  $4d4b     [c14d4b]   A:5d65 X:0001 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:279
c14d48:  inx                       A:5d65 X:0001 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:282
c14d49:  bra  $4d43     [c14d43]   A:5d65 X:0002 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:254 H:285
...
c14d43:  cmp  $a3e2,x   [80a3e8]   A:5d65 X:0006 Y:001e S:012c D:0c80 DB:80 nvMXdizC V:255 H: 15
c14d46:  bcc  $4d4b     [c14d4b]   A:5d65 X:0006 Y:001e S:012c D:0c80 DB:80 NvMXdizc V:255 H: 21
c14d4b:  stx  $3b       [000cbb]   A:5d65 X:0006 Y:001e S:012c D:0c80 DB:80 NvMXdizc V:255 H: 25
c14d4d:  rts                       A:5d65 X:0006 Y:001e S:012c D:0c80 DB:80 NvMXdizc V:255 H: 32
c14ba4:  ldx  $3b       [000cbb]   A:5d65 X:0006 Y:001e S:012e D:0c80 DB:80 NvMXdizc V:255 H: 42
c14ba6:  lda  $a3fc,x   [80a402]   A:5d65 X:0006 Y:001e S:012e D:0c80 DB:80 nvMXdizc V:255 H: 48
c14ba9:  and  #$bf                 A:5d84 X:0006 Y:001e S:012e D:0c80 DB:80 NvMXdizc V:255 H: 56
c14bab:  sta  $3d       [000cbd]   A:5d84 X:0006 Y:001e S:012e D:0c80 DB:80 NvMXdizc V:255 H: 59
The above code compares (RNG value mod 256) by going through a table to determine the item. The following site gives the resulting probabilities: https://www.thesupersnes.tv/compendium/mm7/rush-search/ . In particular, small life energy needs a value of 0x00 to 0x17, large life energy 0x18-0x1F, small weapon energy 0x20-0x37 and large weapon energy 0x38-0x3F. Finally, the other RNG call is for how many times to repeat Rush's dig animation: 
c14bba:  jsl  $c1023d   [c1023d]   A:6180 X:0074 Y:0002 S:012e D:0c80 DB:80 NvMXdizc V:255 H:299
...
c14bbe:  and  #$03                 A:2f38 X:0074 Y:0002 S:012e D:0c80 DB:80 NvMXdizc V:256 H: 53
c14bc0:  clc                       A:2f00 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdiZc V:256 H: 56
c14bc1:  adc  $3d       [000cbd]   A:2f00 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdiZc V:256 H: 59
c14bc3:  and  #$7f                 A:2f84 X:0074 Y:0002 S:012e D:0c80 DB:80 NvMXdizc V:256 H: 65
c14bc5:  sta  $3a       [000cba]   A:2f04 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdizc V:256 H: 68
c14bc7:  rts                       A:2f04 X:0074 Y:0002 S:012e D:0c80 DB:80 nvMXdizc V:256 H: 75
Take RNG value mod 4, and add it to a fixed number depending on the item obtained to get the number of loops in the dig animation. For small life and weapon energy, add 2 (from 2 to 5). For large life and weapon energy, add 8 (from 8 to 11). Note on RAM addresses: 0xCBA = # of tail wags / digging loops, 0xCBB = X value of item obtained, from 0 to 25. (0 = small life energy, 1 = large life energy, 2 = small weapon energy, 3 = large weapon energy) 0xCBD = # of fixed dig loops to add to Rush's digging animation. If bit 7 is set, Rush does a second digging animation of 5 faster digs (only for certain items).
1 2
130 131