Open DaZombieKiller opened 9 years ago
Did you set locale to be en_US.UTF-16? (IIRC that is the default one for jast usa rel. Can't check now, am at uni >.<)
Not much of an improvement:
Did you extract it with correct locale?
I actually extracted it with Steins;Gate Archive Decompiler, and when I try to extract it with npaextract (locale en_US.UTF-16), the output is... well, strange.
If I don't supply a locale, it attempts to write to paths like "n s s / s y s _ t i t l e . n s b", thus only the last file actually gets extracted (in the form of a file called "n" with no extension)
I suspect that nptools is windows-unfriendly (it generates ja_JP.UTF-8 output, and was only tested on linux). It shouldn't be too hard to fix. I will look into it later today.
Alright, thanks. In that case I should note that there were specific changes I had to make to the CMakeLists files, and a few changes to the source files themselves in order to get it to compile under MinGW32. I'll see if I can get a pull request together later.
I should also note that nsbcompile2 doesn't seem to work, I get a "syntax error" when I try to compile scripts from the original Japanese version that I've decompiled.
Or en_US.UTF-8 output... i forgot xD
nsbcompile2 is an experimental tool for development purposes only, broken on most original scripts (bison probably fails on either array syntax or "select" event loops), works only on trivial custom scripts. I haven't bothered to fix it yet because i use it only on steins-gate/test.nss.
Any updates?
I don't use windows so it's difficult for me to tackle this. I'm pretty sure it works fine on linux.
When using nsbparse2 with nsb scripts from the JAST USA release of Steins;Gate, the scripts do not get decompiled properly: