- This topic has 31 replies, 7 voices, and was last updated 14 years, 4 months ago by
.
-
Posts
-
Quote:Actually, reading this made me wonder of a super-easy solution that can be implemented in DoaEd, but I doubt Niahak would want to do it. Picture this:
An option in DoaEd that asks for the following input from the user:
Input / Output ROM File to Edit: Full file path.
Input ROM File to get data from: Full file path.
Start address for Input file 1.
Start address for Input file 2.
Number of bytes.
It's easy in theory, but in practice it might be a support nightmare (no more usable for the novice than FEIDIAN).
The other concern is different numbers of patterns-per-portrait – for example Gemfire NES has 40×48 portraits and DOAE has 48×48, so a direct conversion's not straightforward.
If someone could convince me otherwise I'd consider it.
On the other hand, direct image input was something I was considering eventually (input 48×48, 4bpp BMP and an index, and it'll overwrite the next 6 strips with the BMP). Since I have a limited framework that can convert from the patterns to an image, I can also do the reverse, hypothetically.
Sonic's pretty much described how my priority list works – get the most frequently used stuff working, then the less frequently used stuff. And I'm not even sure how much this stuff gets used – I certainly don't use it myself :P
P.S. Warp/Battle movement on the map's nearly complete, I just need to troubleshoot it a bit… although gullwing locations may not update initially.
Oh, I was thinking of something more along the lines of taking portraits from DOAE 2 and using them in DOAE 1, but if you guys are using portraits from other games, then that would be more work.
Actually, in spite of that, it would still be an usable feature. No matter what NES game you are talking about, they all use 8 x 8 pixel, 4-color Patterns with the exact same format. ( If it was not for that fact, programs like TileLayerPro would be useless. ) So really, the only problem would be that the user would have to specify the address of each Pattern that makes a portrait.
I still think it would be something that can have a potential for some use, as it can be used as a binary copy-paste mechanism for any byte-stream of data, but I can certainly understand that it would not be nearly as useful in practice.
- You must be logged in to reply to this topic.