Topic: Texture errors write themselves to older files.

[Simoni]

Lumion is wonderful but...in RC4 and RC5 there has been a worrying glitch in that if a texture has been wrongly applied, and in both cases it has been water, then, without undo, I try and open a previous file version, say many hours old, the texture error also appears in these old files! This is mad and illogical, my hardrive is not haunted.

[Ferry]

Remember that all projects share your content library. So saving a scene which uses an imported model does not save a copy of that imported model with that scene. So changing the imported model later also changes it for your old scene!

[Simoni]

The point is I do not save the scene with the error, maybe the autosave facility does this , which to repeat my earlier rant, is giving me help that I could do without.

[Simoni]

Strangely the texture reverts back to its correct material, in older file version if I select it (it was glass, not water as I mistakenly said) in the horizontal tally of material assignments at the bottom of the interface, I just click on the assigned glass icon, then on custom icon (of the 8 choices  in the materials editor) then in magically reverts back to its correct texture ie. a slate texture.

[Ferry]

We don't overwrite any old file automatically with autosave to get back to your rant. I can't make anything out of what you are saying is happening with the materials. Also the original textures are never removed so using a standard material will always give you back your textures. Glas just hides them.

[Simoni]

I do not save the files with texture errors, thats what makes it so illogical. This has happned twice now and is very worrying.

[Ferry]

Remeber that if you in some project drag in a model from the library and you edit the material that it automatically SAVES that model! Models are not saved per project they are saved accros the whole use of Lumion.

[Simoni]

This is pretty worrying, without a proper undo, I can make mistakes which I discover a few minutes later, too late.. Lumion just writes it into the unsaved model?

Without a proper undo feature this is impractical, I would prefer the changes saved to the library only when I say so, ie when I save my changes.

Too much happens automatically, snapping, saving, I spend most of my time trying to undo these great labour saving features, literally days.

[Morten]

Hi Simon,

We've got a couple of entries on the Functionality wish list which deal with this issue, i.e. implementing a system which allows you to save materials as model-independent files so to speak, so that you can create your own material library:

• Save/Load user-created materials to avoid having to create them again in other scenes


• Save/Load user-modified Lumion materials to avoid having to create them again in other scenes