Been working on an image in Vue Infinite 8.5, fairly complex, using Poser and DAZ objects, saving regularly, now after a crash Vue will not open any of the last 10 saves I've made. I get a message saying "Unable to read file/Volumes ..and name of the file. Initially it asked me to find various material files (which I tried to) now it goes straight to the "Unable to read..." file - bit depressing - have I lost a weeks work, or has anyone got any suggestions?

 The only thing I can think of in this case other than calling e-on would be to try and do a restore in windows to a previous working date, like a few days before your crash possibly.

it would help to also post what OS you using and if it's PLE or full Vue

OK to explain this more precisely - and I'd be grateful for any answers/ideas/feedback.

I am using a MAC 2 x 3.2 Ghz, Quad core, Intel Xeon - with NVidia GeForce 8800 GT graphics card and OS 10.5.4. And Vue Infinite 8.5

Vue Infinite states there are 1,192 objects, 1 light and 3,184,376 polygons in the file. In fact there are 'only' 41 objects (Poser and DAZ objects, and a few .objs).

The problem I am having is with materials. When I try to open files I get a pop-up saying "Unable to find fileApplicationObjectsJenny_Col_Body.jpg. Would you like to locate it?" I then get about another 40 more similar pop ups asking me to find other jpgs. Regardless what I do - whether I try to find the file or if I click "no", or "no to all", at some point the file crashes.

In fact I do not need the Poser materials because I am applying materials in Vue Infinite.

Is there any way I can reduce the number of materials in Poser objects - ideally to one?

Any ideas?

You can export from Daz or Poser as collada, that will work better, how ever you can not use repose inside Vue, if you do so. Problem that Daz, Poser and Vue was created as PC applications and ported to Mac platform. Looks like configuration does not set correct, when you install additional objects to your library. Verify in Poser/Daz that working directory set to your application folder. Also it's may releated to user right issue. Application may not have right to that folder, so it does nto see it.