Post by PepperSanders in RATTENKORPS comments

Viewing post in RATTENKORPS comments

I think I got it. I left a boot event on perpetual loop every frame, not usually an issue when working from the Bakin editor, but a horrendous problem for the player running from the .exe.

AND Bakin, boots up every single Common Event used in the game at startup, after caching the shaders and engine. Which is why I'm stuck at the 2min load, after the fix, which it still horrible, but not the 5min torture cycle I put you through.

I have to figure out how to resolve that, and get closer to your boot speed; I can't have players bail before the game even starts.

I spent the night playing other Bakin games, and that seems to be an unresolved and common issue, some worse than others. Especially bad in mine bc I automate a lot through the Common Event system.

Coyrestaurado16 days ago

Great, really great. I’ve been looking into it, and your engine actually does something interesting: the Common Events automate the global logic. Structurally, I’m not entirely sure how it works internally yet.

I was also checking the wiki:

28: Set the number of materials to “2” in Material Reduction.
29: Assign a texture atlas resolution.
30: “(!) Placing multiple models with large texture sizes on a Bakin map will affect the processing speed of the editor.” Please determine the size you need for your project.

And also this parameter:
float shadowmapScale; // Dynamic resolution of shadow map

Have you already experimented with these kinds of parameters?

Anyway, this is very good news. Just let me know whenever you want, and I’ll test it.
🧡🧡🧡

itch.io

Viewing post in RATTENKORPS comments