NEXXT 3.6 released

NEXXT studio 3.6 » Devlog
13 days ago by FrankenGraphics (@FrankenGraphics)
Share this post:

This update is in particular good news for NESmaker users: there's now a hand tailored method to import and export NESmaker-encoded tileset images! It will even correct rogue colours for you, meaning you can use it as an intermediary step between NESmaker and some other graphics editing tool. 

NESmaker users should be aware that whenever NEXXT imports a tileset that is smaller than a full NES tileset (which is usually the case with NESmaker tilesets), it starts laying down that tileset from where the Tile Cursor currently is. That means you typically want to set the cursor to the top-left corner of the tileset canvas before starting.

As an added bonus, NEXXT can now also interpret any 24bit png or bmp as a 4-colour tileset in the simplest way possible - it clamps RGB colours to 4 ranges of average brightness and lays them down as pixel colours 0 through 3. Colour order and pixel value order can then be customized through the palette menu, if needed.
This was done with fairly popular grayscale tilemaps in mind, but could also work for conversion of colour content in a pinch. 

Using indexed mode images for full control and intactness is still recommended. 

There's also a new map placement tool (place from map selection [c-click]), improvements to the quick-paste tool [v-click],
along with several new cursor tool/mode indicators.
 
The UI has been improved/streamlined a handful subtle minor ways, and there are some bugfixes. 

For a full report, please review the changelog in the download. 


Files

NEXXT 3.6.0.zip 8.3 MB
13 days ago

Get NEXXT studio 3.6

NEXXT studio 3.6

Featureful NES assets studio based off the classic "NES Screen Tool". It's the "famitracker" of NES graphics.

Add NES Graphics Tool To Collection

More posts

See all posts

Comments

Log in with itch.io to leave a comment.

Uncle Dan12 days ago (6 edits)

There are some bugs when exporting *metasprite banks* VS *individual metasprite* to clipboard. When exporting individual metasprites, negative values are prefixed with a low byte operator, but it's not the case when exporting banks.

Front:
  .byte <- 8,<- 8,$00,0
  .byte    0,<- 8,$01,0
  .byte <- 8,   0,$10,0
  .byte    0,   0,$10,0|OAM_FLIP_H
  .byte $80

VS

Front:
   .byte - 8, - 8,$00,0
   .byte   0, - 8,$01,0
   .byte - 8,   0,$10,0
   .byte   0,   0,$10,0|OAM_FLIP_H
   .byte $80

This results in Error: Range error (-8 not in [0..255])

Also, when exporting individual sprites, animation data are not included. They are included when exporting banks, however the value often overflows. We get things like .byte 300.

For instance, with this Metasprite GnomeStillFront, I get .byte 300 as animation data.


Reply
FrankenGraphics12 days ago

Thanks for the detailed report!

I'll try resolving the low byte operator- and overflow issue at my earliest convenience. 

Animation data was originally not intended to be included with single metasprites as the animation scheme is considered "opt in" and a lot of projects out there assume their own scheme, but i can see if i can include some kind of setting for that where it makes sense. That might take a while longer. 

Reply
Uncle Dan12 days ago

I think it'll be easy to get our way around as it is now, so I don't see this as very urgent. Just a nice to fix, eventually. My overall experience of the app, even though ran through wine, is pretty good.

Reply
FrankenGraphics11 days ago(+1)

Once i'm done with the next release, you'll find the temporary settings here:


And the permanent (startup) counterpart will be found in the Preferences; text export tab:

Reply
FrankenGraphics11 days ago

i'm having trouble replicating the bug with the extra 0 / overflow on the duration. could you send me a session file where this is exhibited on your end? feel free to send it to Larsson . Ellen86 [at] gmail . com 

Reply
Uncle Dan5 days ago

I’m under then impression that the bug is caused by PAL value being included as 0 even though NTSC has been check.

For instance, this would result in 150.

Also the animation data should be on a new line. It is exported on the same line as the last byte which cause issues with the compiler.

Reply
FrankenGraphics4 days ago

It turned out to be something simpler. In some cases nexxt manually prints out a 0 to a string to concatenate with other things, this was a case of mistaken condition as it turned out. :) 

It's been resolved (and the new line too), but will be a little while before i push a new version.

Reply
OSZAR »