Optimization¶

Linking assets¶

We go through great lengths to allow linked assets. We heavily recommend you link by default and only convert to editable when you need to make changes. There are several advantages in favor of linking:

• your .blend scene file will be smaller
• RAM or VRAM usage might be lower during renders (if you use the same asset multiple times)
• get fixes and upgrades in your scene when you upgrade traffiq and reload

Smaller .blend files¶

Let's go through a small exercise to outline scene file size differences between editable and linked assets. For our testing purposes we will be using Blender 3.0.1 with factory settings.

1. (optional) Disable File compression in Blender (Preferences → Save & Load → File Compression). Everything here applies even with compression but results will be more pronounced and predictable without it.
2. Open Blender and save the default scene (with default cube) as testing_scene.blend. It should have roughly 100 kB.
3. Now spawn 3 different trees as linked. Save the blend. Observe that the file is around 108 kB. The additional trees take almost no extra space on hard-drive.
4. Now convert the 3 trees to editable using the Convert to Editable operator. Save the file. The file will now have roughly 14 MB. The specific size depends on which trees you chose to spawn. The point is it will grow noticeably.
5. Now click File -> External data -> Pack Resources. This will pack external files into the scene. In this instances it's mainly textures. The file will grow to roughly 18 MB.

As you can see, keeping the assets linked makes scene files much smaller. With a complex production scene the file sizes would be even larger. This greatly helps when collaborating with others, especially when using Google Drive, OneDrive or other file sharing solutions. You want to speed-up file transfers are much as possible.

Lower RAM / VRAM usage when rendering¶

Similarly to the previous example we will use a testing scene with several trees and compare RAM usage when rendering with cycles. In our example we will use CPU rendering with the Cycles renderer. Results are similar when rendering on the GPU with CUDA, Optix or HIP.

1. Open Blender, spawn several instances of the same tree to the scene.
2. Check that Render Engine is set to Cycles and hit Render -> Render Image. RAM usage will be around 200 MB in our example.
3. Select all trees and click on Convert to Editable. Hit Render -> Render Image. Notice that the resulting image is exactly the same but RAM usage more than tripled! Now it's over 600 MB.

You would expect Cycles to figure out that you are using exactly the same meshes and materials, etc... but it doesn't. You have to tell it that the trees are exactly the same to get the RAM savings. The most reliable way to do that is with linked assets. If the assets are linked and are linking the same source .blend file they have to be exactly the same.

File compression¶

Blender allows you to use file compression on .blend files it saves. At the cost of taking more CPU time to save the resulting files are smaller, sometimes a ton smaller. This is especially helpful when you have a lot of complex geometry in the scene.