- This topic has 1,129 replies, 26 voices, and was last updated 10 years, 12 months ago by
.
-
Posts
-
<embed src="https://www.box.com/embed/coqpalc92bmcl7p.swf" width="466" height="400" wmode="opaque" type="application/x-shockwave-flash" allowFullScreen="true" allowScriptAccess="always">
<embed src="https://www.box.com/embed/coqpalc92bmcl7p.swf" width="466" height="400" wmode="opaque" type="application/x-shockwave-flash" allowFullScreen="true" allowScriptAccess="always">
I updated the first post, but just in case you'd rather check here:
I'll add to that, colors pulled from the rom as well, especially w/ the changes we make to those now, everything isnt red/white blue/white green/brown pink/green anymore…
Problem w/ portrait selection is you cant mix and match portraits…. :crybaby:
I like the mock up though :) Now wheres my whip for Niahak…. FLEXX
This ROM seems to be breaking DoaEditor (Unknown Key errors)
https://www.box.com/s/88eabf399bd354140c80
What I did…
I manually added text to the end of text bank 03:
0x2C170:
80A1B4CEEA06213C506476B4F1011124
3746566E87A6E25960889EE2010B3053
0x2C370:
B7B7B7B7B7B8B8B8B8B8B8B8B8B9B9B9
B9B9B9B9B9B9B9BABABABABABBBBBBBB
0x2F790:
F0D99055F0E1A096CE3CF00A3433FBF0
4D2E2FAE46FDD0A266F0F2342DAE632E
ECF40AFBEE852EA0603237F0AA343D36
3463FDFFF40A37E0DE3334323BF0EB34
33A0603237F0AA343D363463FDFFF5A0
A33130333B680A663E643D333433FBF0
EB90A63364343B63FDFFF4A0A3313033
3B680A663E643D333433FBF0EB90A633
64343B63FDFFF50A37E0DE353B343390
A63364343BFBD0EB2F342D2D3E2D63FD
FFF40A37E0DE353B343390A63364343B
FBD0EB2F342D2D3E2D63FDFFF5A0A31A
181B1B1413B0EBA0A63364343B7AFDFF
F4A0A31A181B1B1413B0EBA0A6336434
3B7AFDFFF5A0A2F4A089D0EB323E3C31
F0F2CEB0FDFFF5612EB0F03DFBD0653B
3E2E2F0AFB32F0EC353833343D3234B0
EBB0B763FDF0A568A096333E64312F90
B33031383BF0EA68FBD0E83B343033EE
B0FDFFFBF4612EB0F03DFBD0653B3E2E
2F0AFB32F0EC353833343D3234B0EBB0
B763FDF0A568A096333E64312F90B330
31383BF0EA68FBD0E83B343033EEB0FD
FFF580A3653832F0E82D383E642E7AFD
FFF480A3653832F0E82D383E642E7AFD
FFF5612EB0F03DFB3630D0EB2E3F3434
337AFDFFF4612EB0F03DFB3630D0EB2E
3F3434337AFDFFF5612EFBF0F03D0A2D
F0AA687AFDFFF4612EFBF0F03D0A2DF0
AA687AFDFFFBF5A0A2F4A06531F0F22F
3B343390E8300A332D30667AFDFFF5A0
A2F48065313E2F37B0E6343D0A663E64
3D3334337AFDFF28342E62905DF0E180
80382DF0EC639097C0F0F0E636D0EBF0
I also added a bunch of code from 4010-4AFF in the ROM.
Niahak can you help us figure out what's going wrong?
Here's a way around the problem:
1. Open your ROM with DoaEditor and painful click through all the key errors.
2. Go to the text tab and go to the bottom.
3. Look for any text above and below the "Duel" text and fix it. In mine the one above the duel text had like a bazillion lines. Simply change it to say:
open slot[END]
4. Save your ROM with DoaEditor.
5. All better now.
I think what's happening is a pointer error of some kind.
It's trying to parse line 0x5f of bank 3, specifically a line that's 0xa39 bytes long starting at 0x2ed57.
Pointers 14c to 15f for the second pair of banks all have the same value, then there's suddenly a huge leap (that 0xa39 bytes).
In the actual ROM, it looks like that text is just an [END] (0xFF), but the text editor's trying to read the following bunch of bytes and it's choking on some of the contents.
If you look at the difference between the pointers at 0x2c16f and 0x2c170 with their corresponding companions at 0x2c36f and 0x2c370 (call them A: 0xAD47 and B: 0xB780) you can actually see exactly where that 0xa39 came from. It thinks there's a line at A of length 0xa39 – when the pointer for A is probably never actually referenced in code. Basically, you have a "dud" line that isn't being used, and DoaEditor is choking when it tries to parse it.
Right, but can DoaEditor just look at the pointers and end at the FF? I was trying to put my text out of the way of where the text bank might have expanded to.
Well… unfortunately, it's not that easy. Right now it keeps track of exactly how many bytes to read out, and doesn't automatically end a line at a 0xFF or other corresponding [END] tag (I'm not even sure what happens in-game if an [END] is midway through a line).
I could potentially prototype it… but I'll have to think about it. It seems better to make DoaEditor configurable in some way so it won't stomp all over any lines you add.
Actually – for that matter – why not just use one of those unused empty lines at the end of the bank? That way there's no dud, and you can edit the text in DoaEditor.
Quote:Well… unfortunately, it's not that easy. Right now it keeps track of exactly how many bytes to read out, and doesn't automatically end a line at a 0xFF or other corresponding [END] tag (I'm not even sure what happens in-game if an [END] is midway through a line).It ends. :) I believe a quote by Yuan Shu has two [END]'s even
Quote:Actually – for that matter – why not just use one of those unused empty lines at the end of the bank? That way there's no dud, and you can edit the text in DoaEditor.The reason I don't want to put my stuff right at the bottom of the text bank is because some ROMs already have an expanded text bank and I don't want to overwrite it.
In other words…
I was planning to add this text via an IPS patch and we can't predict where everybody's text bank ends… :? So I figured the bottom of the page was the safest.
Quote:I didn't edit your new text at all, just used DOAEditor and my mod got all borked up. I believe that I am going to have to re-apply your IPS EVERY time I make adjustments via DOAEditor atm… I think we really need to get Niahaks help on this one.We need your help to get DOAEditor to accept the new text that MidKnighT has added to the game. Whenever DOAEditor is used, for text adjustments or not, it seems to be borking the rom. Any ideas?
- You must be logged in to reply to this topic.