For those who don’t know the tool: InstaLOD from Abstract is a geometry optimisation layer sitting between DCC tools such as Blender and engines like Unreal Engine. It turns CAD, scans and DCC exports into predictable, well-behaving real-time assets without asking you to babysit every mesh.

VR as a first class citizen

With InstaLOD 2026, Abstract adds a dedicated VR target inside Delivery Optimization. Instead of nudging triangle counts and texture sizes mesh by mesh, users can now choose VR as the destination and let the system evaluate scene-wide constraints. InstaLOD accounts for triangle density, material complexity, texture resolution and runtime constraints when preparing assets for immersive devices or web deployment. Delivery Optimization can still run interactively, as reusable profiles or as rule based batch operations.

The difference is philosophical as much as technical. Rather than tweaking assets one at a time, teams define a policy and apply it everywhere. For large libraries sourced from CAD, scans and assorted DCC exports, that shift is more than cosmetic. It is also a reminder that XR performance budgets do not care how lovingly a mesh was modelled.

Raytraced shadows, fewer surprises

InstaLOD Studio’s physically accurate viewport now renders raytraced shadows using its deferred renderer, enabled by default. Raytracing can be toggled in Viewport Settings under Raytraced Effects. This is not pitched as a final render solution, but a sanity check. Evaluating silhouettes, normal fidelity and shading response under raytraced lighting during optimisation reduces the need to bounce assets back and forth to an external renderer. Translucency, bloom and transparency handling have also been improved.

Full scene wireframe rendering, adjustable opacity for filtered selections, corrected bloom and depth behaviour, and updated gizmo controls push the viewport closer to a diagnostic tool than a passive preview. The deferred renderer stays on by default, raytrcaing is optional. Less guesswork, fewer late night re-exports.

UVs without the ritual

UV Unwrap gains primitive based projection. Users can project from planes, cylinders, spheres in several variants, or boxes. Projection can be fitted to selected geometry via Adjust To Selection or aligned to bounding volumes using Fit To Bounding Box.

The feature is available from the Mesh menu, as a dedicated window or embedded in scene rules. When executed as a mesh operation, the projection adapts per mesh without manual parameter tweaks.

For large CAD imports or scan datasets, this means repeatable UV layouts without a custom setup per object. It will not replace hero asset unwrapping but works greatly for primitive geometry so you don’t have to unwrap the same bolt for the fiftieth time. For more complex geometries, InstaLOD’s already-existing UV algorithms can be applied.

Fixing geometry before it bites

Abstract states that the tool can fully reconstruct face orientation rather than simply flipping detected backfaces. For anyone who has chased blank faces through a pipeline at 2am, that promise alone will be appealing. Whether it resolves every pathological import case still depends on asset testing. So, now the Mesh Toolkit expands with Mesh Smoothing and a reworked Fix Winding Order. MMesh Smoothing is most useful for fixing messy scan data, not so much for CAD.

Fix Winding Order is the most helpful one for fixing broken CAD data. Fix Winding Order introduces a new algorithm that recomputes polygon orientation when normals are inconsistent or flipped. It is accessible in the Mesh Toolkit, Mesh menu, CAD import dialogue and CAD Live Link panel.

Bakers that trade triangles for pixels

Two new texture bakers extend surface detail workflows. Disk Sampling Curvature replaces previous curvature sampling approaches. The vendor states that it provides more stable and accurate curvature maps across varying art styles and geometric densities. It is enabled by selecting the Curvature baker and choosing Disk Sampling in the Texture Output panel.

The Bevel Normals baker generates rounded edge information directly into a normal map. Instead of adding subdivisions, it simulates bevelled edges in shading space. For low poly assets heading into real-time engines, this allows visually softer edges without increasing triangle counts.

The principle is familiar. If detail can live in a map instead of the mesh, the GPU will usually thank you. The art director may also stop asking why everything looks razor sharp.

Animation stays intact

InstaLOD 2026 extends animation support across GLTF, USD and FBX. GLTF and USD now support skeletal meshes, blend shapes and both skeletal and object based animations. FBX export introduces more granular control over skeletons, animations and blend shapes, with improved compatibility across DCC tools. The headline here is preservation. Optimisation does not automatically mean animation loss. InstaLOD positions itself as a geometry processing layer that respects rigs and deformation data rather than flattening them into static meshes. That is a meaningful distinction in pipelines where animation is not optional.

USD

USD workflows support polygonal meshes without forced triangulation, improved handling of stage metadata such as metersPerUnit, and removal of the default USDRoot node in exports. Material handling has been corrected for cases involving emissive colours or naming conflicts.

Polyverse inside the tool

Deeper Polyverse integration brings a built in asset browser into InstaLOD Studio. Users can download and import original meshes and automatically generated LODs directly inside the application. Authentication tokens are stored to reduce repeated logins. Assets can be previewed or opened in a web browser from within the interface.

The practical effect is fewer open tabs and less manual file shuffling. Asset discovery, LOD retrieval and optimisation now sit in a contiguous workflow. It is not glamorous, but it is the kind of friction reduction that accumulates over long productions.

