Lumion Pro 5.7 File Management (Part 1 of 5)

Share on email
Share on linkedin
Share on facebook
Share on whatsapp

Lumion Pro 5.7 is a real-time rendering package used by approximately 63 of the world’s top 100 Architects. It offers incredible real-time rendering capabilities and provides the best solution to familiarize Architectural clients and designers with model designs. It provides great quality in a fraction of the time of other packages with little or no rework should the model change. Micrographics is the exclusive reseller of Lumion in Africa.


  • Facilitates 7 day trials of the fully functioning package
  • Offer a dedicated high-end Lumion PC for evaluation and rental
  • Offer hardware solutions for running Lumion


In Lumion the following refers to:

Model                   A Model is a component that may be loaded into a scene. For instance, a Revit project may be converted to a .dae file using the Collada Revit to Lumion Bridge exporter, and this can be imported into a Lumion scene as a model. A model is defined by three separate files within “C:\Users\paul\Documents\Lumion 5\Library\”. Drawing (.dwg) and Sketchup (.skp) files are among others that may also be imported.

Scene                    A Scene is Lumion’s term for “File” or “Project” and is defined by two files of the same filename albeit with differing extensions (.spr and .sva). By default scenes are saved within “C:\Users\paul\Documents\Lumion 5\Scenes\”. In this document and in general they are referred to as LS# files, where “#” refers to the base edition of Lumion under discussion. For Lumion 5, Scene files are referred to as “LS5” files.

1 Introduction

A prospective Lumion Pro 5.7 client ran a 7 day full trial, compiling a project in evaluation anticipating that he would invest in the software, which indeed he did. As a new user, the LS5 save/open dialogue posed some challenges which this blog addresses.

  • Will a project set up with the 7 day trial version be opened by the full version?
  • Can their files be saved to a network location instead of their hard drive?
  • If they were to invest in multiple licenses, how would they manage their files so they could work on projects together (not concurrently)?