Welcome to Smashboards, the world's largest Super Smash Brothers community! Over 250,000 Smash Bros. fans from around the world have come to discuss these great games in over 19 million posts!
You are currently viewing our boards as a visitor. Click here to sign up right now and start on your path in the Smash community!
That's actually what I meant in my post, lol. But yes the ability to be able to update all the pointers would be absolutely amazing. With that, in the near future we could add more information for what could be projectiles, animations, and more.
I have this already. It's actually not that complicated. It's part of how I made this.
def extendDataSpace( offset, diff ):
""" This function will expand the data area at the given offset, starting at the first argument. The second argument is the amount to increase by.
All pointers occurring after the sum of the two arguments will be recalculated. """
def replaceHex( hexData, offset, newHex ): # Input takes a string, int, and string, respectively.
offset = offset * 2 # Doubled to count by nibbles rather than bytes, since the data is just a string.
codeEndPoint = offset + len(newHex)
return hexData[:offset] + newHex + hexData[codeEndPoint:]
global datDataHeader, datData, rtData
if datDataHeader != '' and datData != '' and rtData != '':
# Update the file header with the new file size and start of the relocation table.
filesize = int( datDataHeader[:8], 16 )
newFilesize = filesize + diff
rtStart = int( datDataHeader[8:16], 16 ) # Size of the data block
newRtStart = rtStart + diff
datDataHeader = replaceHex( datDataHeader, 0, "{0:0{1}X}".format(newFilesize, 8) + "{0:0{1}X}".format(newRtStart, 8) )
# For each entry in the relocation table, update the address it points to, and the value of the pointer there, if they point to locations beyond the extended space.
entriesUpdated = 0
pointersUpdated = 0
for nib in xrange(0, len(rtData), 8):
rtEntryNum = (nib/8)
rtEntryAddress = rtStart + rtEntryNum * 4
rtEntryString = rtData[nib:nib+8]
rtEntryValue = int( rtEntryString, 16 ) # i.e. the pointer address
pointerString = datData[rtEntryValue*2:(rtEntryValue+4)*2] # Multipled by 2 because this is per character/nibble, not per byte.
pointerValue = int( pointerString, 16 )
# If the pointer appears after the change, update its address in the relocation table accordingly.
if rtEntryValue >= offset:
newRtEntryValue = rtEntryValue + diff
datData = replaceHex( datData, rtEntryAddress, "{0:0{1}X}".format(newRtEntryValue, 8) )
entriesUpdated += 1
# If the place that the pointer points to is after the space change, update its value accordingly.
if pointerValue >= offset:
newPointerValue = pointerValue + diff
datData = replaceHex( datData, rtEntryValue, "{0:0{1}X}".format(newPointerValue, 8) )
pointersUpdated += 1
# Fill the newly extended space with zeros. (Values doubled to count by nibbles rather than bytes, since the data is just a string.)
datData = datData[:offset*2] + '0'.zfill(diff*2) + datData[offset*2:]
#msg('RT Entries updated: ' + str(entriesUpdated) + '\nPointers updated: ' + str(pointersUpdated))And every single action state, stage, etc.?
Gamecube audio samples are 2 bytes per sample, with the Audio Interface reading 16 sound samples per 0.25ms, which is 8 stereo samples @ 32KHz. To mix samples, Parameter Blocks are needed, which work like so:
Command 02: PBAddr
->
this.pb
next.pb
volume
source
sample rate
LPF
mixer
adpcmAdventure Mode with co-op (and 3D movement, which is entirely possible)? Or are you talking about a follow-behind camera?
Adventure Mode co-op with 3D movement. Is it really possible?
Well, the game has a 3D depth and movement. Depth is only really used on stages that are offset from 0, like Great Bay, and specific moves (Brawl and Smash 4 have a number of moves that change your Z-Axis).
Lol well at least it's possible. Ima have to find it now!
A new camera mode to do this is possible too. I once made a camera mode that worked from the perspective of about where a character's eyes would be. That was... interesting. Lol
So like a fox/falco fps and link crossbow training? x)
No, like Holding up is 90, right is 0, left is 180, and down is 270. For every frame it is held add that number to a set of data. When gathering them is over get the average of these numbers.
Like up 2, left 1, right 3 would be 90, 90, 180, 0, 0, 0. The average of that is 60, so you can then translate that into the correct analog input. Would that be 64,200 something?
Seems overly complicated, given that it takes holding a single direction for the real value under normal circumstances. I mean, it wouldn't be hard to do, I guess. I just don't understand why you would want to do it.
64, 200? What? Analog Inputs are -1 to 1 on the X,Y axis, so I'm not sure what you mean here. Plus, in this situation, it'd be easier to just provide the angle from the input, like the game already does.
Yeah, I could do that right now. Or just stop them from spawning in the first place.
Could you give me a code that could do that? I kinda sorta changed some random values in tatahackpack somewhere a long time ago that make items crash sometimes a lot when you pick them up and I really do not want to do a full diff check of my start.dol and look through every difference.
Give me a few hours, and I'll see what I can do. I want to test the most efficient method, then I'll work from there if it doesn't work.
