A few other notes from my own experience. I have this exact issue, I find it really is texture indigestion. Vue has a memory leak/issue somewhere that's causing this. I've found that if I get the image imported, save the file immediately (if you can) before manipulating the image. Then close Vue and restart and reload and you can go on. Of course sometimes texture indigestion is so great that it can't go on. I've found then that scaling back on the texture size/type etc can help, as mentioned, but then once you get it loaded and saved. Restart. You are then set. It seems that if Vue loads the object natively from it's own format it has no problems, with whatever texture. I've been able to cram lots of extra poser objects in this way. Actually saying this, I might want to import objects independently and save them, and then load them natively. That should work, have to try. Anyway, the only other thing I didn't see mentioned and that you may not have been aware of. If your file is corrupted 17kb'd as I say. All is not lost. By default Vue makes a copy of the file every time you save. So you should always have a copy of like right before the last save. This file has the same name and a .bak extension. You can open like a normal vue file (you just have to use . in the Open File dialog filter. When things crunch, I make a copy of my bak file, the open the bak file and save as a .vue file.