Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Wonder Workshop

13
Posts
2,659
Followers
A member registered Mar 09, 2026 · View creator page →

Creator of

Recent community posts

That's rather odd. While we're not quite sure how to replicate that bug (let alone why it's doing that), we'll try to find ways to mitigate it in the next update.

We've debugged this very same issue with someone else, and unfortunately, we've determined that this seems to most likely be a graphics-driver-related issue, in that specific older hardware seemingly doesn't play nice with Godot's OpenGL implementation.

Unfortunately, we have no real way of fixing this, but a potential workaround would be running the Vulkan ".bat" file, which forces the game to run with Vulkan instead of OpenGL. Have you tried that?

Harassment towards our team members will not be tolerated. Please speak respectfully, or you will no longer be welcome on this page.

While we would love to help you, we cannot feasibly provide any helpful feedback unless if you clarify certain hardware specifics.

For instance, can you give us any detail on your phone's hardware? The specific phone model would probably be the most helpful. It's entirely possible that your phone could have insufficient hardware or old software-related issues.

We have now replaced the Vulkan executable with a batch script, which should ideally prevent it from being falsely detected as a virus in the future.

(1 edit)

Adding on to BlackHail's statement, we have now replaced the Vulkan executable with a batch script, which should ideally prevent it from being falsely detected as a virus in the future.

(2 edits)

Version 0.3.6. It should be referenced in the post above you.

Upon beating the second night, you should have access to the third one.

The soundtrack was purchased from Purple Planet Music. Specifically, the tracks Horror Playhouse, Lost Souls, and Clown Around.

Ah, it seems that certain textures are still failing to load on certain hardware. That's rather bothersome. We'll try yet again to fix that whenever the next update rolls around.

Apologies, I think there was some misunderstanding regarding what those "black squares" were. There were bizarre accusations of censorship in the past due to the player's willy in loss scenes being depicted as a generic black rod.

But anyway, if you're coming across randomly placed black squares in animations, that is most likely unintended. Can you send us a screenshot of this visual error so that we can get an idea of what you're dealing with?

(1 edit)

Lead (and only) programmer here (@janky_dev). Like how BlackHail said, jumpscare animation issues, largely from it failing to load.

You see, I'm an idiot that loves texture atlases, AKA sprite sheets. A lot of the game's graphics use them, especially jumpscare animations, which use big ones. Turns out that they just, well, fail to load on certain builds if you make them too big, especially on 32-bit exports, which is what our Windows release is on for compatibility's sake. I heard it may be due to some internal memory address issues that allegedly occur in 32-bit Godot games with huge files that cause them to fail to load, but I don't know enough details about the subject to truly verify that.

Anyway, I went through a lot of effort into making sure that the sprite atlases for jumpscares were as small as I could make 'em for the Night 1 build. And they worked! The jumpscares ran, so we released the game in that state.

...At least I thought they worked, and for most people, it did! Unfortunately, as it turns out, they still cause problems on certain machines, and even just... fail to load randomly, even on my machine. The camera monitor and even the game itself fails to load on certain machines, likely due to the texture atlases they use being too big.

So, I kind of bit the bullet and manually split the atlases into multiple smaller ones so that they're at a much more manageable size. This fix will be publicly implemented during Night 2's release, and hopefully should solve a lot of crashes.

Lead (and only) programmer here. While our loading of jumpscares does have technical problems that we plan on hopefully patching out in the next public release (the jumpscare scene sometimes fails to load at all), I'll admit that this bug of yours particularly puzzles me.

The jumpscare here clearly loads, but, judging from your description, it only plays a snippet of it, while also being horribly cropped. I admittedly have no idea as to how or why the game on your machine is acting like this, and I have never heard this happening from anyone else. Can you please tell me what you're running this game on?

Not sure why that isn't working. I'd like to say that this a shader issue, but if it was, I don't think you'd be able to view anything on the tablet, so the inconsistency in its presentation puzzles me...

I can only assume that there's something wrong going on behind the scene with loading certain resources, like the scene that holds the camera images and the monitor overlay. That is all automatically done by the Godot engine itself though, so even if that was the problem, I'm not sure how I'd go about fixing that, especially with how this seems to be a unique issue for your computer. Are you sure that your computer has enough memory while running this?