- This topic has 1,129 replies, 26 voices, and was last updated 10 years, 12 months ago by
.
-
Posts
-
Yeah, I needed to increase a value by one in the DoaEditor code.
http://www.niahak.org/images/DOAE/DoaEdv098f.zip – not updating front of topic for reasons stated below.
This is a bit sad, because my text editor always assumed that each line was denoted by two pointers: start, and end (beginning of next line). Pretty much what you said MiDKnighT – it lays all the lines end to end and that's how it can do its nifty compression.
So you can edit the last line, but it doesn't have a preset 'end' pointer… so to get more space in the 2nd text bank, you'll have to delete something. You can always delete the 0s at the end of the last line.
I'll consider this a bug, though. Lines should parse until they hit the first [end]… but that's a hefty refactor I don't think I can tackle tonight.
No problem for me Niahak. I have an open slot I can use in the duel text so I can intentionally leave the last line blank if that will save some grief. Just let me know.
Ah, so is all the new garbled text I have on the last line safe to delete?
Too late, deleted it and it seems fine. Rom is working now again as well. Hooray!
:huohu:
Despite the fact it may be "bugged" it did work*
emailed you two copies of the Rise of Ieyasu mod i'm improving atm. One is broken the other still seems okay. After editing w/ DOAEditor, it breaks it and causes it to freeze during battles. This sometimes happens when editing text and other times just with a simple officer edit. Compiling issue, overflow issue, or exporting issue? I'll leave it to the master!
It still puts in the "ghost lines" also after I edit a line, it duplicates it beneath the line I just edited. Not sure if this is affecting it or not?
Hey sonic,
I'm afraid I'm on vacation and may not be able to troubleshoot it all that quickly, but I'll help when I can.
I took a look at the broken rom, and nothing seems that unusual in the hex. My guess would be a pointer gets misaligned when it tries to save.
Any chance MiDKnighT could help us debug the freeze somehow? That would narrow down the problem.
Will give it a try, but I think I might have to bribe him with some Yuan Shaoish propaganda…
Quote:Will give it a try, but I think I might have to bribe him with some Yuan Shaoish propaganda…Works for me hehe. ROM + save state if you can reproduce the hang and I can try to find out why it's hanging.
Quote:Will give it a try, but I think I might have to bribe him with some Yuan Shaoish propaganda…Works for me hehe. ROM + save state if you can reproduce the hang and I can try to find out why it's hanging.
okay, one sec, but if I get it to hang should I SS it while its hanging or just in a battle where I KNOW its going to hang?
hmm first couple of battles I tried with the broken one worked fine. Anything specific to reproduce the problem?
Okay, sent two savestates. fc2 glitches up after a few battles. fc4 is in the middle of a glitch. Granted, the rom not labeled as broken should work fine with fc2 and not glitch up at all.
Save state 4 won't work since I can't see how it got to that point. With save state 2 I probably got into 20 battles and didn't see the problem. Will keep trying. Is it more likely to happen against enemies who use tactics?
Also, Hanzo's sprite kicks ass! :thumleft:
- You must be logged in to reply to this topic.