Home› Product Feedback

Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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

AuroraRonAuroraRon Member Posts: 139 PRO
in Product Feedback
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:

Comments

  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,967 image
    What format are you importing and which CAD system did it come from?
    Senior Director, Technical Services, EMEA
  • AuroraRonAuroraRon Member Posts: 139 PRO
    Inventor is one of them.  Supplier just tried again to export as a Parasolid and it just fails to translate.  I just created another support ticket.
    We also have no luck with step for engines, always errors that cause it to be unusable.  I have many examples from different engine companies you can try.  
  • AuroraRonAuroraRon Member Posts: 139 PRO
    After seven years....


    Your support ticket:
     "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.

    Lets hope importing large assemblies finally gets some attention.  It really bothers me to see all the advertising trying to get solidworks customers to switch over and when you do, it takes seven years to address the issues with imports not translating correctly or failing all together.


  • AuroraRonAuroraRon Member Posts: 139 PRO
    I tried to import another file today and waited two hours for Onshape to process only to end up with another unusable assembly. 

    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.    


  • AuroraRonAuroraRon Member Posts: 139 PRO

  • nick_papageorge_dayjobnick_papageorge_dayjob Member, csevp Posts: 1,049 PRO
    Have you tried importing in another CAD program? I keep a (free) hobby license of Fusion360, and if something does not come in clearly in OS, I try it in Fusion. I think "from memory of the last 3 years", anything that failed in OS also failed in Fusion.
  • AuroraRonAuroraRon Member Posts: 139 PRO
    Thank you, Nick.
    The demos I've tried so far have file size limitations.   


  • AuroraRonAuroraRon Member Posts: 139 PRO

    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?
  • lloyd_snelllloyd_snell Member Posts: 27 PRO

    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?

  • lloyd_snelllloyd_snell Member Posts: 27 PRO

    This engine model is so simple compared to the JD4 I am trying to import.

  • AuroraRonAuroraRon Member Posts: 139 PRO

    I can tell you from almost ten years here, it’s an ongoing issue. What error are you having, perhaps I can help.

  • MichialAndersonMichialAnderson Member Posts: 7 ✭

    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

  • lloyd_snelllloyd_snell Member Posts: 27 PRO

    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.

  • martin_kopplowmartin_kopplow Member Posts: 1,195 PRO

    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 …

  • AuroraRonAuroraRon Member Posts: 139 PRO

    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.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Sign In

Categories

Vanilla Forums