Formats and host apps covered

CAD support now includes DWG and DGN. SolidWorks configurations are supported with optimised retessellation. Winding order correction is available during import. OBJ import and export have been reworked. GLTF vertex colour support has been extended. USDZ embedded texture path sanitisation is included.

Plugin compatibility extends to Blender up to 5.0, Unreal Engine up to 5.7 with improved Nanite fallback LOD quality, Autodesk Maya 2026, Autodesk 3ds Max 2026 and Autodesk VRED 2026.1.

In 3ds Max, Abstract reports execution time reductions by several orders of magnitude, bringing performance closer to InstaLOD Pipeline. This claim is vendor stated and not independently verified at press time. Unreal integration removes deprecated API calls and addresses previous instability around Skeletal Mesh editors and hardware ray tracing. On macOS, the Pipeline build ships as a notarised DMG. The compatibility list reads like a checklist of common production pain points. If your DCC of choice is on it, that is one fewer integration hurdle to clear.

Small updates, fewer surprises

The release also adds machine translated UI localisation, an automatic update system, improved selection performance on high poly meshes, new export settings for animation data, improved material name preservation in Delivery Optimization and warning systems for unsupported DCC versions. Individually, these are incremental. Collectively, they aim to make the tool less likely to annoy you at inconvenient moments. In production, predictability often beats novelty.

For teams working across games, XR, enterprise visualisation and virtual production, that middle layer is frequently a patchwork of scripts and manual cleanup. Abstract is consolidating it into a unified environment.

InstaLOD 2026 is available now from Abstract. As always, new pipeline components should be tested on real production assets before being rolled into active shows. Even the tidiest mesh can hide a suprise if you do not look closely.

https://www.abstract3d.com

The post InstaLOD 2026 Targets VR and Animation Pipelines first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

You can see an overview of InstaLOD’s complete feature set in DP 03:19. In this issue, we look in particular at how InstaLOD can automate the workflow from CAD data from a PLM system to a real-time-ready VR model.

by Calvin Bacon

Computer Aided Design (CAD) data from engineering consists of nurbs curves and surfaces and cannot be rendered by most renderers. Until now, there were two options for preparing them for real-time rendering. Either a manual retopo, i.e. building the asset from scratch as a 3D mesh, or tessellation.

Manual retopo is a process that can take days or weeks per scene – depending on the complexity of the models. The other option is automatic tessellation. However, since CAD data is parametric (has infinite accuracy), automatic tessellation achieves an extremely high polycount, which is practically useless for real-time rendering, and if a low tessellation is aimed for, details are often missing, curvatures are poorly modelled or get broken normals.

If the CAD object is then tessellated with sufficient accuracy, the polycount must be reduced, again by automatic optimisation or manual retopo. Finally, UVs have to be designed and textures baked so that the model can be viewed in the VR scene with sufficient fps. And even then, there are long-term problems with both manual preparation methods if a different renderer is to be used or if the initial CAD data changes.

Huge material libraries are currently being created, but these are only customised for a single renderer. Whether VRED, Arnold, V-Ray etc., the problem is the same. If you want to switch to a different engine in the future, every material from the library has to be completely rebuilt as a shader.

Another major problem with a product lifecycle management (PLM) system is that CAD data in it is constantly being modified by engineers, which means that all of the above steps often have to be carried out from scratch on a weekly basis. This workflow can be completely automated with InstaLOD’s CAD Live Link and Scene Import Rules.

By the way: Each feature can be executed as a batch process operator. All settings that are set up in a profile, including Scene Import Rules, can be saved externally as a JSON file. These can be used as presets or, if the CAD object changes again next week, the user loads the profile that has already been set up, applies it and achieves the same result again: an object that works for VR without manual intervention.

Loading CAD data with CAD Live Link

But what is the CAD Live Link and how do you use it? When loading a CAD file, you are first greeted with an import window in which you can select which parts or sub-assemblies are to be imported. InstaLOD supports a variety of CAD formats including Catia, Solidworks, Rhino, JT, NX, STEP and many more. Since the CAD Live Link still maintains the connection to the original CAD parts, we can still selectively retessell the parts.

Tessellation is influenced by three settings:

Maximum Deviation – uses a tolerance specified by the user to determine how much InstaLOD may deviate from the original CAD surface. This feature originally comes from InstaLOD’s optimiser, but was so popular that it was also integrated into CAD Live Link.

Maximum Edge Length – Specifies the maximum length of the edges.

Maximum Angle – Specifies the maximum angle between two polygons. If the angle is exceeded, the area is subdivided again until the specified angle is achieved.

The maximum angle is mainly used in other tessellation programmes, but is often not the ideal solution. The reason for this is that small parts – such as screws – can very quickly become very strongly tessellated within large assemblies. Normally, you don’t want to have a single screw with 50,000 polygons. Maximum deviation is therefore the ideal solution. This tessellates the objects to the quality tolerance that is specified, but does not subdivide the object unnecessarily.

Getting the splits ..

