Visual Fidelity


Category: Visual Fidelity

Here you will find an explanation and best practices for solving Visual Fidelity related synchronization errors.  

Visual fidelity errors refer to problems related to the accuracy, quality, or appearance of visual content, such as graphical elements.

 

Table of Contents

Materials

Warning: DgnV8_0057

   Warning message: "The texture 'File_Name.jpg' used in material 'Material_name' used in file '1-1111-S-001' either could not be located or could not be loaded."

Issue:

Cause:

Solution:

The textures can be solved by fixing the paths of textures (PNG\JPG) files used in materials using the Material Editor dialog in the Bentley design application. The dialog can be launched using search-> Material Editor.

Attachment

Info: DgnV8_0005

   Info message: "No model found for <x>. It will not be added to view < y>"

Issue: 

Model is not added to the view. 

Cause:

Model was not found and it was failed to convert one of the models used in view x. 

Solution:

When there is related issue to model (x), after resolving that issue model should be added to the view (y). - Please check the Synchronization Report for other errors that contain the same model (x) issue, this might be the root cause of why the model is not found. Refer to the root error on Communities, solve issue with the provided solution, re-run synchronization and model should be added to the view.

About BIS modeling: https://www.itwinjs.org/bis/guide/intro/modeling-with-bis/

 

Warning: DgnV8_0063,DgnV8_0064

 

Info Message DgnV8_0063: Texture 'C:\stagingDir\d0246137\TextureFile.jpg' for material 'Material' is of unsupported PBR material type. 

Info Message DgnV8_0064: The texture 'C:\stagingDir\d0246138\TextureFile.jpg' in material 'Material' uses 'Solid' mapping mode which is unsupported. The material will be dropped. Please change the mapping mode to a supported mode. 

 

Material types and texture mapping modes

There are numerous techniques for texture mapping, such as cubic, cylindrical, directional drape, elevation drape, front projection, parametric, planar, solid, spherical, and many other complex methods and variations. However, iTwin connection synchronizations are limited to supporting only three of these texture mapping modes. If materials with unsupported texture mapping methods are used in iModels, a Visual Fidelity warning will appear in the Synchronization Report, indicating that 'The material will be dropped. Please change the mapping mode to a supported mode.'

 

Supported texture mapping modes in iModels:

More information about each mapping mode:

Parametrichttps://docs.bentley.com/LiveContent/web/Bentley%20Raceway%20and%20Cable%20Management%20Help-v8.1.1/en/GUID-8CCCE1F0-2D81-4EE7-A943-23CE19EF86C9.html

Elevation drapehttps://docs.bentley.com/LiveContent/web/Bentley%20Raceway%20and%20Cable%20Management%20Help-v8.1.1/en/GUID-0A7C6CBE-D452-8E55-74F0-61073266EBC1.html

Planarhttps://docs.bentley.com/LiveContent/web/Bentley%20Raceway%20and%20Cable%20Management%20Help-v8.1.1/en/CreateSurfacesPlaneByPoints.html

 

Geometry

Error: Revit_0035

   Error message: Symbol <Symbol ID> of <entity class> '<Entity name>' (Revit <Id>) cannot be saved, most likely because the element is too large.

Issue:

Cause:

Solution: 

 

Error: Revit_0039

   Error message: The converted geometry for [Element] '[Name]' (Revit ID: [ID]) is [Size] MB, exceeding the limit of [Limit] MB. As a result, [N] of [Total] symbols were excluded. Please split up this element to ensure all symbols are converted.

Issue:

Cause:

Solution: 

 

Warning: Revit_0040

   Warning message: The geometry for [Element] '[Name]' (Revit ID: [ID]) is [Size] MB, which exceeds the recommended limit of 2 MB. This may reduce display performance. Please split up this element to improve performance.

Issue:

Cause:

Solution: 

 

Error: Revit_0041

   Error message: The converted geometry for Symbol [ID], containing [N] items from [Element] '[Name]' (Revit ID: [ID]), is [Size] MB and exceeds the limit of [Limit] MB. The symbol has been excluded. Please split the symbol to ensure the entire element is converted.

Issue:

Cause:

Solution: 

 

Level

Info:DgnV8_0044

   Info message: "Level [Level name] has a different definition in [path name] than in other files or attachments: weight/color/style (x vs. y).""

Issue:

Same name level carries distinct values across associated files.

Cause:

Level sharing the same name across related files which have different definitions for line color, weight or style.

Solution: 

Either modify the level names or ensure consistent definitions for levels with identical names.


Example:

 

Same name "Blue" sharing levels has different definitions for color and style.

 

MicroStation documentation related to levels: https://bentleysystems.service-now.com/community?id=kb_article&sysparm_article=KB0113400 

 

Warning:Dwg_0089

   Warning message: "Error: 1 out of X shared part geometry element(s) may have display discrepancy for entity [Entity Name]"

Issue: 

Coming soon. 

Cause:

Coming soon. 

Solution:

Coming soon. 

Raster

Info: DgnV8_0012

Info message: Failed to convert [Processing Visible Edges extraction in tiled mode due to memory constraints. - There is insufficient memory to perform Visible Edge extraction on model: <model> of file: <file>. The model will be automatically processed as a series of tiles.] 

Issue:

This message is emitted by the DgnV8 converter while generating Cached Visible Edges (CVE) for a drawing/section view. The reported message is passed through from the visibleedge extraction engine and, in this case, reads: 

Failed to convert [Processing Visible Edges extraction in tiled mode due to memory constraints. - There is insufficient memory to perform Visible Edge extraction on model: <model> of file: <file>. The model will be automatically processed as a series of tiles.] 

Note: DgnV8_0012 reflects the severity of the underlying engine message. When the priority is Info (as here) it is informational only; the same issue Id can also appear as Warning or Error if the engine reports a higher priority. The "Failed to convert […]" wrapper is the generic converter prefix — the bracketed text is the actual engine message. 

Cause:

Visible Edge extraction converts 3D reference geometry into visibleedge (hiddenline) drawing output. For large or complex models this can require more memory than is available in a single pass. When the connector detects that it cannot perform the extraction in one operation, it does not fail — it automatically falls back to tiled mode, splitting the model into a series of tiles and processing them individually. This is a normal, selfrecovering optimization, not a conversion failure. It is typically driven by model size/complexity and the memory available on the machine running the connector. 

Solution:

No action is required in most cases — the message is informational and the converter continues processing the model in tiles, producing correct output. 

If tiled processing is slow or you want to avoid the fallback: 

  • Provide more memory. It may be possible to increase the memory for the machine running the synchronization. 
  • Reduce model complexity in the source. Simplify or split very large/dense reference models, remove unnecessary detail, or turn off levels/references not needed in the drawing so less geometry is processed for visibleedge extraction. 
  • Review the drawing/section view scope. Ensure the view is not referencing far more geometry than intended (for example, an overly broad clip volume), which inflates memory usage. 
  • Confirm the output is correct. After the synchronization, verify the affected drawing (e.g., Default model of the listed file) displays the expected visible edges. If edges are missing or the same message appears as Warning/Error rather than Info, treat it as a genuine failure and contact Bentley Support with the file name, model name, and the connector log. 

View

Warning: Revit_0034

Warning message: <Count> Revit elements use per-view graphical overrides. The iModel will only show their default representation. Revit element(s): <Revit ID list>

Issue:

Cause:

Solution: