17 replies to this topic

[dlamey8015]

Alright, so my previous problem is fixed, but now I'm having a problem with the text command.
The game glitches every time I try to load a bit of text that I've edited.
It doesn't occur when I load text that was originally in the game,
but only with custom text.

Here is my code:

Opening_event:
LOU1 Bad
ENUN
TEX1 0x800
REMA
LOU1 RebeccaLoad
FIGH Rebecca Zephiel Fight 0
KILL Zephiel
ENUN
END_MAIN

[Snow]

Yeah that's happened to me before, several times in fact >_> I still can't figure it out but I think it has to do with the rom you're using.

[Golden Warrior]

Could you elaborate a bit on "the game glitches"? What exactly does it do to glitch? Screech of death? Or does the screen just go black without a noise. (Oh, and could I see the text you are trying to load? I think I've fixed this problem before.)

[dlamey8015]

It gives me the screech of death.

[Golden Warrior]

Ok then, could I see what text you're trying to use? The custom text, I mean. It'll give me better understanding of what's happening.

[dlamey8015]

Actually, it just decided to randomly fix itself.
Well, never mind then.
Thanks anyway.

[Golden Warrior]

Huh. Ok then.

Well, any time there's a problem go ahead and ask away!

[OmnisScio]

I kind of wish it didn't fix itself, now no one will know what was actually going on.

See, I too have encountered this exact problem. I'm trying to get text working, if I point it to text that I have altered, I get the horrible screeching, but if I point it to unaltered text, it works fine.

[dlamey8015]

It's a problem with your rom. You'll have to get a clean rom and start over.(Unfortunately) Save any data that you can, then get a new rom.

[OmnisScio]

All I had done to a clean Rom before encountering this problem was insert the map (0x8DA0000) and event file (0x8D80000), re-pointed the prologue map and events in FE7 reference editor, changed the map settings in chapter data to fit with the new map. I had a text command in the event file point to 0x815. Running the Rom at this point works perfectly. If I then go into FEditor and change that text, I get the screech. This is what I had done before posting here.

However, I tried your suggestion anyway, got a new clean rom, inserted map, event file, works fine, change text, screech.

What I really want is an action that directly solves the problem with an explanation as to whats going wrong and why that action fixes it.

[dlamey8015]

Actually, I seem to be having the same problem at the moment. Originally, just using a clean rom worked, but it doesn't now.

[Fire Blazer]

What game is this? What is the original text and the new text? It might be the specific text slot you're using--try using another text slot. Also try making the text blank and see if it still screws up. If it's FE6, that might be your issue--FE6 is screwed up in general though there's supposed to be some fixes for some of the FE6 bugs (see here)

This sound like a rather annoying problem and multiple people are having it so let's work together to try to fix it. If the issue persists I'd say the next step would be to make a copy of a clean ROM, edit nothing but the text, replicate the glitch, then make a UPS patch between the clean ROM and the glitched ROM. Then we'll use patch difference to analyze the difference in data--however for you guys if you're not familiar with the ROM this might not be very useful to you so you may need to upload the patch and link it to me so I can check it out myself even though I'm supposed to be retired from hacking

[dlamey8015]

The game is FE7 for me.

The error doesn't occur when I change the text with the ID 815 and play the game normally with no other modification.
The error also doesn't occur when I change text with the ID 800 and use a simple event script to display that text.
So far it has only occurred in a rom where I inserted a map, a custom portrait, made an events file, and THEN changed the text.
I'm not sure if examining the changed data would allow you to see the cause of the error, just because of all the things I've changed,
but I'll put the patch here anyway.
Patch

[Fire Blazer]

That's why I said we need to replicate the glitch on a ROM as clean as possible first. There are a couple other people here so maybe they can help with a ROM with less edits, we'll see. If it's just inserting data, that's fine, the main issue is if there are weird patches applied, ASM hacks done, random graphics or other peculiar data edits, etc., but if it's just like inserting maps to the 0xD00000-0xDFFFFF or 0x1000000+ areas, I know that can't be the problem so I'm not worried about that.

[dlamey8015]

I tried replicating it on a clean rom, but the error didn't occur.

[Fire Blazer]

Hmm, any chance you could list the changes--at least in general--you made to your hack then? If possible note anything directly related to the text, i.e.

- the EXACT code you used to load the text
- ID of that slot/index
- the actual text in that slot/index

as well as any weird changes

and then other generic changes e.g. "nightmare edits", "portrait edits", etc., which we can -probably- rule out but are useful to know in terms of analyzing the data

I realize this is a pain but sadly this is how higher-level debugging goes (and tbh this is mostly just basic logical, trial, and error...)

[OmnisScio]

I am also modding Fire Emblem 7

I tried changing the order that I did things, and found that if I modify the text before loading and re pointing the events and map, it worked. Hopefully this is helpful in finding out whats going on, because this is most definitely not a solution. i don't want to have to do all my text before touching anything else.

Information:
map location: 0x8DA0000
events location: 0x8D80000
Edited text slot 0815

Event file:

x (Click Here To Hide/Show Text)

//Made by markyjoe1990 of Youtube
//Modified by Nintenlord

#define DISABLE_TUTORIALS
#include EAstdlib.event

EventPointerTable(0x06,Pointers)


ORG 0xD80000
Pointers:
POIN Turn_events
POIN Character_events
POIN Location_events
POIN Misc_events
POIN TrapData TrapData
POIN Bad Bad Bad Bad
POIN Good Good Good Good
POIN Opening_event Ending_event

Bad:
UNIT Batta Brigand 0x00 Level(5,Enemy,True) [7,1] [7,1] [IronAxe] [0x00]
UNIT Empty

Good:
UNIT Lyn_t LynLord 0x00 Level(10,Ally,True) [2,8] [2,8] [ManiKatti,Vulnerary,ChestKey] [0x00]
UNIT Empty

Turn_events:
TurnEventPlayer(0x00,Opening_event,1)
END_MAIN

Character_events:
END_MAIN

Location_events:
Chest(IronSword,13,1)
Seize(0x00,Ending_event,7,1)
END_MAIN

Misc_events:
CauseGameOverIfLordDies
END_MAIN

Opening_event:
CMOF
LOU1 Good
ENUN
LOU1 Bad
ENUN

FADI 16
HIDEMAP
BACG 0x06
FADU 16
SHOWMAP
TEX1 0x815
REMA


//Text(0x06,0x815)
ENDA

Ending_event:
MNCH 0x02
ENDA

TrapData:
ENDTRAP


MESSAGE Events end at offset currentOffset
//The map for this chapter is at offset: ????????

[Fire Blazer]

^Sadly I doubt it's your events. I don't see any errors in your events in my so as long as they're loading alright/setup alright I don't think that's the problem. That being said I didn't really doubt you guys on what you said earlier which suggested it wasn't, but I'm just playing it safe since I'm pretty much just as in the dark as you guys (if not more so because I haven't encountered this problem myself and don't have a patch and savestate to experience it).

That patch the other person uploaded (sorry I can't remember your name and don't feel like checking cuz it's really late and I'm really tire) had a MASSIVE amount of edits to a large section of the ROM which might have been the text area... which is awfully weird because I don't see why so much of that would be edited. I'd like to know why in the world it decided to screw all that up, tbh. Another weird thing is that if the patch was correctly made and is essentially a patch to convert a clean FE7 ROM to your hack, and you saved with FEditor Adv... why doesn't it include changes to the ASM part of the ROM? Your UPS patch makes NO changes to the main ASM part of the ROM which is highly suspicious. That pretty much yells "I haven't been edited by FEditor", but if it really has, there's a problem. I can't say anything decisive yet without help from you guys but someone try opening their ROM, saving it, and closing, and seeing if that does anything, and also if someone can get me another patch (this one I just checked out real quick seems way too odd so I'd like another one to try and help figure things out) and perhaps a savestate to go along with it, that would help greatly.