 |
|
Main
| FAQ
| Uploader
| IRC chat
| Radio
| Memberlist
| Active users
| Latest posts
| Calendar
| Stats
| Online users
| Search
| |||
| Views: 88,483,398 |
Main
| FAQ
| Uploader
| IRC chat
| Radio
| Memberlist
| Active users
| Latest posts
| Calendar
| Stats
| Online users
| Search
|
04-25-24 09:25 PM |
|
| Guest: Register | Login | |||
| 0 users currently in ROM Hacking | 2 guests | 2 bots |
| Main - ROM Hacking - Problems editing/ripping N64 graphics | New thread | New reply |
| joe |
| ||
 Red Paratroopa Level: 31 Posts: 144/172 EXP: 178015 Next: 7348 Since: 04-08-07 From: Justus League 2 Last post: 6116 days Last view: 6084 days |
On a random whim, I decided to see if I could rip graphics from Paper Mario. Well, Tile Molester can edit N64 graphics, right? Right. Well, a quick look using Tile Molestor and I found the "no controller" graphics, lots of mangled garbage, and the N64 logo. (Looked terrible until I switched to RGBA5551.) "That's odd," I thought, "Why isn't it byte aligned?" I looked closer. "That's really odd, why does it look like the colors are leaking out the side?" That's about when I gave up.
I was bored, and wondered why some roms had different extensions. I googled them, and found out that different extensions are for different byte orders. I wondered if that had anything to do with the funny colors. A bit more searching, and I discovered that the problem was not my byteswapped ROM. (Mostly because it ...uh, wasn't byteswapped? It's a .v64, so it should be...) I byteswapped it anyways, to see, and the N64 logo showed up, perfectly clear and byte aligned. But now everything else was messed up. Time for another program. n64gfx.exe is currently in my recycle bin. Why? It fails the same way Tile Molester did when confronted with RGBA5551. Surely another program can handle this simple* format! SpriteView, the only other program I could find that could handle RGBA5551, seems to think there isn't enough memory on my computer. It joins n64gfx. (Not only that, but its "high" and "true" color modes use a 256-color pallete, so even copying is impossible.) So, after much frustration, I ask only this: Is there any program that can CORRECTLY display Nintendo 64 graphics? *So simple, I could use nothing but Translhextion, Calculator, and Paint to rip it from a non-byteswapped ROM! ____________________ "I'm sick of it and I'm out. See you around." ~Cpu's last post here |
| Raccoon Sam |
| ||
 Cobrat Level: 56 Posts: 279/672 EXP: 1379964 Next: 18212 Since: 02-19-07 From: Hi Last post: 3467 days Last view: 2698 days |
I'm glad I'm not the only one who noticed.
(If anyone thought his post was too long, he mentions that Tile Molester does not handle the 16bppRGBA5551 format correctly.) I don't know the answer, but I would like an answer also! ____________________ |
| Aurakitsune |
| ||
 Goomba Level: 15 Posts: 12/34 EXP: 15632 Next: 752 Since: 04-17-07 Last post: 5358 days Last view: 4713 days |
I've been looking for an answer to this for a while now.
Maybe I should bug Zoinkity next time he posts over in the DnM translation thread on EmuTalk...  |
| joe |
| ||
|
Red Paratroopa Level: 31 Posts: 147/172 EXP: 178015 Next: 7348 Since: 04-08-07 From: Justus League 2 Last post: 6116 days Last view: 6084 days |
Wow my post is long 
I think the 16bpp mode was designed for byteswapped ROMs, but the lower-bit modes were designed for non-byteswapped (big-endian) ROMs. ...Tool64 (Windows only) can be used as a workaround. Select your ROM and click the four arrows icon. Then, edit the 15 or 16bpp graphics. When you're done, select your ROM and click the arrow pointing to the right. This program automatically changes the extension. Converting a ROM to byteswapped will change its extension to .v64, and converting a ROM to big-endian will change its extension to .z64. Keep that in mind so you don't accidentally edit the wrong file. ____________________ "I'm sick of it and I'm out. See you around." ~Cpu's last post here |
| HyperHacker |
| ||
|
... Level: 73 Posts: 1118/1220 EXP: 3366634 Next: 119234 Since: 03-25-07 From: no Last post: 6091 days Last view: 6074 days |
Tile Molester apparently makes assumptions about the CPU's byte order, so it handles that format properly on PPC Mac but not x86. You can view the graphics by advancing a byte, but trying to edit them this way will usually just corrupt nearby data. Also, most N64 games compress their graphics; look for the ASCII "MIO0", "YAZ0" or "YAY0" in a non-byteswapped ROM. |
| joe |
| ||
|
Red Paratroopa Level: 31 Posts: 151/172 EXP: 178015 Next: 7348 Since: 04-08-07 From: Justus League 2 Last post: 6116 days Last view: 6084 days |
Since it works just fine on most Macs, then everyone using Windows can convert their ROMs with Tool64, and avoid those problems entirely. As for your method, it just makes colors bleed and gave some graphics a strange yellow aura.
MIO0, YAZ0, YAY0, ... It's got "Yay0" multiple times, but Tile Molester seems to be showing me all of the graphics. (Hard to say for sure, since the palettes are 16-bit and I have to enter them by hand, and the graphics tend to not fit neatly within the 8-pixel increments that Tile Molester uses.) How would I be able to decompress the YAY0 data? ____________________ "I'm sick of it and I'm out. See you around." ~Cpu's last post here |
| Main - ROM Hacking - Problems editing/ripping N64 graphics | New thread | New reply |
© 2005-2023 Acmlm, blackhole89, Xkeeper et al. |
|
MySQL - queries: 57, rows: 83/83, time: 0.015 seconds. |