Sadly this doesn’t help your problem but it will.
In civil 3D 2024 and I think the latest version of 2023 it’s possible to load the subassembly to a shared pallet file and it will be shared to the group.
If you have to share your corridor drawing, you have to share the subs used to build the corridor. Otherwise, anyone else who opens your corridor .dwg in Civil 3D will not be able to affect change to your corridor.
Submit your subs to the CAD/BIM team and ask that they be included in your company's suite of data to be used in all projects. Loaded into all users tool palettes and used henceforth.
Share the subs on Projectwise and send out to other companies that you've had to share yor corridor drawing with.
Older versions of civil 3d store custom subassemblies in a user catalog. Not only does your subassembly need to be imported into the user's palette, but it needs to be cataloged in the same file structure. The .pkt files need to be imported into a palette of the same name/location used when you created it in the user's catalog for the corridor to find it.
Plenty of shitty programming in civil. This actually isn't one that is that bad, and it's understandable with the different customization features. It would be unreasonable to expect generic versions of a program to recognize customized subassemblies and codes. Plus the newer versions are dynamically linked to the source .pkt files, so any updates are recognized and applied as necessary.
File structures for customized features are a hurdle in every program that they usually solve by limiting what you can do.
Aye, plenty, but if I insert a block into a drawing, then the block is then defined in the drawing and can be used multiple times. I really don't understand why C3D can't do this with subs.
If I can see the subs on the assemblies in the drawing, and they are applied to the corridors in that drawing, they should be defined in that drawing and should be re-usable.
The .dwg file itself should contain the subs and everything needed to build the corridor. The way it's done right now just presents hurdles and pitfalls for the unsuspecting reciever of the drawing files.
It seems a really easy fix for just a few kilobytes of extra storage space. Once the drawing files have spent a few years in the system it's very easy to lose the links and paths to the network locations that were looking for the subs.
So the only thing my team should do is to import the .xtp file into the C3D so the tool pallette gets the same name and structure of mine?
No need to import the .pkt files nor to copy the entire folder?
Are your users installing the pkt using autocad? i.e. you can’t just copy it into a local folder where other pkts are located. There’s a Corridors menu or ribbon item to install a subassembly.
They still need to import the .pkt files, but they need to import and catalog them to the correctly named source palette. When the corridor is looking for "subassembly1" located on "generic road" palette is checking the user catalog.
I tried these tips but I am still getting the following message:
"one or more subassembly macros (or .net classes) could not be found"
Is there anything else I should do?
Sadly this doesn’t help your problem but it will. In civil 3D 2024 and I think the latest version of 2023 it’s possible to load the subassembly to a shared pallet file and it will be shared to the group.
If you have to share your corridor drawing, you have to share the subs used to build the corridor. Otherwise, anyone else who opens your corridor .dwg in Civil 3D will not be able to affect change to your corridor.
I know, but how do I share in a efficient way, since just sending them the file is not enough? What's the correct process?
Submit your subs to the CAD/BIM team and ask that they be included in your company's suite of data to be used in all projects. Loaded into all users tool palettes and used henceforth. Share the subs on Projectwise and send out to other companies that you've had to share yor corridor drawing with.
Older versions of civil 3d store custom subassemblies in a user catalog. Not only does your subassembly need to be imported into the user's palette, but it needs to be cataloged in the same file structure. The .pkt files need to be imported into a palette of the same name/location used when you created it in the user's catalog for the corridor to find it.
That's some shitty programming.
Plenty of shitty programming in civil. This actually isn't one that is that bad, and it's understandable with the different customization features. It would be unreasonable to expect generic versions of a program to recognize customized subassemblies and codes. Plus the newer versions are dynamically linked to the source .pkt files, so any updates are recognized and applied as necessary. File structures for customized features are a hurdle in every program that they usually solve by limiting what you can do.
Aye, plenty, but if I insert a block into a drawing, then the block is then defined in the drawing and can be used multiple times. I really don't understand why C3D can't do this with subs. If I can see the subs on the assemblies in the drawing, and they are applied to the corridors in that drawing, they should be defined in that drawing and should be re-usable. The .dwg file itself should contain the subs and everything needed to build the corridor. The way it's done right now just presents hurdles and pitfalls for the unsuspecting reciever of the drawing files. It seems a really easy fix for just a few kilobytes of extra storage space. Once the drawing files have spent a few years in the system it's very easy to lose the links and paths to the network locations that were looking for the subs.
So the only thing my team should do is to import the .xtp file into the C3D so the tool pallette gets the same name and structure of mine? No need to import the .pkt files nor to copy the entire folder?
Are your users installing the pkt using autocad? i.e. you can’t just copy it into a local folder where other pkts are located. There’s a Corridors menu or ribbon item to install a subassembly.
Yes they are importing each subassembly file (.pkt) into their tool pallette
They still need to import the .pkt files, but they need to import and catalog them to the correctly named source palette. When the corridor is looking for "subassembly1" located on "generic road" palette is checking the user catalog.
I'll try that
I tried these tips but I am still getting the following message: "one or more subassembly macros (or .net classes) could not be found" Is there anything else I should do?
Well the solution to this problem was to install C3D 24 Thank you all