Heya Fuzzies.
It’s pudding here again. I may be on my short game development break but I’ve been considering making this post since the original FuzzBoob’s release.
How did Five Nights at FuzzBoob’s begin?
Glazed had always wanted to work on FNAFBoobs for many years now. And he finally bit the bullet when he found someone to help him make it.
Neither him or this other person had made a game before, so Glazed did what he knows best: creating quality art with his shockingly fast speed.
Fast forward a year and a bit, I hear news from Proteins (link in credits) that there was someone making a game.
I was put in the team as a co-developer. I was excited to work on my first non-university proj-
It was a fucking mess.
It’s not entirely Glazed’s fault as he hadn’t made a game before, but he hadn’t done research either.
Every. Single. Asset. And. Variation. Was. It’s. Own. Image. At. Absurd. Resolutions.
The assets were around 8K resolution each, which had immense Ram and Filesize cost.
And by ‘It’s Own Image’ I mean the office itself had far too many large images:
- Office with BlackOut
- Office with lights Out
- Office with Left light on and Right light off
- Office with Left light on, Left door shut, Right light off
- Office with Left light off, Left door shut, Right light off
- Office with Left light on, Bonnie at door, Right light off
- Office with Left light on, Bonnie at door, Left door shut, Right light off.
- Office with Left light off, Right light on
- Office with Left light on, Right light on
- Office with Left light on, Right light on, Right door shut.
- Office with Left light on, Left door shut, Right light off, Right door shut.
- Etc etc. Hope this proves the point as there’s a lot more.
It wasn’t just the office. Even the cams had this too.
- Stage with Freddy, Bonnie, Chica
- Stage with Freddy, Chica
- Stage with Freddy
- Stage Empty
- Stage with Freddy, Bonnie
- Stage with Bonnie, Chica
- Stage with Bonnie
- Stage with Chica
And this carried on for all the other cams, the worst one being Foxy’s Cove with how many Bonnie Sign Variations there are.
But if they were images, how do they animate now?
Early on during FuzzBoob’s Classic development, I took over as the developer as I knew how to handle assets.
I got him to separate all the assets, and helped remake some.
So the Assets became like:
- Office Main
- Left door
- Right door
- Outer office Left Light
- Outer office Left Light Bonnie
- Outer office Right Light
- Outer office Right Light Chica
- Office buttons, etc.
and
- Freddy
- Bonnie
- Chica
- Stage
And this was a drastic change. The original source files went from 16gb to about 1gb.
But what about the Absurd resolutions?
When I was working with the Unity version, it allowed you to resize the assets on import, and place them into a Sprite Atlas which also enabled you to apply Crunch Compression.
However, this looked like shit.
If you compare FuzzBoobs to FuzzBoobs: DE, you can notice the original looks like shit.
In the Godot Definitive edition release, I didn’t have the luxury of resizing on import. So I went through and resized as many assets I could to fit in 1440p resolution. Not every thing got fully resized as there are a lot of frames in here. If I went any lower, it would have looked bad.
However, there was complaints of the game being poorly optimised. This is because I hadn’t found out you can create sprite atlases on Godot, as it is not in the documentation. But, since the assets are a lot bigger, these atlases are huge, some stretching up to 16k resolution. However, it reduced the draw calls for each individual image and majorly reduced crashing as overall it is technically less.
For the majority, this minor change adjusted the opinion to “It works great”.
But now we’re in the position of not *every* hardware can load these images. I believe this is why some people see Black or nothing instead of the images.
Can anything be done to improve?
As of version 1.1.0, I’ve implemented a few tricks to help computers run this game. Such as:
- The ability to reduce Asynchronous loading. I created a system that allows me to begin loading scenes early. For example, when you click the buttons in the menu, the game immediately begins loading the next scene as it fades to black. However, for some computers two scenes are too much. Reduce Asynchronous Loading helps by waiting until the scene fades out, fully unloading the previous scene, and then loading the next scene. It’s why the load times are longer, but reduces crashes for others.
- Light compression. The assets now have a compression technique similar to Jpeg on their main atlas. This is almost indistinguishable but also reduces the ram usage heavily.
I’m going to look into seeing what can be resized more without hurting the quality too hard when I get back into developing this game.
However, I will not let this situation occur for future games I create. There was not much that could be done for FuzzBoob’s as I had joined late in terms of asset creation.
For those who want to make a game: Do research into assets before creating them. And use sprite sheets / sprite atlases whenever you can to reduce draw calls.
Finally,
i apologise for this rant thing. No one is at fault here.
I don’t know how much I can do to fix this game’s problem.
I’ve done as much as I’ve can do currently, but this issue will not stop plaguing FuzzBoobs. This issue carries over to FuzzBoob’s DE Part 2 unfortunately.
and I hope you guys stick around for my other projects. This problem has been troubling me, and I wanted to be transparent about it.
If you have a question about this, feel free to leave a comment here or @twistcumet Glazed’s discord. I read each comment here.