Few bugs etc.

Samarium

After testing, the samplemap and samplemap2 maps work on Chrome on my side

Edit: it can be related to the size of the map

dezet994

Hmm, probably i messed something up. ;P

dezet994

Sometimes game crashes while colliding with circle block. Console returns "toPolygon() is not a function" in Hit.js:

testPolyCollision(type, hit1, hit2) {
        let collided = false;
        switch (type) {
            case 'box':
                collided = sat_1.default.testPolygonPolygon(hit1.toPolygon(), hit2.toPolygon());
                break;
            case 'circle':
                collided = sat_1.default.testPolygonCircle(hit1.toPolygon(), hit2);
                break;
            case 'polygon':
                collided = sat_1.default.testPolygonPolygon(hit1, hit2.toPolygon());
                break;
        }
        return collided;
    }

Ps: side question to not open a new thread. I would like to know if you could (and are going to) optimize somehow big map lag in the closest future? Once again, i'm not pushing, i just want to know if there is a point to make larger maps 😉

Samarium

Thanks for the feedback.
For the big maps, I have to find the problem first.
If it's related to the server reconciliation, then the problem will be fixed soon. If not, it will take more time

dezet994

Samarium Thanks bro 🙂
Please, let me know when you will know something, regardless the outcome.

dezet994

I didn't notice before, but problem happens only during the movement.
video

It also doesn't happen in left-top corner (idk why), but the closer to the middle i'm getting, the worse lags.

Edit:// Actually it depends from start position. If i'll put start in the middle, game works quickly in the middle. The further from start point i get, te bigger lags during walk i get. What's also interesting, every time i will return to area of starting point, game starts to work quickly again.

Samarium

I don't think the problem is related to the size of the map but to code instructions that slow down the processor.
With you in onInput loops that run on character movement?

dezet994

Hey, i commented out all onInput methods, without success.
Anyway, i have 8 cores 16 threads ryzen overclocked to 4 ghz, i don't think it's cpu issue.

dezet994

Ehh, i found a solution... Quite stupid of me 😃
In onChanges (RpgSprite) i called a method without verifying if data really changed, so it was called few times per step... ;D

Anyway, thanks again for support. 🙂
Btw, maybe you should limit calling the onChanges method to x times per second?

Samarium

In fact, onChanges is called every time the player's property changes. Here, it was the X and Y positions

Anyway, it shows that the size of the map was not the problem here 😉
I remove from the bug list 😄

dezet994

Yea, i didn't really expect this, as i'm always trying to check stuff like this. Anyway, consider throttling it a little bit. If we have around 30 NPCs on the map + each tile has for example 32x32, then onChanges caused by random movements might be called too often 😉 Actually i never seen anything on my PC to get so laggy so far, so i think it's worth attention 😃

Look at the video - it's just 2 NPCs on this map.

Edit:// With 30 NPCs on the map there is a huge lag between client and server. Also NPCs movement gets weird, instead of whole tile they go few pixels and change direction, although here i'm not sure if it's not something on my side.

Samarium

Yes, the benchmarks show the same thing. In fact, the number of events on a map takes performance.
It is mainly because of the collision searches on the other events that cause lags.
I've thought about several points to remedy this, which theoretically would allow not to be blocked by the number of events on a map

dezet994

Maybe, i didn't finish my map so i've got no ready collisions. But the fact, that onChanges method is triggered ~ 30 times during one tile step done by NPC needs attention 😉 Throttling it will definitely increse performance and probably remove lag/jump between client server

dezet994

Another one: I think in documentation (https://docs.rpgjs.dev/classes/client-engine.html#rpgenginehooks) instead of RpgEngineHooks should be RpgClientEngineHooks