I haven't run into the createdata error, but if that's crashing out then that's an issue with the nwjs container, something is being sent to that API call that's causing problems. One way to test for that is to try a newer version of nwjs.
If you just replaced files in data then you didn't fix anything, you just made the KG version the original, if you replaced the images and they magically fixed the memory leaks then that simply proves my point, the bug is in the plugins I listed.
What probably happened if the old files don't cause a memory leak is that the new encoded ones hit a buggy codepath in the plugins that the old ones didn't, this is what we call an "intermittent" or "data related" bug. I'd have to unminify and step through the JS for the PIXI plugin, but the bug itself likely lies there.
Last edited:
Not sure who you're referring to, but I'm a programmer who is very familiar with low level coding, like bare metal no OS coding, so I'm very familiar with these kinds of bugs and can usually get a correct diagnosis of the root cause simply by looking through logs, printf debugging is pretty common for my type of programming.
Let it be known that I do absolutely blame KG for the state of this release, they should have checked their deployment before sending it off to steam. However, it's also the fault of the tooling itself for not being robust enough to provide checks for issues like this. Compilers have errors and warnings for exactly this reason, RPGM not having any kind of checks is a failing of the tool itself.
If pointing out things that are objectively verifiable is "white knighting" then sure I'm a white knight, but personally I prefer the term "pragmatic."
Last edited:
- Aug 3, 2017
- 823
- 501
Nope i didnt touch the images at all, I do this for a job ya know.
I will leave ya a clue on where the file i replaced was, and i will tell you KG touched something they didnt need to touch at all if they were doing a localization.
The clue is inside the JS folder , but it is not what you mentioned.
Its just habit of KG to touch things they shouldnt. Its no surprise that the skilled techs that KG had (who fixed the "newbies" mistakes) all jumped ship really to do their own things or work for other companies.
Also:
White Knight- a person or company making an acceptable counter-offer for a company; a person or thing that comes to someone's aid.
Oh, I'm absolutely not coming to KG's aid, they fucked up, royally. All I was doing was pointing out that the tools themselves *share* blame.
- Sep 15, 2020
- 137
- 31
That same mistake also happened to me with Winter Memories although it was only once, but it hurt me since I had to replay a large part of it for not having saved
blocked very early in the game by "UnknownError: the input is not a PNG file" in the compressed steam 1.01 version 
- Aug 3, 2017
- 823
- 501
I am pretty sure the compressed versions do have a disclaimer. something like:blocked very early in the game by "UnknownError: the input is not a PNG file" in the compressed steam 1.01 version
"This compression is unofficial. Use at your own risk. I sometimes don't test my compressions if I have too much to do.".
Last edited:
Funny. I got that in another game. Sometimes, either the game can't read non-PNGs, or some specific files HAVE to be PNG.blocked very early in the game by "UnknownError: the input is not a PNG file" in the compressed steam 1.01 version
Sorry to say I solved it by trial and error, had to have the originals at hand, ended up being the title screens. And some portrait images also had to be PNGs or they didn't show up and also didn't cause an error. Not sure if here it's the same issue.
now i'm getting the same error at the same place in the old compressed version...
...which btw is completely different and has actual png pictures!
now that's odd, guess i need to check both uncompressed ones
You sure? The compression tools tend to just make a WEBP and the rename it to a PNG, since nowadays most browsers support it. But remember you're dealing with an old-ish japanese engine.
- Aug 3, 2017
- 823
- 501
Its rpgmaker MV. Not exactly old, if anything its the most up to date engine.
- Aug 3, 2017
- 823
- 501
Ye, I know, but I mean in the webp support part. Some of its methods don't support webp, while some others do. It's why I said that in the other game, replacing the title images and standing portraits for their PNG versions, while racking up to 20% extra size, fixed the startup error and showed the portraits to begin with.
no, seems real png internally; also very old viewers were able to display them even animated
upd: ok, some interface pics (buttons, standing sprites) are internally webp but didn't cause problems
the worst thing is, the error doesn't even tell what file it doesn't like
started over of course, as it was in the very beginning anyway
Last edited:
- Aug 6, 2017
- 104
- 46
- Aug 5, 2023
- 1,328
- 2,672
You're right, it's strange that they haven't announced it on Discord. They usually always post what they fix. I suppose the list of errors was so long that they're embarrassed to announce it.
You must be registered to see the links
- Aug 3, 2017
- 823
- 501
I did mention it in the thread before the whole white knighting convo that happened.
And they did announce the patch on discord btw. People seem afraid to join KG discord. Its not like they can sniff out f95 users there.You're right, it's strange that they haven't announced it on Discord. They usually always post what they fix. I suppose the list of errors was so long that they're embarrassed to announce it.
You must be registered to see the links
And thats literally all that the patch does. Nothing else.
Sadly it doesnt fix anything. Some people have even worse issues now with the memory leaks and the various crashes.
Ofc this is most likely the last patch they will ever bother to release for this game.
The diferences:
The 1.13 version (based on the japanese version) is censored and obvious chatpgt MTL but you wont find any crashes or performance issues.
The steam version is uncensored , official english localized and still haz crashes and performance issues despise 2 patches. (its currently at 1.02).
So pick your poison on what version you prefer.