Screenshots

[Eden.GT]

Just having fun!

The clouds look "off"....

[PresidentLeever]

A quick Deep Duck Trouble SMS to NES port mockup pic I just did (18/15 colors):

Reduced sprites to 4 colors in pic b.

Edit:
Aladdin SMS to NES (17 colors):

[Midna]

That "four colors" bit with the NES sprites includes transparency, so effectively it's just three colors. Sometimes developers like Capcom with Mega Man or the DuckTales games would create the illusion of a sprite having more than three colors by layering sprites on top of each other, though.

[KingMike]

3 colors per palette (x4 background palettes and 4 sprite palettes) plus one background (transparency) color.
Also, if you're going for authenticity, the NES can only set palettes on a 16x16 pixel grid (every 2x2 tile square must share a palette).

[Midna]

I think there are at least two NES mappers that allow you to assign palettes on an 8x8 pixel grid instead of 16x16. I know the VRC6 (Akumajou Densetsu) is one, and the localized Castlevania III uses a first-party equivalent.

[PresidentLeever]

That "four colors" bit with the NES sprites includes transparency, so effectively it's just three colors. Sometimes developers like Capcom with Mega Man or the DuckTales games would create the illusion of a sprite having more than three colors by layering sprites on top of each other, though.

Oh ok, I thought it was 3+one shared color between sprites. I've read about that, and there are also some enemies in SMB3 that use 4 and 5 colors.
http://2.bp.blogspot.com/-CU2WFCti4As/VInXikrI5CI/AAAAAAAAB7Y/yYs7NHynNCo/s1600/smb3title.jpg

[Midna]

That's using the layered sprites technique.

[paul_met]

Farland Saga - resolution hack (Saturn)

[Special T]

Farland Saga - resolution hack (Saturn)

Are you also translating the game or just the menus?

[paul_met]

Are you also translating the game or just the menus?

Just some of the general menus for easy navigation.

[Madsiur]

WIP FF6A (E) and (U) Text Editor (all game text, all game languages).

I've good a good part of the monster data, item data, Font, monster gfx and portrait editors done so hopefully a beta version should be available in a not so distant future..

[justin3009]

- Got 3 byte experience working, thankfully.  Had to gank some code from Sailor Moon: Another Story to get it to display properly but all the calculations seem to work inside and outside of battle thankfully.

[Kurt91]

Do you have something in mind, or did you just want to turn Super Mario RPG into a massive grind session?

[Kea]

Getting a hang of FF1a's text routines. Before:


And after:

(The "-1" means that the Mythril Hammer reduces your number of hits by one, another feature I've added)

[justin3009]

Getting a hang of FF1a's text routines. Before:


And after:

(The "-1" means that the Mythril Hammer reduces your number of hits by one, another feature I've added)

Very nicely done!  That looks a lot better!  The new feature is pretty nifty as well.

[Kea]

Thanks! I had considered displaying the weapon's evade bonus, replacing Crit Rate or as a fourth stat, but the Evade boost of a weapon is visible when you equip it, while Crit isn't (yet anyway). Adding a fourth displayed stat looked too cluttered and would break symmetry with armor displays which don't have a simple fourth stat to display.

Most of the rest of my FF1 work is more mechanics-oriented, so there's not much in the way of screenshots to show of it.

[Kiyoshi Aman]

You could move the cost over to the stock/equipped window, I think. It'd give you more room to work with, especially if you changed Equipped to Worn and put the stock and worn numbers in the same row as their labels. This would allow you to add hits or other relevant fields (up to six).



(quick mock-up in the GIMP. I really, really hate the FF1 Advance font, by the way. It looks like ass.)

[Bonesy]

i love whenever people call it "the gimp"

it just sounds so


dirty

[Kea]

You could move the cost over to the stock/equipped window, I think. It'd give you more room to work with, especially if you changed Equipped to Worn and put the stock and worn numbers in the same row as their labels. This would allow you to add hits or other relevant fields (up to six).

That's good idea, I might go for that. I don't think more than five displayed fields will be practical or helpful unless I can figure out how to display elemental properties ingame (that'll go in the readme most likely). Will experiment with placement some more.

And yeah, I'm not fond of FF1's font either.

[justin3009]

- Got this annoyance out of the way finally.

I've been wanting to display the 'Speed' stat but there's no room on the screen using the big font unless I extend the window down to the very bottom of the screen.  In that way, it would've been pretty damn ugly and inconsistent with everything else in the menus.  Had to go a rather obnoxious roundabout way to get all this to work.

The text itself is pre-rendered graphics.  I was trying to tie it into the actual text routine but it's way too convoluted to go that route unfortunately, so I went the easier way.  The arrows themselves are a lot smaller.  I added in a new routine that sends the decompressed graphics of the Menu Sprites into VRAM so now they're freely able to be edited which fixed that.

After that it was a massive mess of getting the Tile Map to update properly for Layer 3 instead of Layer 1.  But it turned out pretty good I think overall, though I'm pretty stressed out from it all, I'm quite glad it's done.