I have a Sketchup model with Enscape people in it that were previously working fine. Now only half of them are visible in Sketchup, but not in Enscape. Newly placed assets don’t show up in Enscape now either. I could only find this issue referred to on PC’s on here, not Macs. The solution was to delete some sort of temp asset file, but I need to know if this is the same on a Mac, and where to locate the file that I need to delete. Please help quick - on a deadline and don’t need this happenening now!!
I am sorry to hear about this of course - As per my other reply to you please kindly reach out to our dedicated support team and you will be assisted soon after we’ve troubleshooted the exact cause behind this.
Ok, but can you tell me where to find the temp file anyway? May as well try that first.
I’m afraid Enscape for Mac does not access a dedicated temp folder like the one used on Windows-based machines (including for assets). After we’ve received your report though (including log files ideally) we will be able to analyse the exact cause behind this and assist you accordingly.
Report sent.
I have this problem today. Did you find a fix?
I tried a few different things, including re-downloading the Enscape asset content to a new folder, but that had no effect for me. I can’t say this will work, but what fixed it for me was this from Enscape’s tech support:
“Sometimes, installations and usage can behave unexpected and be solved by granting full disk access to Enscape and the CAD in the system settings. To do this, close all applications and open the System Settings. Then navigate to Privacy & Security → Full Disk Access. There should be at least one entry for Enscape and the CAD. Flip the switch on all of them to allow full disk access followed by entering the admin password. This might be necessary in very unusual cases so that Enscape can exchange data with the CAD software, even on a very basic level. Restart the Mac after this and check again.”
Hope that helps you and anyone else in the same boat.
Thanks for the reply. It seemed to self correct when I shut the Mac down and restarted. It must have been to do with the memory cache similar to the Windows solution.