I'm making a large scale game at the moment with a very large layout (16k x 16k). So far everything is running smoothly, but I notice now that I've added pathfinding to one enemy type, when the enemy is loaded into RAM for the first time, if the pathfinding is enabled on the sprite, it hangs for a few seconds. Then all of created sprites afterwards load instantly and everything is fine. If I turn off "enabled" on the sprite and load it for the first time, there is no fps hang.

I've tried setting obstacles to custom, and that seems to have helped, but there is still a small stutter on creation. Being that most of the enemies in this game will have some sort of pathfinding, is there a reason this is happening? Currently there aren't a lot of objects in the game (just 1 tilemap and maybe 100-200 sprites for testing purposes).

Asmodean & — - okay bad news...clearing the cache (ALL of it, too) did literally nothing. It still crashes out of memory...and my cache was only around 500 some mbs.

Asmodean & — - thank you both!! I will give this a shot, then.

— - hmm, that's really strange. When the vram is high, it's about 60-70 mbs (I have games on steam that is WELL over that). There's a decent bit going on, but I can't imagine it's anything out of the ordinary. I usually have a few tabs open on chrome, but nothing too much. The preview is generally always open as I work on it and then f4 to test new changes.

Is the cache only from my CURRENT session? Or is it a cumulative of everything I've been doing over the past however long it's been? Like I said, I NEVER had this problem with the C2 runtime. It could, of course, be coincidence, but I kind of doubt it.

— - does that mean something is wrong with my game? Will this happen when I export to NWJS?

Nepeo - yeah this seems similar to what we're doing. The only difference is that your repeat loops take MUCH less time (almost 1/10 of the time) as ours does in our game. In a brand new project, it's fine, but the second we loop through a 1k x 1k array, it hangs for around 10 seconds.

I've even tried doing this on an empty layout with no event sheet includes.

I think this is more of an Ashley question - is there any particular reason for that? There are some art assets in the game, but at an extremely small pixel scale.

Nepeo - I get a "Failed to Open Project. Check if it's a valid c3p project" when I import to c3.

Yes, I left the tilemap whatever default size it was when it imported; the actual tilemap in the game is 1k x 1k. We thought about doing small cells of loading as you needed them, but it still created a second or two hiccup in the game.

Nepeo

Ashley

So I've now gone back to my original project, and did the changes based on what Nepeo suggests, and instead of 27 seconds, it only takes 9-10 seconds! Which is a huge improvement, but I tried disabling every line of code except for the "for" loops, and it takes around 7-8 seconds just to process that many repeats.

It could be because there are now more events in play, but would there be another reason for this, Ashley?