Another problem that often occurs with CAD data is surface inaccuracies, which can lead to shading problems. One such problem is shading splits – as shown in the images on the right. By default, a 3D operator has to manually repair these splits piece by piece, which is a lengthy process. With InstaLOD’s CAD Live Link, these can be repaired quickly and easily using the shading settings. In many cases, recalculating the normals is sufficient. In our case, however, a lot of shading information is stored within the CAD metadata, which would be lost by recalculation.

We therefore use InstaLOD’s Shading Magic, which automatically localises and repairs the problematic areas. After the tessellation has been performed and any shading problems have been repaired, the rim is not really usable yet, as all materials would have to be set up again for a render. There are also no UVs yet, so textures could not be added, and finally we have 80,000 polygons in the current state. If you were to scale these to a complete car, you would quickly have several million polygons, which is not compatible with a VR application.

So the next step is to make the rim VR-ready in a few steps. Firstly, we go to the mesh operation settings and start with a UV unwrap. Here we use the Hard Surface Axial algorithm, which creates a clean unwrap for the surfaces facing the axles.

Material Merge

After the UV unwrap, we perform a material merge operation. The reason for this is that we have three objects with three materials in this scene. If we scale this scene to a complete car, we quickly have thousands of objects with thousands of materials. Firstly, this is a lot of work for manually setting up the materials for a render, and secondly, this is also a huge amount of draw calls for a real-time application. We therefore use the material merge, which combines all materials and textures into a single material with a texture atlas.

Here we also merge the material parameters of metalness and roughness into a texture. This saves time later on when setting up the individual materials, but also saves a lot of draw calls and texture memory. To make it even easier to set up the materials, we combine the objects by using “Combine Meshes” in the Mesh Tool Kit (MTK). We now have an object with a material and a draw call. This object can now be exported and imported into any renderer, as we have the UVs and textures to render the materials exactly as initially set up – completely independent of the renderer.

Away with the polygons

Now the number of polygons must be reduced. To do this, we use InstaLOD’s Remesher, which performs a complete reconstruction of the rim within a very short time, simultaneously building UVs and baking textures. The result is an incredible reduction of over 90 %. We had already done all these steps manually, which begs the question: Why didn’t we use Remeshing directly on the original object? The reason for this is the workflow that we want to set up. What we can do now is to take our timeline with all the entries of UVs, Material Merge, Combine Meshes and Remesh – and convert all that into a new profile.

Outlook and application

Now you really realise how powerful InstaLOD’s workflows are – we can test multiple mesh operations, and if we’d rather try something else, we can just jump back in the timeline and test other operations until we’re happy. Then we can turn the workflow into a profile and scale it to hundreds or thousands of objects by exporting the profile as a JSON file and running it through the command line as a batch process. Or we can run the profile directly within InstaLOD Studio XL with InstaLOD Pipeline.

Profiles (which contain all settings) can be saved and used again at a later time. This is how presets etc. are set up if this ensures a better workflow. Experience has shown that you should first test the profile on one or two objects to see whether the profile has been set up correctly. Then nothing stands in the way of making your work easier – or of complete automation.

Scene import rules

When batch processing the CAD file, you logically have no manual control over the first steps that we have applied to the rim. This includes changing the tessellation and materials and often also changing the object hierarchies that you want to change or delete, as you don’t need them for the visualisation (see image above left “Organise outside” and “Organise inside”). With the Scene Import Rules, all this is possible with little effort. Simply specify which objects are affected and what should happen to them.

To set up a rule, you need to add a new entry in the “Scene Import Rules” window and give it a name. You then need to specify an attribute. Everything from the object name to the path can be specified here. The nice thing here is that basically any available attribute can be used within the metadata. You can see exactly which ones are available in the “Selected Object Information” window.

If you use “Name” as an attribute, for example, you must enter the name of the object in the “Match RegEx” field below so that it is processed by the rule. In the Predicate, you can specify how important this rule is, which is helpful if there are many rules, so that you can specify which rule is processed earlier or later in the list.

The predicate determines what the rules should perform on the objects. Available options are operations such as “Material Assignment”, “Tessellate”, “Delete” and many more. (top left image “Scene Import Rules”). Customised predicates can also be added using a C plug-in. These plug-ins are automatically compatible with the complete InstaLOD system. With these plug-ins you can customise InstaLOD to what you need for your own pipeline.

Conclusion: Automation rocks!

Now we come back to the PLM system that was briefly mentioned earlier. Once you have set up a set of rules, including the subsequent mesh operations, it is no longer a problem to update the CAD objects on a weekly basis. Simply load the finished profile and run a batch process in which the objects are automatically prepared using the rules (including materials, tessellation, organisation, etc.) and finally reduced by the mesh operations.

At the end, you get the finished, updated scene at the touch of a button, without having to manually intervene in the process. This means that large assemblies can be continuously extracted from a PLM system and made VR-ready within a very short time. By the way: If you want to try this out for yourself, you can get a trial version by filling in the form on our website InstaLOD.com and try out the described workflow and all the other features and processes that InstaLOD makes possible on your own assets.

The post InstaLOD: From CAD to VR? first appeared on DIGITAL PRODUCTION and was written by Alexandra Kaschny.