I have a glitch for you:
Editing anything in the Preferences box, even just the Animation type, then saving, obliterates the image.
Not just this, the editor seems to think that 00 is still the free space byte, when it's actually FF. (Using BPRE)
I have found a Bug. IF I edit the text box of Fire Red, in game it Restart or hang.
I have a problem with this tool. Everytime I open it. This thing always pops up.
" Application failed to intialize properly. (0xc0000135) "
Help? ;X
Yes, it's finally here!Update NSE 1.7-
Yay, it's finally here XD
- Fixed some bugs
- An overall speedup
- Better, faster free space finding
- More dynamics added to bookmarks, (Image lengths, more dynamic pointers, support for LZ bookmarks)
- LZ Decompression and Re-compression on both images and palettes
- Re-point compressed images and palettes, NSE will search for and change any referencing pointers
- Automatically finds free-space or do it yourself in Advanced Mode
----------![]()
![]()
![]()
Get this dialog (above) by switching to Advanced mode,
or let NSE do it automatically! (Applies to both images and palettes)
Note(S): What this means-
This does not mean that you can change the size of compressed images,
-But rather means that you can edit the image and palette inside of NSE, export and import bitmaps, and a ton of other things.
I highly recommend you bookmark anything you re-point , so you don't forget the offset.
Yes, it's finally here!
Two things though:
What about images that are decompressed, but have a compressed palette? Or vice-versa? Maybe you could combine both offset browsing boxes and put checkmarks to determine whether one or the other is compressed (or not).
Second, you have a spelling mistake (Auto-abort if data is to big, should be too big).
That feature is cool!- NSE automatically checks what exactly it is your looking at/for.
It knows if a palette is compressed. It knows if an image is compressed.
It just knows... spooky:paranoid:
And yes, you can mix and match compressed and uncompressed images and palettes.
![]()
Whoops... :knockedou
Sorry for the spelling issue. My bad,
and after all the work I put into this update... cries.
That feature is cool!
And no worries, it's just one letter. The same exact mistake was made in un-LZ (Compressed size is: 0xYYY. Which is to big. Aborting.)
lol, it pains me how common that mistake is D:
anyways, might i suggest something to you?
if/when an image is repointed, you should also over-write the old image with the "FF" byte, as to preserve free-space.
tucking
fypos
hurn ni bell!