I can't get this error to occur again (thankfully), but the first time I tried running this on my laptop, none of the tiles after the exterior scene at the beginning rendered properly, only the player character and the critter at the front desk were displayed.
The log file located at /AppData/Roaming/Clockwork Manor/logs/godot.log is insanely large (3.4 GB). Here's the beginning of it it:
Godot Engine v4.0.rc6.official.0cd148313 - https://godotengine.org Vulkan API 1.3.215 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics 620 USER ERROR: Condition "slot >= slot_max" is true. Returning: nullptr at: get_instance (./core/object/object.h:972) USER WARNING: Setting autoplay after the node has been added to the scene has no effect. at: set_autoplay (scene/2d/animated_sprite_2d.cpp:433) USER WARNING: Setting autoplay after the node has been added to the scene has no effect. at: set_autoplay (scene/2d/animated_sprite_2d.cpp:433) USER ERROR: Cannot remove TileSet atlas source. No tileset atlas source with id 2. at: remove_source (scene/resources/tile_set.cpp:494) USER ERROR: Cannot remove TileSet atlas source. No tileset atlas source with id 2. at: remove_source (scene/resources/tile_set.cpp:494) USER ERROR: Cannot remove TileSet atlas source. No tileset atlas source with id 2. at: remove_source (scene/resources/tile_set.cpp:494) USER ERROR: Cannot remove TileSet atlas source. No tileset atlas source with id 2. at: remove_source (scene/resources/tile_set.cpp:494) USER ERROR: Cannot remove TileSet atlas source. No tileset atlas source with id 2. at: remove_source (scene/resources/tile_set.cpp:494) USER ERROR: Cannot remove TileSet atlas source. No tileset atlas source with id 2. at: remove_source (scene/resources/tile_set.cpp:494)It continues like this, repeating the "USER ERROR" line over and over.
Trying to run the game again a few days later, it now works as expected, with a much more reasonably sized log file, haha.
It's not impacting me anymore, but I figured I'd tell you just in case it comes up for anyone else, and possibly to let anyone else experiencing the same issue know to delete their log file.