Register | Login
Views: 19364387
Main | Memberlist | Active users | ACS | Commons | Calendar | Online users
Ranks | FAQ | Color Chart | Photo album | IRC Chat
11-02-05 12:59 PM
1 user currently in Rom Hacking: hukka | 2 guests
Acmlm's Board - I2 Archive - Rom Hacking - FCEUXD Release
  
User name:
Password:
Reply:
 

UserPost
Parasyte
Posts: 412/514
Originally posted by HyperHacker
Er... How is NESticle able to save graphic changes?


Only for games containing CHR-ROM. And only for CHR-ROM that is visible during V-Blank (or around there). So NESticle even makes a terrible tile editor.
iamhiro1112
Posts: 335/487
Originally posted by Gavin

it's not slander about nesticle, just fact. an NES emulator is a piece of software that attempts to replicate the NES hardware, on that basis, as a matter of fact and not opinion, NESticle sucks because it replicates the NES very poorly


Ok, its a fact. But just the same the thread didn't go in the direction I was expecting.
HyperLamer
Posts: 4027/8210
Er... How is NESticle able to save graphic changes?
Gavin
Posts: 598/799
Originally posted by iamhiro1112
My emulator thread got derailed like this too. Instead of getting suggestions on emulators to add to the list it became a slander nesticle and it's users thread.


actually he's asking rather pertinent information about the functionality of an emulator. i guess what i'm really getting at is: what purpose did your post server other than to bitch about how you were pointed out as not knowing what you're talking about?

it's not slander about nesticle, just fact. an NES emulator is a piece of software that attempts to replicate the NES hardware, on that basis, as a matter of fact and not opinion, NESticle sucks because it replicates the NES very poorly
iamhiro1112
Posts: 328/487
My emulator thread got derailed like this too. Instead of getting suggestions on emulators to add to the list it became a slander nesticle and it's users thread.
Parasyte
Posts: 409/514
The hex editor cannot save changes to RAM or PPU memory, because this data is all generated by the game at run-time. The ROM is what you can change and save. And in fact, you can change the title screen in the very first ROM bank (in Metroid). The data is sort of "compressed" though. It's a very simple format, really. You just need to understand the PPU to edit it by hand.

The title screen begins at ROM address $000304
The format is pretty simple: First two bytes are the PPU address (desination). Third byte is the length of the data to write. Then that number of following bytes is the data to copy.

So let's take a look at the first PPU command used to build the title screen:
23,C0 - PPU address (destination) $23C0
20 - Data length, $20 bytes
00,00,00,00,00,00,00,00,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF - The actual data

The data following will be another PPU command, with the same exact format. The game continues to read more and more commands until a PPU address of 00 is read (upper byte, meaning if the first byte of the command is $00, the game stops drawing the title screen).
Get Yoshi's NES docs, if you don't understand what the PPU addresses are for. The name tables and attribute tables are what's important to you in this situation.


Now that the Metroid-specific stuff is out of the way, this can go back to being about FCEUXD. (Meaning, please continue this conversation in a new thread.)
midget35
Posts: 15/70
Yeah, I need to read up more because I'm starting to confuse myself now. I just can't see how the graphics are ordered per-room in the rom view. There seems to be no consistency, which is of course not true.

the title graphics layout is the same in the PPU and rom, albeit they start at different addresses. Yet this does not seem to apply for ingame screens. I'm really thrown out by it all.
Gavin
Posts: 583/799
heh, ouch, that sounds like some painful hacking
dan
Posts: 503/782
You are actually editing the PPU in the hex editor? I don't think it's possible to save the changes made there. Nor will it ever be possible.
midget35
Posts: 14/70
Is there a way to save aesthetic graphic changes made in the PPU, so that they are a permenant feature of the rom?
Ice Ranger
Posts: 114/183
Originally posted by Parasyte
Originally posted by Chill Penguin
Heh, one feature I'd like in the next build is definitely a debugger that snaps when certains values are run through the break point set. ... seems like that's being worked on last I checked, I just don't have an idea of when/if it's going to be released since the project went open source.


