Friday, 28 February 2014

Bugs and stuff

First off, as people apparently cannot google/read previous comments anymore, this:

IF YOU ARE MISSING MSVCR100.DLL INSTALL THE MS VC++ REDISTRIBUTABLE HERE: http://www.microsoft.com/en-us/download/details.aspx?id=26999

Now that's out of the way - for the people with error in Pythons multiprocessing libraries (the one that ends with "TypeError: WriteFile() argument 1 must be integer, not None"): thanks for the system specs. One thing I notices is that you're running Core i7s which have 8 threads, which leads me to think that RPGMaker Trans is going too parallel for Windows to handle. Hence the next version of RPGMaker Trans will have a limit on the number of processes it uses, and hopefully that will be a cure.

As to me testing this out: I don't have a Windows machine with an 8 thread processor in, so that could be tricky. I'll see if I can set something up, but there's a very high chance that'll I'll be working blind on this one.

ETA on RPGMaker Trans 2.01: Sunday/Monday morning 

EDIT: I've managed to do some testing and managed to produce a similar (although not entirely the same) bug, so I'm pretty certain that this is related to Python spawning too many processes on systems with a high thread count. The reason for this is due to some default behavior in Python that I wasn't aware of (specifically multiprocessing.pool does not spin up processes as necessary, but by default starts one process for each hardware thread). The fix is a bit more involved than I thought, but should be done shortly. It wasn't caught before because testing is on a 2 core VM, which doesn't exhibit this problem. 

EDIT2: And it wasn't that... it seems to be a more fundamental bug in Python, but it's fixed anyway.

Wednesday, 26 February 2014

On version 1.99

Seeing as a few people have commented "it worked on 1.99" now...

v1.99 is not coming back. The codebase is unmaintainable, I do not have the time or inclination to maintain it, and I am unable to open source it. It doesn't have the architectural features that I need for new features. Further, it was announced very early on that v1.99 would be killed off and I did ask people to test v2. Unfortunately, very few people did.

If more people had tested v2, then I'm pretty certain that all the bugs would be ironed out by now. That isn't the case. I fully intend to get v2 bug free, but that will take time. Until then, people will have to put up with bugs, because if I put v1.99 back out I won't get the bug reports I need to fix v2. To anyone who doesn't like this policy: sorry, but that's tough on you, I guess. If I could get bug reports for v2 any other way, I would. But no-one wanted to engage with the beta testing report unless they were one of the people who couldn't use v1.99.

So in summary: v1.99 is gone, and it isn't coming back.

Sunday, 9 February 2014

RPGMaker Trans v2 Final

Well, it took a little bit longer than I thought due to some last minute bugs, but RPGMaker Trans v2 is out. In theory, this should fix the errors that people have been encountering. It should also work with networked file systems, but that's not a tested feature.

Next features:
  1. Compiling with Nuitka: This should fix the CLI mode and give a speed boost.
  2. RPGMaker VX support: Still at the parsing Ruby problem...
  3. Non-ASCII locale support: Still working on finding all the places where files can be referenced in 2k files...
  4. Patch Errors: Mainly for translators; the current handling of problems with patches is less than optimal. Patch errors will simply allow proper reporting of problems in patches.