- This topic has 534 replies, 19 voices, and was last updated 9 years, 5 months ago by
.
-
Posts
-
ok i don't know how to upload photos (photobucket doesn't want to work for me) but that last battle has:
Lu Bu 41332 Zhang Jue 50903
Jiang Wei 40481 Sun Ce 50903
Zhao Yun 39340 Sun Quan 50903
Zhang Liao 37214 Li Ru 32303
Zhuge Liange 29727 Cao Pi 42509
once I beat that, there is this…:
Dong Zhuo 61529
Zhang Jue 50903
Cao Cao 46440
Yuan Shu 46440
Ding Yuan 46440
Crazy…
The ghost fights were meant to be insane ;)
I forgot how I handled it, but it was before some patching SP had done to the mod, you can prolly find my turn out earlier in the thread heh.
Rise of Lu Bu suffers from not having TP regeneration. It's old school DOAE and turns into battles of attrition or Thwart-Luck. This is one of many things I'd like to change in it.
MiDKnight, gonna send you the current version of Rise of Lu Bu. Can you see if you can expand it to 1MB? I expanded it and it messed up the sprites, unless I missed something…
Any luck expanding ROLB to 1MB? I wanted to continue working on it. I can use the current version if you can post the bugfix here that I can use to expand it to 1MB.
Yeah, the sprites at 74090 are garbled no matter what I do
sonic – the IPS patch is updated for 1MB ROMs and it includes the sprites fix. Try expanded ROLB with DoaEditor then apply IPS 1.2 Patch2 and that should fix it.
Okay, will give it a shot
Working on version 3.0!
Essentially, I'm changing it to what I originally wanted. Starting with Lu Bu and keeping him throughout. It's a lot of changes, but my past mod experiences has allowed me to finally bring it to fruition. This just wasn't possible 2 years ago… At any rate, stay tuned!
Emailed the latest file w/ a few things:
1. The mismatch list just doesn't seem to match up with the addresses.
2. The last person in the formation going first locks things up still. Wasn't this fixed? Maybe Patch 1.2 didn't have this fix.
This is from the Rise of Ieyasu Thread
Quote:I've had stack overflow issues before. This bug isn't overflowing the stack…but it gets fairly close. Ie…it gets within 10 bytes or so of overflowing the stack. Perhaps I should try limiting it further.
To understand the bug more let me show you what is happening. There are a handful of flavors of the bug but they basically end up doing the same kind of thing… Here's a different variation of the same problem:
It's enemy 09's turn:
$A92C:A6 78 LDX $0078 = #$09 A:06 X:12 Y:5E S:1C P:nvUBdIZC
$A92E:B9 A0 65 LDA $65A0,Y @ $65FE = #$12 A:06 X:09 Y:5E S:1C P:nvUBdIzC
Switch to page 08:
$C4B6:68 PLA A:00 X:FC Y:00 S:11 P:nvUBdIZC
$C4B7:8D F9 FF STA $FFF9 = #$AC A:08 X:FC Y:00 S:12 P:nvUBdIzC
PC jumps to EE79:
$86AE:F0 0B BEQ $86BB A:00 X:0A Y:0E S:10 P:nvUBdIZc
$86BB:A0 05 LDY #$05 A:00 X:0A Y:0E S:10 P:nvUBdIZc
$86BD:B1 CC LDA ($CC),Y @ $0762 = #$00 A:00 X:0A Y:05 S:10 P:nvUBdIzc
$EE79:08 PHP A:00 X:0A Y:05 S:0D P:nvUBdIZc
$EE7A:48 PHA A:00 X:0A Y:05 S:0C P:nvUBdIZc
Switch to page 08:
$C4B6:68 PLA A:00 X:FC Y:00 S:05 P:nvUBdIZC
$C4B7:8D F9 FF STA $FFF9 = #$AC A:08 X:FC Y:00 S:06 P:nvUBdIzC
Going to switch pages to page 01:
$8000:A9 01 LDA #$01 A:00 X:09 Y:5E S:1C P:nvUBdIZC
$8002:20 82 C4 JSR $C482 A:01 X:09 Y:5E S:1C P:nvUBdIzC
$C482:85 44 STA $0044 = #$1E A:01 X:09 Y:5E S:1A P:nvUBdIzC
$C484:85 ED STA $00ED = #$1E A:01 X:09 Y:5E S:1A P:nvUBdIzC
Push "01" to the stack:
$EF08:A5 ED LDA $00ED = #$01 A:00 X:FC Y:00 S:09 P:nvUBdIZC
$EF0A:48 PHA A:01 X:FC Y:00 S:09 P:nvUBdIzC
Pulling "01" from the stack and switching to that ROM page:
$C4B6:68 PLA A:00 X:0E Y:1C S:06 P:nvUBdIZc
$C4B7:8D F9 FF STA $FFF9 = #$AC A:01 X:0E Y:1C S:07 P:nvUBdIzc
The RTI here dumps us back to $86BF on ROM page 1 which is invalid.
$EF37:40 RTI A:00 X:0A Y:05 S:0D P:nvUBdIZc
$86BF:C4 AD CPY $00AD = #$85 A:00 X:0A Y:05 S:10 P:nvUbdIZc
$86C1:73 UNDEFINED A:00 X:0A Y:05 S:10 P:NvUbdIzc
So the whole bug is that it's executing code on the wrong page (01). I guess it expects to be on the original page which is page 08.
Regarding the IRQ stuff, the bottom of each ROM page references EE79 but not sure how that all works with IRQ just yet:
000000004804000008AC79EED8FF79EE
Writing this all out has helped me understand it a bit more but not sure how to fix just yet.
And this, but ROLB is now 1MB so…
Quote:That said, sonic, I think FOW is already 1MB right? We can work on getting RoLB and Ieyasu to 1MB then I can work on a fix in the 1MB format. I think this might be easier to fix in the 1MB ROM, or at least I'd need to fix in 1 format instead of 2.It would be easier to get RoLB and Ieyasu to 1MB than it would be to fix this bug in the 500k version.
So sonic here's my job for you:
1. Expand RoLB and Ieyasu via DoaEditor.
2. Make sure the hex lines up with the first post here:
http://www.lordyuanshu.com/forums/topic/uber-rom-expansion
If not, correct it with what is in the 1st post.
3. Fix the duel text (it will be the default duel text after the expansion).
4. If there are any problems with the expansion, send me the ROM and save state.
5. Then let's try to make the problem happen on a 1MB ROM. If you can get it to happen, send me ROM and save state.
I think we should just scrap the 500k ROMs – ie…get them all upgraded to 1MB.
The only difference I found in the code was at 0x80000 and 0x80001 being 5A and E4, instead they were C4 and 4C
Quote:1. The mismatch list just doesn't seem to match up with the addresses.Who are the officers that are supposed to be mismatched? What are their names and officer IDs? Also the save state seems to be corrupted. Can you re-send?
Quote:2. The last person in the formation going first locks things up still. Wasn't this fixed? Maybe Patch 1.2 didn't have this fix.Ya I still saw this on lud's mod with 2 potential fixes in place. Both of us are baffled as to what's causing it at the moment but we'll keep looking.
Resending…
The officers (which I didn't put in place because I didn't want to mess more up) were Lu Bu (AA) vs. Mu Shun (16) and Wu Anguo (18).
So far I've completely redone the first two chapter and It's going pretty fast since I know what I wanted. It's just changing the story progression, map edits, and balancing tweaks but Lu Bu all the way through!
I remember sort of the time when the bug was introduced. You were fixing a bug that happened during All-Out because some major update was just added to the game. It was around the time of agility based attacks and the like but not sure if that was what triggered it or not.
- You must be logged in to reply to this topic.