That doesn't seem to work on my laptop. Space make the MC cum and don't have a mouse. Also how do you collect bugs?Press space or mouse3 button.
That doesn't seem to work on my laptop. Space make the MC cum and don't have a mouse. Also how do you collect bugs?Press space or mouse3 button.
Click on mc portrait.That doesn't seem to work on my laptop. Space make the MC cum and don't have a mouse. Also how do you collect bugs?
Thank you!!Click on mc portrait.
Buy jelly at store, click on trees.
For me, when you in the room and outside it's lagging unless you're in conversation. The same thing happend on succumate too unless succumate lag comes when you go outside only.Okay, sorry I need to ask because I'm not seeing it (but I'm not running on Windows) is there a particular action where you see the lag?
Is it after running for some time? Is it when changing rooms? Or changing points on the map?
Basically where does it look the worst?
One more question, do you have chrome open along with the game?For me, when you in the room and outside it's lagging unless you're in conversation. The same thing happend on succumate too unless succumate lag comes when you go outside only.
It's just heavy like opening 100+ tab chrome.
No, because the lag will got worse when you opened chrome.One more question, do you have chrome open along with the game?
Yes for me both with your version and with the original.One more question, do you have chrome open along with the game?
Yes, but the issue is later versions of Chromium (which is the core of Chrome) tend to interfere with each other (contention over using the GPU to render web pages.)Yes for me both with your version and with the original.
Translation fixes.what is the difference between 2.02 and 2.03?
Awesome. Happy to test them and let you know.Yes, but the issue is later versions of Chromium (which is the core of Chrome) tend to interfere with each other (contention over using the GPU to render web pages.)
So as I see it, there are a couple of possible issues that could be going on. One is texture garbage collection, basically when a sprite (meaning a piece that moves) loads, it will pull the image from disk and store it in RAM (sometimes on the graphics card). When it is no longer visible, that is not immediately thrown away. The thought is, what if it is needed again soon, loading from disk is slow.
So textures are cached. If this cache isn't purged, the memory usage goes up and can bring a machine to a crawl.
PixiJS normally tracks how long it has been since it used a cached texture and cleans up anything that hasn't been touched for 60 seconds. The problem comes in, with things like map loads and such, a lot of sprites can expire at the same time. So you can inconsistent behavior of a lag point, followed by everything looking fine. (I need to look, but I don't think the RPGMaker core is using the cache efficiently.)
I was trying a more aggressive way of collecting the unused textures, which may use more CPU, but would lead to consistent behavior.
What this means is, since I can't reproduce the behavior myself, I'll need to build a set of test versions.
There are a number of moving parts here so I'm going to put together a few different versions, and I'm going to name them differently so it is obvious which version is which.
I should have the first of these tomorrow, as I've spent most of today fighting CMake.
what is the difference between 2.02 and 2.03?
diff -r -q Summer\ Memories\ 2.03 Summer\ Memories\ 2.02Translation fixes.