The URL to previous versions of SketchUp is: www.sketchup.com/download/all
Just some Ideas:
This is the first time I’ve seen this issue reported on the forum. Which is odd because I’d expect to see others commenting if it was a unique problem associated with SketchUP 2016 and Windows 10. It’s been out long enough now, and I’m sure more than a few SU users are running under Win 10.
Running multiple applications simultaneously doesn’t create the textbook environment for isolating a problem. If you do have some days in which SketchUp doesn’t drop models, then I wonder how that might coincide with other application NOT being run at that same time.
For the sake of easing up on some of the variables involved, and isolating the problem—to say nothing of the unfortunate consequences of increasing your own aggravation and inconvenience while doing so—I really think you should try to run sketchUp solo for a while… see what happens, and then slowly introduce other programs back into the mix.
The lack of this problem being reported by others, makes it just as likely that you could be encountering incompatibility across applications. Unique to your own computer, and work habits.
AND, Maybe it is SketchUp 2016,… but then there are also all the Extensions which come with it. . . and I wouldn’t rule out the possibility of an outdated extension causing issues as well (if we’re going to entertain this idea of application incompatibility). . . So you might also turn off the plug-ins for a while, or see if you can verify that they have been updated to work with SU 2016.
Software issues aside, this could also have a hardware aspect to it… (albeit a little less likely by comparison, but still worth consideration as a possibility)
You have a lot of memory. Running applications, and the data they generate, get stored there until being written to a drive… I wonder how likely it is that once you load up the memory enough, data finally reaches a bad/weak sector and read/write errors start to occur.
Intermittent memory errors are hard to recognize. But they do happen—I ran across this myself when building a new desktop some time back… While trying to install the OS, and software, I had a random assortment of strange things happening, and not typically repeating themselves when retrying the same task a 2nd time around. There was also a good deal of misdirection, because very often it would seem as if the issue was with my DVD drive not reading the disc correctly. It took a number of days before I finally started to test the memory, and ultimately discovered that my brand new memory straight out of the box was the problem all along.
Checking the memory is relatively easy to do. There are probably a few programs to choose from—but the one that I know of, used, and have no problem recommending is called… MemTest86.
- [ The reputation of this program has been, and continues to be good, but I haven’t used it lately, so please make sure to check it’s compatible with your computer before jumping into it, if you even do. ]
Intermittent memory errors can be trigged by stress (only occurring after the memory has worked to a certain performance level), or even just encountered once a certain temperature is reached.
… and back into the software realm… you can’t go far wrong by checking over all of your device drivers, looking for update possibilities.