New behaviour.
-
also I was thinking about any basic cleaning of this kind already - just to make it clearer for me and for not to run into the same issue - have you uninstalled the older versions which were so far executable installed? or have you done any manual cleanings in the data directorys?
You wrote "...now I cannot import skp files at all without a catastrophic crash" - so SkUp2019 at least opens and works without problems as long as you don't use "import" ? -
I have uninstalled the prior versions apart from the two I mentioned and searched for orphaned files. I also made sure that files were associated with sketchup 2019.
I cannot view the thumbnails and cannot import skp files but I can import autocad and collada files which makes things interesting. I can only believe it is a new bahaviour or another corrupt bloody model file. I am going through my other models which I can open and check to see if the import problem persists across the board which is time consuming but what else can I do?
-
Did you run the v2019 installer exe file correctly ?
Try this...
Close SketchUp [and/or Layout] whilst logged into Windows as your normal user-account name.
Find the relevant SketchUp installer's exe file - in Downloads ?
Select its icon and choose "Run as administrator".
When prompted choose 'Repair'.
When it completes restart SketchUp and see if that helped.Running a complex app's installer's exe file in any other way will cause all kinds of unpredictable and unexpected weirdness - often around permissions, file/folder accessibility, saving settings/preferences etc - so never double-click the exe file's icon to 'Run' it, even if you have admin-powers it is not the same thing !
-
Thanks mate, done that a few times now, I am leaning towards some kind of problem with the file. All my models are stored on drive 'D' my second hdd but still installed direct to the MB and inside the PC case.
-
Working on SKP files other than where SketchUp is installed [usually C:] can cause weird issues,
Copying the SKP files onto the
drive to work on and saving changes there, and then finally saving them when the work is all done onto the 
drive would be recommended - however, at least it's probably better that saving to a memory-stick or somewhere like 'DropBox' ! -
Most of the time drive 'D' is fine but I do not see why it should go teets up just because the file is on drive 'D'. Another one of life's mysteries.
-
It depends how the
drive is connected to the system...
Delays in saving data down the wires can cause these saving data issues... -
Does not like importing skp from drive d even when the model I'm working on is saved on the 'C' drive. This is a problem with 2019, no idea why.
-
So if you copy the file-to-import from
to does it import OK into a based SKP ? -
Sorry mate, I just wonder what the point of duplicating all my files is all about. This has only happened in 2019 and only really since the .3 edition, nothing like this before and I do not appreciate the mucking about.
The idea of putting the files on drive 'D' is to save memory on drive 'C', it is an internal hdd direct to the mother board.
BTW, the answer is no. Having moved my files to the 'C' drive I still cannot import SKP. I think I must be getting two tuesday's this week. I hope only two anyway.
Advertisement