Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Fix Importing Large Files
AuroraRon
Member Posts: 139 PRO
I am experiencing constant import issues with Onshape when working with large files. Despite using Onshape for seven years, I have yet to notice any improvement in this area. I love using Onshape, but working with files that are not created in Onshape becomes very difficult or impossible. I would settle for just a shell, but parts with errors keep wrecking the complete assembly.
Tagged:
1
Comments
"Failed to import parasolid"
has been identified as a bug and we are working on it. As soon as this gets addressed and is pushed to cad.onshape.com, we will update this ticket to so you can confirm the update.
Does anyone know of a way to convert or import a Parasolid or stp file to one big solid or shell so that I can at least show something on a drawing? It's been like this for every large assembly since I started here seven years ago and still nothing from Onshape.
The demos I've tried so far have file size limitations.
After seven years of using Onshape, I still can't get any large file format to import into Onshape that is remotely usable. It does not matter who the source is. Will the importing from other formats ever be fixed?
I am currently trying to import a John Deere Engine - AH SNAP is the word of the day …. Nothing is working! How can I expect to design off-road equipment that will include several large imports, such as Hydraulic Pumps and motors, an Engine, Axles, Consoles, Seats, and other imported components? Can Onshape handle it?
This engine model is so simple compared to the JD4 I am trying to import.
I can tell you from almost ten years here, it’s an ongoing issue. What error are you having, perhaps I can help.
We have been having the same issue with aerospace composites. They will either fail the imports or take hours to import with faulty geometry. Has anyone found a work around. We are sent STEP files from our customers and it is coming mainly from CATIA
Still working on finding a valid solution. I have the file as an x_t, which is nothing but parts, 2393 parts. I created a copy and began deleting parts, currently 638 parts and thousands of surfaces. I inserted the parts into an assembly, but some features are represented only as surfaces. John Deere, why? Also, download the file that generates the assembly files, in addition to the parts studio. I have copied this download also and am going to explore deleting unnecessary assemblies to create a lighter graphical requirement.
Continuing to search for a tolerable solution.
When I get files, I usually don't delete stuff, but derive only the parts required into my new design. That's generally less work, and I can go get a forgotten part anytime, or replace with updated versions I get.
My main trouble is that when imported parts are faulty, OS provides little to none tools to analyse and repair. Sometimes it could be fixed by recreating a smallish warped surface or a fillet gone wrong, which would take seconds to do, but finding those is a nightmare. I just got a STEP export from a Fusion guy and am having the issue again. I wanted to make a small change on one end, but I need to repair the model first …
We have repeatedly verified that these STEP files are valid and import correctly in other CAD systems, across multiple suppliers and over many years.
In Onshape, large or complex imports still frequently fail or result in unusable geometry, which makes external data workflows difficult to rely on.
There seems to be no roadmap for improving import robustness. It has been this way from day one.
Update on my engine file management journey.
As previously noted, I imported a John Deere Engine file as an x_t, made a copy, and deleted roughly 75% of the parts. There were almost 400 bolts.
Next, imported the model and Split into multiple documents, 99 assembly tabs, a parts tab, and a CAD input folder.
Next, starting with the assemblies loaded to the far right, created a configuration table On/Off and subsequent rows, On and Off. On represented the original assembly, and Off was used only to move forward the required parts, with component modeling based on space and volume needs. One of the wiring harnesses had over 900 parts that were not required for my project.
Once these basic tabs were developed, future tabs would show that assembly, and again the On/Off configuration table with an On and Off row. So first the reference assemblies had to be configured to match the state. So op the Change Configuration for each assembly and configure to the On/Off table. Then, in the current assembly, select the Off Configuration, select the parts that are new to the assembly, and add them to the On/Off table. The last step is to suppress those items in the instance table, suppress and the On/Off configuration table is set.
I Fixed the oil pan and grouped the entire assembly.
In case anyone has comments about Performance.
I think there's a song here 99 assemblies in the scroll, Open it up and configure up, 98 assemblies in the scroll.
Two items, the alternator and radiator surge tank, are surface geometry, 6000+ for the alternator and 262 for the radiator surge tank. Need to figure out how to manage these. Sometimes wonder if the big CAD systems at big companies are just messing with us.
Is there anything else I can do to the file to make it more manageable when placing it, and creating parts in context with a native Onshape Assembly?
Here is the engine with roughly 2500 parts turned off from the original picture.