Yeah, that worked. Went back a few versions and I’m up and running. I would really like to have the latest though, so I don’t want to let Enscape off the hook.
Agreed. It’s been really unstable for me since that particular build. Even that one still has some issues and I might even revert back further. Don’t forget to file support tickets as much as possible. Mine typically don’t resolve anything, but at least I know logs get sent to the devs. that way.
@adam_heckman , I am sorry to hear about that. We have received your additional replies and the system information as requested (through your existing support case) yesterday, so you can also expect a further response very soon thereafter. Thank you as well for initially reaching out to the support team right away.
I had the exact same issue on multiple computers in my company and only the 4.2.1 version was still working for us.
However, I found the solution this morning while analyzing Windows events logs on my computer. The Windows event linked to the Enscape error message “Enscape could not start…” was about the MSVCP140 dll being defective.
So I downloaded and installed the lastest Microsoft Visual C++ Redistributable package to repair the dll. Now Enscape 4.4 (and 4.3) work again on all my computers.
For me, support found that I had broken links to material maps in my model. So Enscape couldn’t find them and would just crash. In particular, it seems missing Alpha masks were the culprit.
I’ve submitted an “idea” to the request portal, in hopes we can get some sort of official tool that can help users clean up the material panel to avoid such errors. Just using SketchUp’s built-in purge function (or even any plugins) won’t purge missing maps that aren’t just albedo/color.
I came across this same issue and I was told to wait for a 4.5 release.
Based on your errors and your explanation, you’re most likely encountering an “Unable to load DLL” error when they attempt to launch Enscape or submit feedback. The issue is that Enscape isn’t asking how to access the universal coding language stored on the computer correctly, so Enscape just crashes and burns. It has literally nothing to do with your computer and is, instead, 100% Enscape’s fault.
Unfortunately, we do not have a solution for this other than to revert to 4.2.1. If Enscape 4.2.1 works on your machine, please feel free to use it until our next release.
Hi @ValeroStudio , and everyone else just to make sure you’re aware, given the recent stability issues within the latest graphics card drivers (NVIDIA) these are the current specific prior versions we reccomend using for the time being:
Latest stable GPU drivers:
NVIDIA: 566.14
AMD: 25.3.1
Intel: 32.0.101.6130
If you’re already using that specific driver, please kindly make sure to also forward us a support report with logs so that we can investigate further. Thank you all for your cooperation!
I have tried just about every single thing in this thread and continue to have issues. My problems started when I updated to the newest NVIDIA update. I have tried uninstalling and reinstalling Enscape, I have tried several old versions of the NVIDIA driver including the suggested 566.14. I even tried Adam.Fairclough’s Microsoft links. Nothing is solving my problem. Does anyone have any other ideas?
As per our latest reply via the created support case of yours, please kindly submit us a fresh set of log files using the support button itself once more.
We’ll then be able to investigate the cause behind this issue further thereafter.
