This forum is now closed.
Please join us at the new Lumion Community forum.
Lumion Community
Use your email address and password from the old forum to log in if your account was created before Feb 20 2020.
Otherwise, you will need to create a new Lumion Account at the new forum.
Pages: [1]   Go Down

Author Topic: Texture errors write themselves to older files.  (Read 2458 times)

Simoni

    Reputation: 24
Texture errors write themselves to older files.
« on: February 10, 2011, 12:07:26 pm »
February 10, 2011, 12:07:26 pm
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.
Logged

Ferry

    Reputation: 0
Texture errors write themselves to older files.
« Reply #1 on: February 10, 2011, 12:17:40 pm »
February 10, 2011, 12:17:40 pm
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!
Logged

Simoni

    Reputation: 24
Texture errors write themselves to older files.
« Reply #2 on: February 10, 2011, 12:31:51 pm »
February 10, 2011, 12:31:51 pm
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.
Logged

Simoni

    Reputation: 24
Texture errors write themselves to older files.
« Reply #3 on: February 10, 2011, 12:56:37 pm »
February 10, 2011, 12:56:37 pm
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.
Logged

Ferry

    Reputation: 0
Texture errors write themselves to older files.
« Reply #4 on: February 10, 2011, 01:15:19 pm »
February 10, 2011, 01:15:19 pm
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.
Logged

Simoni

    Reputation: 24
Texture errors write themselves to older files.
« Reply #5 on: February 10, 2011, 02:01:49 pm »
February 10, 2011, 02:01:49 pm
I do not save the files with texture errors, thats what makes it so illogical. This has happned twice now and is very worrying.
Logged

Ferry

    Reputation: 0
Texture errors write themselves to older files.
« Reply #6 on: February 10, 2011, 02:43:20 pm »
February 10, 2011, 02:43:20 pm
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.
Logged

Simoni

    Reputation: 24
Texture errors write themselves to older files.
« Reply #7 on: February 10, 2011, 03:05:46 pm »
February 10, 2011, 03:05:46 pm
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.
Logged

Morten

Texture errors write themselves to older files.
« Reply #8 on: February 16, 2011, 01:24:19 pm »
February 16, 2011, 01:24:19 pm
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

Logged
IMPORTANT: Please do not send private messages and emails to members of staff - unless we specifically ask you to send us sensitive information, for example License Keys.
Pages: [1]   Go Up