[CS] LiveSynced model always resets to original state in Revit

1. Problem:

1.1: A user wants to know why their LiveSync model always reverts to the original state (white, without materials), even after saving it.

1.2 User quote:

I am struggling with Revit and the lumion model staying linked. Is there a proper shutdown procedure? If I save the Lumion model after making changes in it like adding a tree, when I reopen it the changes are gone - no tree. Livelink works on the newly opening Lumion model but it is not the same model I saved from the prior session. In other words, once you make changes in Lumion and close the files, the changes are lost unless you open the old file from inside of Revit - but then there is no livelink.

[...]

Everything disappears, objects, material changes to model. It looks like a linked file that opens for the first time.

2. Reply (not standard):

2.1: Answer:

Thanks for getting in touch and sorry to hear about your issue.

That sounds a bit unusual since Lumion should not forget information unless the files are not saved properly. I presume you are saving the Lumion file before/after closing LiveSync and Revit.

Please answer some follow-up questions just to make sure we get everything right:

1. When you try to LiveSync after re-opening Lumion, does the .RVT file have the same name and location?

If you change the name or location of the Revit project, you need to use the 'Re-connect' button to relink the files and make Lumion compare the data:

2. What type of objects disappear after re-opening Lumion? Is it only Trees and assigned Materials? Can you confirm this happens with all included Lumion Library objects?

3. Can you confirm that your workflow is the following when LiveSync-ing?

You:

save the Project in Lumion and also save the .RVT file
you close the 2 apps
you reopen the .LS file that you had previously saved and the .RVT file
you start LiveSync again
(then all your previous progress is gone?)

4. For most users, the syncing procedure seems to not cause any issues. As you have mentioned for your case:

The relinking procedure is cumbersome and the reimported model in Limion is all white so that doesn't work. Clearly, I am missing something as the LiveLink process so far is largely useless unless you don't make any additions to the Lumion Model until you are 100% done in the Revit model. That makes no sense.

That is correct, it does not make any sense and LiveSync does not behave that way. Normally all the changes you do in Revit are visible live in Lumion.

Did you try following the instructions from the article provided in the article below? 99.9% of the times, that is the issue the users are dealing with and the article explains the LiveSync relink procedure:

Knowledge Base: How does LiveSync work with existing imported models in Lumion Projects?

If you can confirm it's the case from question 3 (the exact same steps and still experience data loss), the most common culprit for this sort of problem is generally cloud-based software that prevents Lumion from properly saving or storing information.

You need to make sure that software such as OneDrive, Gdrive, Dropbox, etc is not backing up the Documents\Lumion folder (or it's simply turned off while Lumion is open), otherwise, you risk data losses. What normally happens to create this issue is that the cloud software locks up the file before Lumion writing all the data. Then, more often than not, you are left with a corrupted file that you can't recover anything from. For good practice with Lumion, we would appreciate if you work locally and then, for backup purposes only, upload your files to the cloud.

3. Cause/Background information:

3.1: Reference:

Zendesk Support Request

https://lumion.zendesk.com/agent/tickets/12257

3.2: User Quote on the solution:

The problem seems to have gone away by moving my model and Lumion model to my local drives and by starting Lumion with the correct model before I start LiveLink in Revit.

3.3: Editor's notes:

There is no reason for which a model should revert to its original state (if using LiveSync or otherwise) unless the model has not been written to the hard drive in the first place. The suspicion, in this case, was that the user was working on their model in Memory (RAM) and then, once Lumion was closed, the model disappeared. Therefore, the course of action that was chosen was to investigate if anything is preventing the user from saving properly.

==========================================

ARTICLE SUPPORT (from transfer to HubSpot):

1. Tables:

Tables were not able to be imported via HubSpot Importer. Any Tables in this article are now based on a DIV Conversion. Same is also the case for the transfer of articles with tables in the EKB.

You can add new (basic) Tables in the HubSpot Editor directly.

If the layout does not work, then you can copy/paste or recreate the old Table from ZD. Where possible the Table has also been copy/pasted from the source page (see link below in 3.). Instructions, see this article: Copying an old Zendesk Table over to HubSpot

2. Finding the reference to the old Zendesk Ticket in HubSpot:

Use this Support article: Finding the reference to the old Zendesk Ticket in HubSpot

and for ZD ticket Search in HubSpot following step 1 in above article:

3. Source Zendesk article:

A source and backup copy was made of all articles 9 June 2025.

The saved HTML files and images are in subfolders of: HTML files and images subfolders.

4: Quick Link to Zendesk IKB article:

(not available when Zendesk closed)

[CS] LiveSynced model always resets to original state in Revit