S2:AE update topic/ rika needs help topic

$14 is just an offset of a memory address. Changing $14 will change what will be increased by $40 :P

 

My bad then.... =P

 

Try setting $14(a1) as low as #3, and see if it has any effect. If not, I'll look into it a bit more. Been quite a while since I touched it.

 

I'll look into it in a clean disassembly for you and see what I can do. Steepness of the slope would effect it as well.

 

Are you completely sure? I thought you could duck in order to avoid the spikeballs thrown by one of Labyrinth's orbinauts...

EDIT: The orbinaut in question is in act 2, around coordinates 0BCC 05E2. Sonic can indeed use this height change to his advantage, althought the "look down" function makes it a bit awkward.

 

I think somewhere in Sonic's SST there is a value that tells what Sonic's hieght is. If you could figure that out, you could change it for when he ducks.

I dunno if that's the case though, as I've never tried this stuff. But it does seem reasonable to me.

 

Ok this is something I never usually do, but since it's you, I'll make an exception.

This is from my disassembly and is a small section from the start of Sonic's programming (0x19F50 in case you didn't know. I've edited the labels).

Code (Text):

1. ; ----------------------------------------------------------------------------
2. ; Sprite
3. ;
4. ; Sonic
5. ; ----------------------------------------------------------------------------
6.  
7. Sprite_Sonic:
8.         tst.w   ($FFFFFE08).w;Is debug mode being used?
9.         beq.s   Sonic_Load;If not, branch
10.         jmp loc_41A78   ;Debug Mode routine
11. ; ?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„
12.  
13. Sonic_Load:
14.         moveq   #0,d0
15.         move.b  $24(a0),d0
16.         move.w  Sonic_Index(pc,d0.w),d1
17.         jmp Sonic_Index(pc,d1.w)
18. ; ?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„
19. Sonic_Index:    dc.w loc_SonicMain-Sonic_Index; 0
20.         dc.w loc_SonicControl-Sonic_Index; 1
21.         dc.w loc_1B120-Sonic_Index; 2
22.         dc.w loc_1B1E6-Sonic_Index; 3
23.         dc.w loc_1B31C-Sonic_Index; 4
24.         dc.w loc_1B330-Sonic_Index; 5
25. ; ?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„?„
26.  
27. loc_SonicMain:; DATA XREF: h+2FF6o
28.         addq.b  #2,$24(a0);Move routine counter to D0
29.         move.b  #$13,$16(a0);Set Sonic's Height (real value / 2)           
30.         move.b  #9,$17(a0);Set Sonic's Width (real value / 2)
31.         move.l  #Map_Sonic3,4(a0);Mappings
32.         move.b  #2,$18(a0);Sprite Priority
33.         move.b  #$18,$19(a0);Set Sonic's Width (real value)
34.         move.b  #4,1(a0);Playfield Co-ordinate system
35.         move.w  #$600,($FFFFF760).w;Sonic's Top Speed
36.         move.w  #$C,($FFFFF762).w;Sonic's Acceleration
37.         move.w  #$80,($FFFFF764).w;Sonic's Deceleration

As you can see, Sonic's height is set in this routine. I looked in the ducking routine and couldn't find any height reference, so I'm assuming it uses this. I could be wrong though. All you should need to do is the following:

Code (Text):

1. loc_SonicMain:     
2.                 addq.b  #2,$24(a0);Move routine counter to D0
3.                 cmpi.b  #8,$1C(a0)              ;Is ducking animation being displayed?
4.                 bne.s   NormalHeight                ;If not, branch
5.  
6. DuckHeight:
7.                 move.b  #$11,$16(a0);Set Sonic's Height (real value / 2)
8.                 bra.s     HeightSet
9.  
10. NormalHeight:
11.         move.b  #$13,$16(a0);Set Sonic's Height (real value / 2)
12.  
13. HeightSet:     
14.         move.b  #9,$17(a0);Set Sonic's Width (real value / 2)

This may or may not work, so if not, let me know and I'll look into it a bit more for you.

 

Try replacing $11 with $D. If that doesn't work, I'll look into it a bit more.

 

I'll experiment with it a bit tonight and see what I come up with then. Can't be too difficult.

 

Sorry I've been so tied up with other things lately that I've only just got round to doing it.

Ok, I've looked into it and it turns out I got it backwards. Increase the value written to $14(a0) to speed up the slopes. I just put it as high as $140 to test and I flew down them. The oly thing is, this also makes it harder for you to get back up the slopes so you have to find a balance unless you recode it like I did for the grind rails.