closed scene, and mats gone?
Posted: Mon Aug 28, 2006 6:53 pm
Well, I'm really trying here. I like the output of maxwell, but i'm about at my wits end.
I have a scene with about 30 different mats. Yesterday, I closed the scene and max, and gave my machine a much needed break. When I loaded it back up, (had to open scanline first, then open mat editor, then switch to maxwell engine, which is a pain as it is!!!!), half of the mats are gone. It wasn't just new mats I made, but it was 2 of the arroway mats, about 3 from the mxm download site, and 3 or 4 of my own mats.
I went in and had to re-choose mxm on all the missing mats. Then, I started getting bitmap not found errors. I then had to re-path a lot of the textures, including some that I had done before, and some that performed the dissapearing act, and some that didn't.
One of the mats that had worked fine before the "restart", just wouldn't keep the bitmap path, so I had to delete it and re-create the material, then save it. That worked.
Is there some reason that these things happend, or is it just ghosts in the machine? Now I'm afraid if I close max again that this will happen again. If I have to do this everytime I close max, I'm going to just give up.
I have a scene with about 30 different mats. Yesterday, I closed the scene and max, and gave my machine a much needed break. When I loaded it back up, (had to open scanline first, then open mat editor, then switch to maxwell engine, which is a pain as it is!!!!), half of the mats are gone. It wasn't just new mats I made, but it was 2 of the arroway mats, about 3 from the mxm download site, and 3 or 4 of my own mats.
I went in and had to re-choose mxm on all the missing mats. Then, I started getting bitmap not found errors. I then had to re-path a lot of the textures, including some that I had done before, and some that performed the dissapearing act, and some that didn't.
One of the mats that had worked fine before the "restart", just wouldn't keep the bitmap path, so I had to delete it and re-create the material, then save it. That worked.
Is there some reason that these things happend, or is it just ghosts in the machine? Now I'm afraid if I close max again that this will happen again. If I have to do this everytime I close max, I'm going to just give up.
