RPGM Completed Sayaka's Addiction [v1.01 Steam] [Kedama Qube]

[antidotecrk]

Indeed, I am comparing the japanese version which i actually own with the KG version.And thus i asked you for these "missing files", because its more likely to be renamed files rather than "missing". Like i said people claiming about missing files and cut content do show up:
https://f95zone.to/threads/sayakas-addiction-v1-01-steam-kedama-qube.191879/post-16483145

But those people dont even own the game from proper sources, nor do know how to patch a game.

And right now idk about what errors you on about, i am talking about the createdata error which indeed crashes/closes the game and IS NOT related to any missing file.
But it is related to Kagura games Stupidity, as i just had to REPLACE a very specific file with the japanese version counterpart to fix it. (still testing it but for no i see no create data issues nor memory leaks that "always existed").

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.

 

[SlidingSubject]

First time I see an avid white knight in this forum.

 

[antidotecrk]

First time I see an avid white knight in this forum.

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."

 

[Maouhime]

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 is 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.

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.

 

[antidotecrk]

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.

 

[raizen23]

Definitivamente es peor. Causaron importantes pérdidas de memoria, por lo que cualquier escena (y la pantalla de estado) que use live2d puede bloquearse aleatoriamente.

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

 

[-dirtyoldman-]

blocked very early in the game by "UnknownError: the input is not a PNG file" in the compressed steam 1.01 version

 

[Maouhime]

blocked very early in the game by "UnknownError: the input is not a PNG file" in the compressed steam 1.01 version

I am pretty sure the compressed versions do have a disclaimer. something like:
"This compression is unofficial. Use at your own risk. I sometimes don't test my compressions if I have too much to do.".

 

[SlidingSubject]

blocked very early in the game by "UnknownError: the input is not a PNG file" in the compressed steam 1.01 version

Funny. I got that in another game. Sometimes, either the game can't read non-PNGs, or some specific files HAVE to be PNG.
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.

 

[-dirtyoldman-]

I am pretty sure the compressed versions do have a disclaimer. something like:
"This compression is unofficial. Use at your own risk. I sometimes don't test my compressions if I have too much to do.".

now i'm getting the same error at the same place in the old compressed version...

Funny. I got that in another game. Sometimes, either the game can't read non-PNGs, or some specific files HAVE to be PNG.
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.

...which btw is completely different and has actual png pictures!

now that's odd, guess i need to check both uncompressed ones

 

[SlidingSubject]

which btw is completely different and has actual png pictures!

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.

 

[Maouhime]

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.

Its rpgmaker MV. Not exactly old, if anything its the most up to date engine.

 

[Maouhime]

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 are not using the same save for both versions of the game i hope?

 

[SlidingSubject]

Its rpgmaker MV. Not exactly old, if anything its the most up to date engine.

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.

 

[-dirtyoldman-]

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.

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

You are not using the same save for both versions of the game i hope?

started over of course, as it was in the very beginning anyway

 

[FieneCanaria]

There's actually a new patch for the performance issues i guess? the game should be v1.02 now

 

[RemoraDFC]

I have Academy Nymphomania v1.13
I know it was renamed, but I dont know if I need to download this new steam friendly version since it is only v1.01

Anyone know?

 

[danadana]

There's actually a new patch for the performance issues i guess? the game should be v1.02 now

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

 

[Maouhime]

There's actually a new patch for the performance issues i guess? the game should be v1.02 now

I did mention it in the thread before the whole white knighting convo that happened.

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 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.


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.

I have Academy Nymphomania v1.13
I know it was renamed, but I dont know if I need to download this new steam friendly version since it is only v1.01

Anyone know?

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.

 

[danadana]

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.
View attachment 4665040

lol I declare myself legally blind, how the hell have I not been able to see that?
facepalm for me, I deserve it