On Azure (winx64) deployed it generates gltf with missing geometry about xbimgeometry

[andyward]

Very strange. We've used Xbim.Geometry 5.1 & 6 extensively in azure app services (winx86 and winx64) and not seen this kind of 'partial' failure. Azure issues are usually all or nothing (environmental etc) rather than this kind of thing. However we're not using gltf which may add another layer of complexity.

Things to check:

• Is it 100% repeatable? Is it always the same elements missing?
• Does it occur with other models, or just this one?
• Have you tried setting the number of threads to 1? (i.e. Xbim3DModelContext.MaxThreads = 1)
• Have you managed to get any logs from the Geometry Engine (using an ILogger)
• Have you tried generating wexbim rather than glTF to establish if it's a core GE issue vs gltf export
• Have you tried stripping the model down to a the affected walls & openings?

It looks like it's failing to cut the openings (a boolean operation in OpenCascade). That might point at a few things including:

• Precision (as you mention) - try adjusting the precision on ModelFactors
• wrong / incompatible VC/Windows runtime (Kudu may be able to tell you what's installed)
• a threading issue
• potentially an endian edge case?