So, what's the status of V4? Well, here's a list of what I know to be not working in the 4.0b release.
- CLI mode is executable is broken. It's actually been broken since release, which suggests it isn't being used much. In any case, this should be fixed soon.
- XP support was broken. Hopefully this is fixed in current code (not released)
- Ruby 1.8/1.9 differences are causing problems. I'm investigating ways to fix this, but it's looking tricky.
- Anything using non-standard DLL extensions doesn't work.
- And some problems to do with bad emulation of the RGSS scripts.
The last three issues are caused because I'm just loading the Scripts file, and a lot of games appear to do loading and processing on load (rather than on game start). While I'd call it sloppy programming, not much that can be done about it, unfortunately. Hence, I'm considering another new loader. This will either be doing some very lightweight processing on the scripts to figure out the structure (without doing any processing - something that may work as I only require module/class names), or brute forcing the structure from Ruby error messages.
Expect a v4.0c release shortly to fix the first 2 issues, then something else later to fix the others.
This comment has been removed by the author.
ReplyDeleteHello! Can the new version of implement with codepage? We really need cp1251.
DeleteCan the new version of implement with choice codepage*
DeleteUm, I'm afraid not. I'm currently focused on getting VX Ace/XP support done. These games don't use codepages (well, they do a little, but not in an important way), so codepage support is not a current priority.
DeleteCodepage support is a tricky one, really. I have had builds which 'kind-of' enable it, but the resulting games tend to be quite unstable. In particular, cross-codepage patching simply doesn't work (so most games could go into English, or an English game to most other languages, but not, say, Japanese to Russian).
Further to these problems, there's no actual mechanism is place for specifying the code page of a patch, and the v2 patch format that 2k games use has no way of implementing one (without a break in compatibility). I'd kind of hope to get some progress on codepages done for the next major version of RPGMaker Trans (i.e. v5), which is when 2k games will get v3 patches (which do have the capability to store a codepage)
If you can't wait that long, then I'm afraid the only thing I can suggest is grabbing the source code and trying to add codepage support yourself. Or simply changing the codepage used in the source (search the files for cp932, and change it to the appropriate code page). Apologies.