Pasky13: Actually it appears that the spin-slash just always goes off the swing animation hit box for the level 1 boss, and probably works similarly for other enemies with variable boxes. Interesting. You're probably right about the level 3 boss, or could it just be a bug? His effective hit box when jumping always seemed pretty much the size and shape of the crouching hit box that your script shows. The only other issue I've noticed is with the mind control orb on the 6-4 boss: slashes well outside the script-displayed box do damage. That said, thank you for making this, it's been lovely to see so many things visualized like this. About the background visualization script: I didn't mean to sound like I was asking you to make it for me. I know you only bothered with this because mikwuyma on SDA asked you. But if you could say a little about how you knew where to find those arrays in the ROM, or how you got to "etype = 0x0438" (I had those addresses tagged as something vague and TAS-irrelevant myself, and had assumed that 0x0400-0x0407 would be the important ones for something like this) I would greatly appreciate it. feos: I have indeed watched your WIP, though I haven't analyzed it too closely. Providing some input on it (and finishing the game resource page I started) have been nagging at me for a while now, but I just haven't made the time for it. Do you have a more recent WIP now?
$E144:BC 38 04 LDY $0438,X @ $043F = #$1E A:00 X:07 Y:30 S:F7 P:NvUbdIzc ; Load Enemy type
$E147:A9 01 LDA #$01 A:00 X:07 Y:1E S:F7 P:nvUbdIzc
$E149:85 94 STA $0094 = #$01 A:01 X:07 Y:1E S:F7 P:nvUbdIzc
$E14B:38 SEC A:01 X:07 Y:1E S:F7 P:nvUbdIzc
$E14C:BD 60 04 LDA $0460,X @ $0467 = #$89 A:01 X:07 Y:1E S:F7 P:nvUbdIzC ; Load enemies X
$E14F:E5 86 SBC $0086 = #$80 A:89 X:07 Y:1E S:F7 P:NvUbdIzC ; Subtract Ryu's X
$E151:10 07 BPL $E15A A:09 X:07 Y:1E S:F7 P:nvUbdIzC ; Branch on Plus (taken)
$E15A:D9 00 B3 CMP $B300,Y @ $B31E = #$0A A:09 X:07 Y:1E S:F7 P:nvUbdIzC ; Enemy X Radius (B400 Y Radius base) (Y register = enemy offset) ($B300 is a bankswitched portion of the rom that is located at 3310 inside the games ROM)
$E15D:10 0C BPL $E16B A:09 X:07 Y:1E S:F7 P:NvUbdIzc
$E15F:38 SEC A:09 X:07 Y:1E S:F7 P:NvUbdIzc
$E160:A5 8A LDA $008A = #$A0 A:09 X:07 Y:1E S:F7 P:NvUbdIzC ; Load Ryu's Y
$E162:FD 80 04 SBC $0480,X @ $0487 = #$A0 A:A0 X:07 Y:1E S:F7 P:NvUbdIzC ; Subtract enemies Y
$E165:30 05 BMI $E16C A:00 X:07 Y:1E S:F7 P:nvUbdIZC ; Branch on Minus
$E167:C5 90 CMP $0090 = #$19 A:00 X:07 Y:1E S:F7 P:nvUbdIZC ; compare against Ryu's Y radiusI've also noticed that some enemies that have multiple box types, like the guys on stage one whose box will change when they have their weapon over their head, that area can't be hit with the sword. Not sure how the game determines you can hit them since only one box type is loaded at a time (the etype, which usually shifts between 3 values per enemy)
Oh I didn't take it as you requesting for me to do, I was just humbling replying I don't really have the time or interest to look at it. But ya, the boxes were a request from Sinister1 actually, who has been bugging me about it for a couple months haha. As far as how I got the etype address, I got it by finding ryu's X,Y and a bosses X,Y and getting hit and setting a breakpoint when ryu got hit and tracing up until the breakpoint:$E144:BC 38 04 LDY $0438,X @ $043F = #$1E A:00 X:07 Y:30 S:F7 P:NvUbdIzc ; Load Enemy type $E147:A9 01 LDA #$01 A:00 X:07 Y:1E S:F7 P:nvUbdIzc $E149:85 94 STA $0094 = #$01 A:01 X:07 Y:1E S:F7 P:nvUbdIzc $E14B:38 SEC A:01 X:07 Y:1E S:F7 P:nvUbdIzc $E14C:BD 60 04 LDA $0460,X @ $0467 = #$89 A:01 X:07 Y:1E S:F7 P:nvUbdIzC ; Load enemies X $E14F:E5 86 SBC $0086 = #$80 A:89 X:07 Y:1E S:F7 P:NvUbdIzC ; Subtract Ryu's X $E151:10 07 BPL $E15A A:09 X:07 Y:1E S:F7 P:nvUbdIzC ; Branch on Plus (taken) $E15A:D9 00 B3 CMP $B300,Y @ $B31E = #$0A A:09 X:07 Y:1E S:F7 P:nvUbdIzC ; Enemy X Radius (B400 Y Radius base) (Y register = enemy offset) ($B300 is a bankswitched portion of the rom that is located at 3310 inside the games ROM) $E15D:10 0C BPL $E16B A:09 X:07 Y:1E S:F7 P:NvUbdIzc $E15F:38 SEC A:09 X:07 Y:1E S:F7 P:NvUbdIzc $E160:A5 8A LDA $008A = #$A0 A:09 X:07 Y:1E S:F7 P:NvUbdIzC ; Load Ryu's Y $E162:FD 80 04 SBC $0480,X @ $0487 = #$A0 A:A0 X:07 Y:1E S:F7 P:NvUbdIzC ; Subtract enemies Y $E165:30 05 BMI $E16C A:00 X:07 Y:1E S:F7 P:nvUbdIZC ; Branch on Minus $E167:C5 90 CMP $0090 = #$19 A:00 X:07 Y:1E S:F7 P:nvUbdIZC ; compare against Ryu's Y radius
Adelikat is looking into it at the moment and should be fixed.
https://code.google.com/p/bizhawk/source/browse/trunk/BizHawk.MultiClient/output/Lua/NinjaGaiden_Hitbox.luaThe playfield as I recall uses a sliding window. As the camera moves this window is updated with physics information. This information is at $0300 in memory. It is $C0 in size. Blocks are 16x32. However they are actually 16x16, but the high/low nibble of each byte is related to the top or bottom half of the block. So represented should be a 512x192 area. Not unlike the NameTable/Background layer. The values (remember that each nibble is a block) for blocks are: 0 = Void 1 = Climb while facing left 2 = Climb while facing right 3 = Climb facing either direction 4 = Stand Ontop/Platform 5 = Solid Block when moving to the Right, Void when moving to the left. You can stand ontop of it and you can climb on it when facing right. 6 = Solid Block completely and Climbable from either side. 7 = Stand Ontop/Platform 8 = Solid Block 9 = Ladder Climb when facing right A = Glitch B = Glitch C = Crash/Reset D = Ladder Area Change (Forward) E = Ladder Area Change (Backward) F = Next Sub-Act, Fade Out and In.
With it you can see how annoyingly prevalent 8's are mid-platform in 2-2 (Ryu loses 1 frame of forward movement when landing on anything that isn't a 7), how an 8 or 0 right of a 9 lets Ryu grab a phantom wall section for 1 frame, or how in a few spots the game will load some an F or two tantalizingly just off-screen. Beyond that, I don't see much TAS-relevant use for this for now. Pasky13: Bizhawk 1.0.5 doesn't seem to like your bitwise stuff: "lua:29: attempt to index global 'bit' (a nil value)." Guessing I'd need an interim build for that.Language: lualocal function viewbg() local addr = 0x0300 local x=0;y=8 for i = 1, 32 do for i = 1, 6 do hi = SHIFT(memory.readbyte(addr),4) lo = AND(memory.readbyte(addr),0xf) if hi == 0 then gui.text(x,y," "); y=y+8 else gui.text(x,y,string.format("%X",hi)); y=y+8; end if lo == 0 then gui.text(x,y," "); y=y+8 else gui.text(x,y,string.format("%X",lo)); y=y+8; end addr=addr+1 end x=x+6;y=8 end end emu.frameadvance() gui.register(viewbg)
Pasky13: Bizhawk 1.0.5 doesn't seem to like your bitwise stuff: "lua:29: attempt to index global 'bit' (a nil value)." Guessing I'd need an interim build for that.
Hi, marx. I have watched you wip, there are 2 problems. 1. you used the wrong rom. Your rom is Ninja Gaiden (U) [b1].nes. U should use the rom like this: Ninja Gaiden (U) [!].nes. [!] means perfect dump. The rule said the rom must be good. 2. what's wrong with this? |2|R.......|........|| In your fm2 file's line 2871. The flag 2 means reset the game. Is it a bug in fceux?
if I was to have a Tool-Assisted real life ... I'd.. I could abuse death, just to see if it saves time ..
if I was to have a Tool-Assisted real life ... I'd.. I could abuse death, just to see if it saves time ..
Hey scumtron. Will you quit tasing after you submit this tas?.
What are your future project(you seem to tas ng games only)
if I was to have a Tool-Assisted real life ... I'd.. I could abuse death, just to see if it saves time ..
I would like to see you TASing other games too.
if I was to have a Tool-Assisted real life ... I'd.. I could abuse death, just to see if it saves time ..
http://dehacked.2y.net/microstorage.php/info/1651353856/NinjaGaidenPacifist-3Levels.fm2 Please point out my mistakes. I'll revisit the second level anyway. Can green-grey witches be manipulated? EDIT: updated the movie, as I completed one more stage.
I'm still holding out hope that this glitch will have some time-saving application, so I've spent some time trying to better understand it Demonstration .fm2
if I was to have a Tool-Assisted real life ... I'd.. I could abuse death, just to see if it saves time ..
Will you continue? I saved 3 more frames up to the middle of your 1-1, but 2 frames were lost due to tysons difference at 1430 and then I was too far forward, so a wall double-jump at 1735 landed me right on the warrior, while doing that jump a frame later caused me to fall off the roof in the first place. I use to give up once I get such crap, but it will be pointless if you stop it too. You don't have to save trap floor frames in 1-1.
Okay, then, when I am in mood I will resume test run, try improving it and post here. I would use this scheme anyway, because it's better to do the whole test, then totally redo, than trying to make each level optimized instantly. Marx seems more interested in a no-damage pacifist.
if I was to have a Tool-Assisted real life ... I'd.. I could abuse death, just to see if it saves time ..
