Blog

This blog covers how to use GetResultDeviation to calculate when to LOD transition. In normal case we strongly recommend to use screen size or max deviation as reduction target, but if you have a specific need which request reduction ratio or exact triangle count this blog will describe how to calculate when to switch to that LOD. We are going to use this to populate a Unity LODComponent. We are also going cover how to reuse materials from LOD0 automatically.

This post will showcase how we can use Simplygon to generate LOD levels to populate Unity's LODGroup component. We are going to use cascaded reduction pipelines with screen size as stop criteria. This means we can think of LOD transitions in terms of visual difference instead of polygon count and distance to camera.

Many scripted Simplygon workflows starts with a pipeline that is exported from one of our integrations. In this post will give you a very straight forward step by step on how to create a scripted optimization with cascaded pipelines.