Bookmarks can be created in different ways depending on how you want the saved view to behave when the project changes.
Two bookmarks can show exactly the same content when they are created, but behave differently when new files are later added to the project.
This article explains two ways of creating bookmarks with the Model Tree and some best practices for keeping bookmarks stable over time.
1. Two ways to create a bookmark
The same visible result can be created in two different ways.
The difference is how the bookmark handles content that is added later.
Method 1 – Start Hidden
Activate View Only Selected.
Content is hidden by default.
Show the folders or files you want.
Save the bookmark.
Use this method when new, unrelated content should stay hidden.
Rule: Start hidden → show what you need.
Method 2 – Start Visible
Keep View Only Selected in its default state.
Content is visible by default.
Hide the folders or files you do not want.
Save the bookmark.
Use this method when new content should be allowed to appear automatically.
Rule: Start visible → hide what you do not need.
2. What happens when new files are added?
Assume both bookmarks currently show the complete Roads folder.
A new file is then added inside Roads.
Method 1: Visible
Method 2: Visible
The complete Roads folder is part of the bookmark, so the bookmark follows that folder and can include new files added inside it.
Now assume a completely new file is added to the project root.
Method 1: Hidden
Method 2: Visible
The root file does not belong to anything the bookmark already follows.
It therefore uses the bookmark's default visibility:
Method 1 → hidden
Method 2 → visible
3. Complete folders vs. specific files
How much of the Model Tree you include also matters.
If the complete Roads folder is included:
Roads
Road 01
Road 02
Road 03
The bookmark follows the Roads folder.
A new Road 04 file added inside Roads can therefore be included automatically.
If only Road 01 and Road 02 are included, the bookmark follows those specific files instead.
A new Road 04 file is not automatically included with Method 1.
In short:
Complete folder → follows the folder
Specific files → follows those files
4. New revisions vs. new files
A new revision of an existing file is different from adding a completely new file.
If a complete model file is part of a bookmark, Novorender can continue to follow that file when a new revision is uploaded.
This makes folder- and file-based bookmarks more stable over time.
5. Individual objects and GUIDs
Bookmarks can also contain individual objects inside a model.
At object level, Novorender must identify the same object again when a new model revision is uploaded.
Objects can be identified using IDs such as GUIDs.
A GUID can be thought of as an ID tag for an object.
If the identifier remains stable between revisions, Novorender can normally find the object again.
If the identifier changes, the object may no longer be resolved as expected in the bookmark.
Object-level bookmarks therefore depend more on consistent model data between revisions.
6. Selection Basket
Selection Basket works together with Model Tree visibility.
Objects in the Selection Basket are reflected as visible in the Model Tree.
If content is hidden from the Model Tree, corresponding objects are also removed from the Selection Basket.
This keeps selection and visibility consistent.
7. Best practice
Create bookmarks at the highest meaningful level.
Use complete folders when the bookmark should follow a discipline or project structure.
Use complete model files when the bookmark should follow specific models.
Use individual objects when needed, but be aware that they depend more on stable object identifiers between revisions.
Choose the bookmark method based on how new content should behave:
Method 1 – Start Hidden
New unrelated content stays hidden.
Method 2 – Start Visible
New unrelated content can appear automatically.