[RMXP] "RGSS Player is not responding": My game only works when it feels like it.

[CarlosDavilla]

Greetings.
So, I've been having this problem for a couple of weeks now.
For some reason, at random, regardless if I start it on playtest mode or not, my game simply refuses to open. It keeps loading forever and when I click on the window it says "RGSS Player stopped working".
But the weird thing is, sometime later (could be minutes or hours), it gets back to working again, like it never had any problems.
It seems that my project only works when it feels like it.
The only thing that mitigates this problem is when I restart my computer, then, the project works again but only for a short time.

That's the only thing I see most of the time. The debug console never says anything.​

Details about my project:

• It's being shared on a Dropbox account (since I'm developing this game with another person);
• Contains extra folders (used to store some development things, like sounds and pictures);
• Contains extra scripts;
• Is using DLLs besides the RGSS104E.dll;
• I'm using MapMaker to take screenshots from the maps, so it stays inside the project folder alongside its dll (RGSS102E);
• There is no antivirus blocking the interpreter (Game.exe) or the project's folder.

I've already tried:

• Restarting my computer (as I said, it only works for a short time);
• Uninstalling RPG Maker XP and then installing it again (the project stays the same, so I believe it's not the editor's fault);
• That method where you put the RGSS Player on the Data Execution Prevention (DEP) list (not only it doesn't work, but for some reason, it impedes other RPG Maker XP games from launching);
• Running the game/editor as administrator(does nothing);
• Running the game/editor in compatibility mode (does nothing);
• Removing MapMaker from the folder and its DLL (does nothing);
• Changing the interpreter (Game.exe) for a new one (does nothing);
• Stop syncing the project's folder on Dropbox (does nothing).

My computer specs:

• Processor Intel Core i7 7700 Kaby Lake 3.60 GHz
• Motherboard MSI H110M PRO-VH PLUS
• RAM HyperX 16gb (2x8) DDR4 1196MHz
• SSD Patriot Burst 120 gb
• SSD KingSpec 960 gb
• HDD Seagate Barracuda 1tb
• Graphics Card ZOTAC GTX 1060 6gb
• Windows 10 Pro 64-Bit

Spoiler: Aditional Info

How the project's folder looks like on a file explorer.

My complete list of scripts at the moment. Removing the ones below Main does nothing.

Here's what it says on Windows Event Viewer.

It looks like I can open other projects and make new ones.

Is there anything I can do to stop this from happening? I believe it could be the scripts, but I find it very weird for them to make the game only work "sometimes".
Would someone be able to help me? I really need to solve this problem, otherwise, I won't be able to develop this game.

Thanks in advance.

 

[AkiraKotatsuhime]

That's quite a big ton of additional third-party code running there nobody could possibly know all of.

The cause of this could be almost everything, but it's strange it doesn't hang at every run. Try to turn off as many scripts as possible when you encounter this problem the next time at game's launch. If it starts afterwards, better test a second and third time to be sure. Repeat this with more and more scripts reactivated, and yes, this process will take some time.

=begin
Just add "=begin" and "=end".
Nothing inside this will ever execute.
Later, undo this change.
=end

If all the text inside a script turns green, you did right. But be careful to not leave scripts active that need others you have deactivated or it might crash. Also, the order of scripts in the list can become a very big problem since they may get in eachother's way by replacing or extending the same functions.

Also, scripts below [MAIN] will never run. The game enters its main-loop there until reset or close.

When you think you've isolated the script causing this, we can continue with analyzing it.

～炬燵あ

 

[CarlosDavilla]

I'll give this a try, Akira.
The project is working for now, so I'll have to wait until it starts acting up again. Thank you for the suggestion.
I'll come back once I have some results.

 

[CarlosDavilla]

Well, using Akira's method, I disabled every single third-party script I'm using, five at a time, and I believe I managed to find the culprit.
It was a script called Memory Font Loader by ForeverZer0.

I don't know why, but when I disabled it, the game came back to life. When I enabled it again, the game hung up once more.
I don't know if there's more to it, so I'm not going to mark it as solved. Probably will wait at least a week to see if it was just this script.
Regardless, thank you so much for your help, Akira. I really appreciate it.
It was a rather simple solution. Don't know why I didn't try this before, but oh well, it worked nonetheless.

Cheers.

 

[AkiraKotatsuhime]

Your link leads to "Dynamic Gardening", but I managed to find the correct thread.

"Memory Font Loader" seems to notify all currently running applications that the font-resources pool cached temporarily may have changed. I don't have that much experience with SendMessage and I'm a bit confused why it also calls SendNotifyMessage with the same data. There might be some window anywhere, even outside the game-engine, that doesn't properly handle WM_FONTCHANGE and makes this entire procedure hangup because either the S or SN one waits for every target responding to it.

Relying on direct access to WindowsAPI functions inside (old) Ruby sadly never guarantees to work on every PC as intended. Indeed this wouldn't be the first time that some fonts-related script causes big trouble for some players, but not everyone (in this case: even the dev) and nobody knows exactly why.

Not being able to temporarily use fonts from a folder is a big flaw in RPGXP's RGSS, that's something they should have considered to do with an update after RPGVX (+Ace) added this useful feature. °~°'

～炬燵あ

 

[CarlosDavilla]

It has been over a week at this point, and the problem caused by F0's script didn't reappear, so I guess this was the only reason this was happening after all.
Thank you very, very much once again for the fix suggestion once again, Akira.

This thread can now be closed.

 

[Shaz]

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.