Troubleshooting Large Assembly Detailing (+100k components): View Generation Freezing at Step 3/5

Hello everyone,

I'm currently facing a significant challenge while trying to create technical drawings for a massive assembly (+100,000 components).

While I’ve managed to optimize the 3D performance within the Assembly Design workbench, I hit a wall when moving to Drafting. Generating the initial or isometric views takes several hours or simply freezes CATIA entirely, typically getting stuck at step 3/5 of the view generation process. During a tested, I maintain the execution by 03:00:00, then I close the CATIA application.

I’ve structured my troubleshooting into two main hypotheses, but I could really use the community's expertise to move forward:

Hypothesis A: File inconsistencies or corrupted geometries within the project. Hypothesis B: Inadequate drafting settings for handling an assembly of this scale.

Here is what I have tested so far:

Testing Hypothesis A (File Integrity): I generated drawings for each top-level subassembly using both Approximate and CGR modes. For the subassemblies that exhibited abnormally long generation times, I manually curated the models, looking for visual glitches and "broken" surface bodies. I applied the "Unload" command to these specific components and generated the subassembly drawing again, which successfully yielded normal processing times.
 


During the creating a view in the sub-assembly 41 appear these error messages:
 

 

Translate this image:

3DEXPERIENCE - Incident Report Manager Message...

Generating minidump...

The Incident Report Manager is trying to get a context of unexpected behavior of the protected application. Please wait, this operation may take a while.

 


However, after performing this cleanup, I attempted to detail the main assembly once again, but the process failed/froze just as before.

Testing Hypothesis B (Performance Settings): I closely followed the recommendations from both older and recent 3DS White Papers regarding large assemblies. I tested:

  • Generating views in Approximate and CGR modes.
  • Using "Disable Update" during view creation/modification and manually updating afterward.
  • Enabling Occlusion Culling and working with Cache enabled and Exact View mode.

Unfortunately, in all scenarios, the result remained the same: CATIA freezes at step 3/5.

My questions for the experts here:

Regarding A (Files):

  1. Are there specific CATIA utilities/tools designed to batch-investigate and heal file inconsistencies in large projects?
  2. How can I effectively use CATIA diagnostic logs to pinpoint the exact component or mathematical operation causing the freeze?
  3. Is there a way to determine the triangle count (tessellation) for each component in the assembly? Or at least identify which components have the highest number of triangles, whether due to multiple instances or high geometric complexity?
  4. What other isolation tests would you recommend?

Regarding B (Settings & Process):

  1. Could anyone clarify exactly what CATIA is calculating under the hood during steps 1 through 5 of the view creation process? (Understanding what occurs in step 3 would be a huge help).
  2. Is there a way to disable the model preview while the view is being generated? I've noticed that the preview always appears with all planes, axes, and points visible, which might be adding unnecessary graphical overhead.
  3. For those who routinely detail projects of this magnitude, what are your proven best practices and advanced settings to save the day?

Additional Considerations:

  • I am currently using CATIA 3DEXPERIENCE R26x FD04 On Cloud (Role MDG).
  • The project was originally created in SOLIDWORKS, saved to the 3DEXPERIENCE platform, and subsequently finalized in CATIA 3DEXPERIENCE.
  • The main purpose of this 2D detailing is to generate a field installation layout for the equipment.
  • I believe CATIA should be fully capable of handling the detailing of assemblies of this scale (or even larger) with acceptable creation and editing times—acknowledging, of course, the natural processing delays expected due to the massive volume of data, but without freezing or crashing entirely.

Thank you in advance for your time and insights!