If you see a window similar to the one above, the good news is that our crash reporter has detected the crash, and can help us diagnose the problem.
If the crash reporter gives you any additional information or instructions, please try to follow them.
If the instructions don't help, here are some possible reasons why the game might crash at startup:
We've noticed that sometimes game files get lost, for example fonts, textures, or meshes. Steam should normally download those files, but if it fails to do so for some reason, or if the files become damaged, for example due to a power failure, then Tiny Glade might crash or misbehave.
To fix damaged game files, use Steam's file integrity check or reinstall Tiny Glade.
Tiny Glade uses graphics technologies that some older drivers might not support. When the game detects an outdated driver, it will warn you at startup, and provide links to download the latest drivers for your hardware.
If the game doesn't give you links, you can use the following list, but you need to know which graphics hardware you own:
Sometimes graphics drivers can get in a weird state, and end up crashing Vulkan applications upon the simplest of queries. Here's some common scenarios:
Tiny Glade's crash reporter may tell you that you have software called "VulkanOn12" (a.k.a. "Dozen") in your system. Unless you're a developer, it shouldn't be there, but some laptop manufacturers have preinstalled it for their customers in error.
It is a "layer" from Microsoft that implements Vulkan on top of Direct3D12. Vulkan is the graphics API (application programming interface) that Tiny Glade uses, and Direct3D12 is another graphics API.
This layer doesn't play nicely with some graphics drivers (most often AMD). It is also not necessary, as your drivers most likely support Vulkan, and don't need this mapping.
As a result of you having this software, most likely all applications using Vulkan crash for you.
The good news is that you can remove it yourself, and we've been told by Microsoft and AMD developers that it is okay to do so. Still, it is your computer, and your choice.
Here's some more information about the mapping layers:
If you'd like to verify that "VulkanOn12" is actually installed on your computer, you can open a PowerShell console, and use the following command:
Get-AppxPackage -Name Microsoft.D3DMappingLayers
if you'd like to remove it, run the following PowerShell command as administrator (Open the Start menu, type Windows PowerShell, right-click Windows PowerShell, and then select Run as administrator). Make sure to use the entire command, including the part used in the previous step and the vertical pipe "|" symbol.
Get-AppxPackage -Name Microsoft.D3DMappingLayers | ForEach-Object { Remove-AppxPackage -Package $_.PackageFullName }
Older versions of OBS (Open Broadcaster Software) are known to crash Tiny Glade. OBS injects graphics hooks into other applications, affecting their rendering, and sometimes causing trouble. If you need OBS for streaming or recording of Tiny Glade, try updating OBS to the latest version. If you don't need OBS for Tiny Glade, you can selectively block the graphics hooks:
Run Tiny Glade using the "Launch Vulkan extension settings" option, untick "OBS" on the configuration screen, and press the "OK" button.
If you're using software that bundles and older version of OBS (for example Streamlabs Desktop), and none of the workarounds above are suitable, you could try upgrading just the graphics hook component of OBS:
data/obs-plugins/win-capture.graphics-hook64.dll into %ProgramData%\obs-studio-hook (typically: C:\ProgramData\obs-studio-hook),
This is not guaranteed to work, but fixes crashes specifically in Streamlabs Desktop 1.17.0.
To restore your previous version of the OBS graphics hook, simply delete graphics-hook64.dll in %ProgramData%\obs-studio-hook. OBS / Streamlabs Desktop / etc. will create it next time your launch it.
Sometimes everything runs fine, but then suddenly the graphics card hangs, and the game crashes. When this happens, Tiny Glade will notify you of the issue.
We've spent a long time investigating this problem (and we're still looking into it), but it is a tricky one, as it seems to happen for a tiny fraction of players, while during our development we've only seen it trigger once, and it promptly disappeared. We've been unable to reproduce it on our test hardware, no matter how many driver versions we try. So far we've failed to identify any bugs in our rendering code that could trigger this. This doesn't mean that our code is perfect, but during the investigations we've identified a few bugs in graphics drivers instead. We've been in contact with graphics vendors including NVIDIA and AMD. They've shipped a few fixes, but not for every one of suspected culprits.
The first thing that you could try is updating your graphics driver.
If this doesn't help, Tiny Glade has a few workarounds that you could try. Run Tiny Glade using the "Launch Vulkan extension settings" option, and scroll down to "Tiny Glade rendering workarounds":
Try checking all of the boxes, hit OK, and see if the game works now. If it does, try the "Vulkan extension settings" again, and disable one or more of the checkboxes. The workarounds come with a performance tax, so the idea would be to find the minimal set that still avoids the crash.
Please let us know what worked for you via the Steam forums, so we can improve this section, and provide better help 💛
If the game crashes for any other reason, we may need to investigate. If you accept the terms of our privacy policy and you're at least 13 years old, please send us the crash report when given the option by the Tiny Glade crash reporter tool.
The crash reporter will give you an alphanumerical code at the end. If you wish to discuss the crash with us in any online forums, please include this code. That way we can quickly look up the details in our database.
If for any reason you can't use the crash reporter, please share whatever information you can about your setup: which operating system you use, your graphics card model & driver, which version of the game you were running (full or demo), and what led up to the crash. Log files and crash dumps might be useful as well.
There's three places where Tiny Glade stores useful logs
tiny-glade.exe. You can find it by right-clicking Tiny Glade in your Steam Library, then from the context menu, selecting "Manage", and "Browse local files". Within, you shall find a folder called tmp, and within, crash_reporter_log.txt.tiny-glade.exe, inside tmp/panics.%USERPROFILE%\Saved Games\Tiny Glade\Steam\[your steam user id]\tmp\log.txt, which is usually something like C:\Users\Tom\Saved Games\Tiny Glade\Steam\123456789\tmp\log.txt.If you find any log files, they would be useful for us to help you troubleshoot. The log files contain primarily technical information, but please inspect their contents with a text editor, and if you're okay with posting them on the internet, please share them with us via Steam forums. You're of course welcome to remove any information you deem sensitive.
Windows has a built-in mechanism for capturing and automatically saving crash data. It is automatically saved to %LOCALAPPDATA%\CrashDumps. If you enter that path in File Explorer's location bar, it should bring you to a folder with probably a few .dmp files. If there's any with tiny-glade in the name, they will likely have some hints as to what's going on. We can load those files into a debugger, and try to diagnose the issue.
The .dmp files may contain some information about your operating system and its parameters, so it's best not to share them publicly. Please reach out to us via Steam forums, and let us know that you have crash dump files.