Could you explain? If you're talking about the conditional break support that I'm working on... it's on the way. :\


It was you I heard it from! I knew I heard it from someone in some thread. Yep, that's exactly what I've been looking forward to being released. Indeed, the people shall rejoice upon the new release of FCEUXD with this added feature.
midget35
Posts: 13/70
Sorry about bringing this thread up. Thought I might have been asked to repost here anyway if I'd started anew.

So my understanding is that any changes I make in the PPU show up temporarily. Fine, but if I copy that information to the rom viewer at the same address and save it, shouldn't it be permanent and present next time I load the rom?

Because at the mo only text changes are saved.

Gavin
Posts: 580/799
and when it arrives... there will be much rejoicing!
Parasyte
Posts: 405/514
Originally posted by Chill Penguin
Heh, one feature I'd like in the next build is definitely a debugger that snaps when certains values are run through the break point set. ... seems like that's being worked on last I checked, I just don't have an idea of when/if it's going to be released since the project went open source.


Could you explain? If you're talking about the conditional break support that I'm working on... it's on the way. :\
BMF98567
Posts: 726/1261
Next time, instead of bumping such an old topic, just start a new one. Falsely getting people's hopes up is bad bad bad.
iamhiro1112
Posts: 323/487
And in the next build they need to include the keyboard shortcuts in the read me document.. I had to press random buttons till I found the Pause key. Not criticizing. I'm just not sure if it's been brought up before.
Ice Ranger
Posts: 113/183
Had my hopes up for a second that more features were implimented and was going to be distributed in the next few months.

Heh, one feature I'd like in the next build is definitely a debugger that snaps when certains values are run through the break point set. ... seems like that's being worked on last I checked, I just don't have an idea of when/if it's going to be released since the project went open source.

Might want to sticky this, make easy access for newbies to know about/get FCEUXD.
Dish
Posts: 319/596
Originally posted by iamhiro1112
I wish it had a turbo option but I guess it isn't really neccesory.


Try the '~' key.
iamhiro1112
Posts: 321/487
Ah, no wonder FCEUXD was so highly reccomended. This is like its birthplace. It's great. I wish it had a turbo option but I guess it isn't really neccesory.
Xkeeper
Posts: -2195/-863
Originally posted by midget35
Hi there. This is probably a real newbie post but please stick with me!

I'm just getting used to FCEUXD, and am using it to do some text and title graphic editing on Metroid.

I've read through the faq and related posts but couldn't find the answers.

Basically- using the hex editor, I can save text string changes under View- Rom File. The changes I make don't seem to appear 'on-the-fly' unless i make those changes in the 'PPU memory view'. Unfortunately, whenever I save changes made in PPU, they don't appear the next time I load the rom. Is this supposed to happen?

Also- I shifted a few title tiles around to create my own graphic, but when I save these alterations in either Rom File or PPU, they don't appear to save and next time I load the rom the tiles revert to their original positions.

Could this have something to do with not using a stripped rom? I tried to strip the header with Ucon64 but it corrupted the file, and I'm not using the logging facilities or anything.

I fear the problem is simply that the changes I make aren't saving for some reason, though I can't explain the string changes saving ok. Strange to me..

Thanks very much for any help,

Regards.
(wow, what a bump)

Regardless, to have the ROM changes show up, you'll need to likely reload the room (go out/back in) or restart the ROM. The PPU, as far as I know, just shows the current one and is erased after it's overwritten by something else
This is a long thread. Click here to view it.
Acmlm's Board - I2 Archive - Rom Hacking - FCEUXD Release


ABII


AcmlmBoard vl.ol (11-01-05)
© 2000-2005 Acmlm, Emuz, et al



Page rendered in 0.005 seconds.