Re: Sketchup Crashes “Not enough space in TEMP folder” error msg
By coincidence I just ran into this bug today for the first time in 3 years of using VfSU. A skp file which previously rendered dozens of times without problem suddenly came up with the error message “Unable to create the error report. Please verify there is enough space in your TEMP folder.”.
Fortunately it was obvious in my case where the problem lay- I had just copied a straight-out-of-3D-Warehouse component into the file and on closer inspection it turned out that some of the texture diffuse maps were gifs… but when I tried to export out the textures out via SU’s Material Editor (so I can make sure they were on my HDD so V-Ray could find them) they exported out as jpgs.
This is probably due to a quirk of SU: that it is actually possible use gifs as diffuse maps even though they’re listed as unsupported. I’m not going to explain here to how to force SU to import gifs as it’s a bad idea for VfSU users. Just stick to jpgs, pngs and tiffs for diffuse maps and you shouldn’t have any problems.
So the solution in this case was:
1 ) Ignore your TEMP Folder or how much space is on your hard drive; they’ve got nothing to do with the problem, despite what VfSU tells you. 
2 ) Open the “In Model” folder in SU’s Material Editor.
3 ) Right-click the materials that are probably causing the problem (most likely from a recently inserted component), choose “Export Texture Image” from the context menu and save them somewhere.
4 ) Then go through the same materials and reassign the newly exported images.
5 ) Save the file and render.
EDIT: I’ve just run into this bug again in a different file. I’m working on diagnosing it, but it’s taking a long time as it requires so many separate tests to narrow down the source. At first I thought it was just the saved visopt I was using, but I tested that in another skp file it worked fine. Then I started deleting geometry and materials (and purging) and sometimes it parses ok, sometimes it doesn’t. Even weirder is that when I removed the bitmaps from background and reflection slots it rendered ok, but if I leave them in and remove some geometry and materials instead it also renders ok. It’s a bit like a game of Jenga in reverse- one in which the goal is to make it fall down. At the moment it seems there are several materials or visopt settings any one of which will cause VfSU to render ok after removal, but I can’t narrow it down enough to be useful. I even started seeing SU error messages which I’ve never seen before in 7 years of using SU (I’ve never seen 3 simultaneously either). This is an actual screenshot with the LC pass VFB in the background:
This is going to take a while to pin down. THE QUICKEST FIX IS TO LOAD ANOTHER “HEALTHY” VISOPT AND EDIT IT TO MATCH THE ONE THAT’S CAUSING THE CRASH. If it works, just save it over the buggy one. I suspect that the problem doesn’t lie in the visopt settings per se, but in how SU and VfSU are communicating during the parse process, in which many factors (materials, visopts, paths, etc) play a role.
I can say though that I’ve never seen this before installing SU7.1, so if you’re really struggling with this, reinstall SU7.0- it seems to be much more stable with VfSU.