Civil 3D 2020 - Crash when importing subassemblies

[cyberflow]

Hi there,

I've experienced crashing while importing C3D subassemblies from SAC onto my Civil 3D 2020 version.

Anyone else has experience the same ?

[copper.chadwick]

@cyberflow ,

I see you are posting about your Civil 3D 2020 software crashing when importing a subassembly? Would you mind posting the subassembly either publicly or private message so that I can test it? I have a few questions for you regarding this.

• Is this a custom subassembly or a stock one?
• What version was the subassembly created in?
• Did/ Does the subassembly work in an older version?
• Is there a CER created at the time of crash?
• Can you post the CER number here? Or private message me the email or CER number so that I can look it up?

Thanks in advance, I look forward to helping you isolate the causality.

[cyberflow]

Hi @copper.chadwick 

Thank you for helping.

Here are my replies : 

• Is this a custom subassembly or a stock one?
  • It is a custom subassembly.
• What version was the subassembly created in?
  • I created first in SAC 2016 but opened and resaved it in SAC 2020.
• Did/ Does the subassembly work in an older version?
  • It works until C3D 2018 (Never tested it on 2019)
• Is there a CER created at the time of crash?
  • What is a CER ?
• Can you post the CER number here? Or private message me the email or CER number so that I can look it up?
  • Where is the CER number on my workstation ?

For the subassembly il'l check with my boss since it's work from the office.

[copper.chadwick]

@cyberflow ,

Being it is a custom subassembly I wonder a couple of things:

• Does Civil 3D 2020 crash when importing all subassemblies?
• Were you able to procure that PKT file, feel free to PM it to me or PM me a private download link location so that I can test it. 
  
  

This really resolves to two things; either 2020 has an import issue in general, or the pkt has something in it that is no longer part of the legacy tree supported in the Subassembly Composer in 2020. Thanks in advance, and always, please hit the Accept as Solution button if a post fully solves the issue or answers the question.​ Thank you for your participation, your accepting a solution adds value to the post for the community as a whole, and helps other members find answers to their issues.

[cyberflow]

Hi @copper.chadwick 

Here's the pkt file

It crashes only when i import one subassembly

It just crashed my C3D 2020 right now :

[copper.chadwick]

@cyberflow ,

Thanks for that file, I tried it and it succeeded in import as well as attaching it to a Assembly.

Here's the steps I used:

1. I opened the PKT in Subassembly Composer 2020 and Save-As to overwrite the original file.
2. Closed SAC
3. Opened Civil 3D 2020
4. Added a New Pallet in Tool Pallets (named it TEST)
5. In the [Insert] > [Import] Tab > [Import Subassemblies]
6. Which opens the Import Subassemblies dialog > Chose the source file in Step 1 to Import To: [Tool Palette] > Test
7. Click [OK]

This workflow worked without crash.

If you try a saveas does that make any difference with the success? I did try and add it to the Curbs tool palette once and it failed but without an error, so I also wonder if it is looking for you to add it to a new palette?

[cyberflow]

Hi @copper.chadwick,

In the other thread that i've reported certain anomalies with the AOR in the SA.

I've recreated a new file manually, created manually all the input/output/targets, copy pasted my workflow.
Did a save as, then retryed in C3D 2018 my SA to see if my superelevations worked properly, and it did.

All i'm trying to say here, is maybe that there's maybe a bug with the original file (Old file) that corrupted it and made the SA react strangly (Only right side generated a delta applied with an input top grade and subgrade on the superelevation, pretty strange huh ?)

Maybe that caused C3D 2020 to crash.
Have you ever tryed recreating the crash and loading the PKT directly without doing a Save As on SAC 2020 ?

I'd like to see if i'm the only one who it has arrived.

[copper.chadwick]

@cyberflow ,

There is a known issue with SuperElevation with AOR in C3D 2019 and 2020, when using custom PKT files. But the results of that issue is not a fatal error, the Super Elevation, simply won't work.

In regards to trying to recreate the crash, I did try to make it crash, the intended workflow is exactly as I described, being that the Subassembly needs to be opened, updated, and saved, in the newer version of Subassembly Composer in order to be used in the newer version of Civil 3D. This process is to allow the program dependencies to upgrade the subassemblies with the their specific frameworks like dot NET.

But if, in a separate issue, after getting the subassembly to load without a crash, there is an Super Elevation with an AOR that is not rotating correctly? Is that another issue you might be experiencing separate from the fatal error?

[cyberflow]

@copper.chadwick  Hi there
It's not the superelevation that makes my C3D crash.
It's when i import the subassemblie.

I have tryed importing it again after fixing the AOR issue (Works fine on C3D 2018).

It's trully the C3D 2020 that crashes.

Dont know why it does that.

Even if i do a save as

[copper.chadwick]

@cyberflow ,

The issue I am working on is the crashing issue only, I did try to replicate the crashing, by importing the subassembly. I was not able to replicate that in my environment. (see the below screenshot of the subassembly after the import without a crash). I will try again, with the workflow you recommended via not doing a save as but just save. I wonder what might differ in our environments, is this the only subassembly pkt file that crashes? Lastly what happens if you open in in Subassembly composer 2018, save it and then open it in 2020 subassembly composer save it and then import it, to a new tool palette.

[cyberflow]

Hi @copper.chadwick 

Okies, Its the only SA that crashes since its the only one i tryed importing.

Il'l try to test your workflow to see how it goes.

By the way, you spoke about dependencies, what are you Dot net framework that you've got installed ?
Maybe it could impact something.

[copper.chadwick]

@cyberflow ,

I have dot NET versions 4.7.03056 installed. you can look that up in your registry editor at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\ in my registry I found that in the v4 folder either Client or Full listed behind version. I like to know if your installation fails the import on any other subassemblies and if so what version of dot NET is installed.

[cyberflow]

Hi @Anonymous

The latest one i've got is the 4.0.0.0

[copper.chadwick]

@cyberflow ,

You could try to update your . net via this link HERE.

That should help you update to 4.7 and see what happens from there, it is easy enough to "roll back" should you care to. Let me know how it goes.

[cyberflow]

Il'l try to give a try this week

Got a project to deliver this week before hitting the vacation 😉

But for sure im keeping you posted 

[cyberflow]

Hi @copper.chadwick  

Try importing a subassembly and creating a new toolpalette at the same time just to try it

I did that and it made me crash

[cyberflow]

Hi @copper.chadwick 

I've already got the latest .net framework

Ive got a project now and i need to use the c3d 2020 and it keeps on crashing 

[Anonymous]

Hello

Try to put in front of subassembly Sa.IsLayout do it in decision

Also check for faulty points, lines or shapes.

Had same problem as you, copy paste didn't work for me, added Sa.IsLayout at beggin of subassembly or a random Aux point just at zero.

Why it worked ? Don't know, but it worked

[cyberflow · Accepted solution]

I had a clean copy of the toolpalette files.

Recopied them and works fine now.

It seems that there's may be corrupted toolpalette i had.

[mpalaciosbaza]

try to put a assemblie to this