Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(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.


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. 

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.

(+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:

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 

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.

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.