DC callback error

shawb · 20 Dec 2016, 11:35

Help please!

I am running SU 2015, 2016 & 2017 (all Pro, Windows 10) and am now getting the attached error messages on all three versions when using the Component attribute & Options dialogue boxes. I have tried using example DCs from the DC training collection as well as simple DCs of my own. They all seem to work ok in unsaved new files but after a 'Save as' the error messages appear.

This was happening after I installed SU2017 and I followed the advice of the time to install the latest DC extension in the earlier versions. I haven't used any DCs until now (and am very much a newbie with DCs). Has anyone else been experiencing this issue?

Garry K · 20 Dec 2016, 13:22

Update your Dynamic Components for each version of Sketchup to the latest version 1.4.2

shawb · 20 Dec 2016, 13:30

Thanks for your reply Garry, I have indeed already updated as you suggest. I can add that in an unsaved file each DC shows in the attribute dialogue but not in the DC options panel.

shawb · 24 Jan 2017, 11:56

An update.

The cause of this problem appears to be a folder or filename starting with a lowercase 'u'. I am grateful to the person who described this on this or another forum (couldn't find the post again) and Yogesh at SU support.

I didn't think this was what was causing the problem on my setup as I knew that I never name files or folders with lowercase letters. However, the culprit was further up the file path in the C:\ directory thus: C:\ Users\ user. It was this last folder name with its lowercase 'u' that was at the heart of the problem. How the folder came to be there (in the SU file path) I do not know. I think I probably messed up right at the start when naming my desktop account on the new PC (three years ago now).

My solution has been to do a reset of the whole PC, which it needed anyway, and then being careful about names and file paths. SU support say they accept this problem as a known bug so there may be a fix at some point without going to the lengths of resetting or meddling with the PC inner workings.

Hope this may explain what is happening for anyone else who has the problem but apologies for not being able to offer a quick fix.