Im working on a model at the moment that has been fine over the last week or so but today I have added a few new materials and modified one existing material. I rendered out a couple of views fine, saved the model but I needed to render another output and when i loaded up the model again this mornings changes haven;t been remembered, i.e. the model rendered out with blank materials where the new ones should have been and the existing that I modified had reverted back to the earlier maerial.
Thought I must have quite out without saving so re-did all the new materials and modified the existing material again and saved, quit out loaded it up again and its forgotten everything again. Its like it doesnt want to know about any new modifications to the model.
Any ideas guys? I’m no where near finished on this and I cant spend anymore time on it without knowing what the problem is.
This is the first time I’ve heard of that workaround not working. Try making the material changes, open and close the Option Editor, the save as another file name and open that in a new SU window. Still lost your VRay materials?
Still didnt work, but I have found a solution anyway. I loaded a new visopt file first then closed the options screen then saved. Open the saved sketchup file and the materials were retained.
Weird, that this is the first time I have had the problem bearing in mind Ive had the program a month now. I’ve either been loading visopt files at the end of a session before rendering out or just had the options screen open all the time and been lucky!
thinking about it the 2 test renders I did this morning were just using the default visopt profiles so this is probably why.
At least I can crack on now, lost about 3 hrs of work this morning cos of that!
Not sure if it helps, but I unroll - roll up one of the sections - just so that I’m doing something in the Option Window. really not sure if that matters.
I’ll just have to remember to load a profile in before I finish a session. Im just surprised that todays the first day I encountered the problem. Should really be a fixed bug if you ask me, but ho-hum
Just opening and closing the Options Editor has always worked for me. It’s funny, when I think about it I do it completely automatically now when I save, I haven’t even though about this bug in months. I imagine it’s pretty high on the fix list.
Come to think of it, could this not be a job for another little ruby? A script that when you hit the hotkey/icon it instantaneously opens and closes the Options Editor, then saves the skp file thereby “patching” this bug? VfSU users would effectively use it instead of the SU save icon/hotkey. Just an idea.
