File size limits free public account

don_b

I can not find the limits as regard file size or account file size and I can not see the size of my file or account files....

NeilCooke

See part b) of my rejected answer. 

S1mon

There's a dimension limit of overall size. I forget what it is, but I want to say something like 1 or 10 km?

NeilCooke

S1mon said:

There's a dimension limit of overall size. I forget what it is, but I want to say something like 1 or 10 km?

It's 500m from the origin in all directions.

nick_papageorge073

don_b said:

NeilCooke said:

Just right-click a part or assembly tab and select move to document to see what it does. You can always undo it if you don't like the results.

Thanks for the help and I was able to move stuff into more documents .....and the project is moving along. 

One problem I am now having with this scheme is that there are different versions for multiple assemblies/ subassemblies and If I update to the latest version in all the documents/assemblies I lose parts, parts go out of position, and backtracking version history or further update complicates the problem....After finding and making a former version current and other massage of the assembly/part studios I currently have correct assemblies, part studios, plots etc. but they are of different versions.

Is there a way to fix this so an inadvertent update does not screw up the works?  

 

If you right click on an asm instance in the asm tree, there is an option called "pin reference". This will lock it to whatever version it is, even if you "update to latest" the rest of the parts in the assembly. The pin reference option will only show up if the part is referenced to a version. This could be what you are asking for.

don_b

Thank you.

I pinned the noted instance that showed "later version" (blue circle)  I am not sure what happens if I need to edit that part considering it is in multiple  version of assemblies or sub assemblies...and I do not understand how this different version problem occurred...perhaps because the part studios were referenced at different times when building a new sub-assembly. or delete an instance in an assembly that is in the assembly twice.....I found in help "updating references" which explains a lot of stuff....  

NeilCooke

a) there are no files b) there is no limit. 

don_b

ok they are Documents are there limits to the Document size?......I see old posts from 2015 talking about 100mb limit and 5 active documents.....Has that changed?

NeilCooke

See part b) of my rejected answer. 

don_b

thank you

don_b

Notifications (0 unread, 0 total)collapse allmark all as readdelete all

×CloseThis operation can not complete because it creates geometry that is beyond the system limit

steve_shubin

Maybe you could post the document because there’s a lot of helpful people here. They might be able to give you some advice on how to get things to work

S1mon

There's a dimension limit of overall size. I forget what it is, but I want to say something like 1 or 10 km?

don_b

I was able to paste the sketch ....I think I had to make a different plane ....sorry no longer have the problem to share 

NeilCooke

S1mon said:

There's a dimension limit of overall size. I forget what it is, but I want to say something like 1 or 10 km?

It's 500m from the origin in all directions.

S1mon

@NeilCooke
Is that a Parasolid limit or an Onshape limit?

NeilCooke

@S1mon it is a Parasolid limit. However, Parasolid is actually unitless so we (Onshape) choose the units and it’s a 10^9 range (I think) so the max is 1km and the min is 1micron. 

don_b

I am getting Resource Limit problems so I guess there are some sort of limits?

dirk_van_der_vaart

As it say,s contact Onshape support or report a bug

don_b

Perhaps the forum had an explanation.....or suggestion. 

NeilCooke

@don_b looks like you've got a lot of data in one document. Split it up. 

Good advice here: https://learn.onshape.com/learn/article/10-essential-onshape-tips

don_b

NeilCooke said:

@don_b looks like you've got a lot of data in one document. Split it up. 

Good advice here: https://learn.onshape.com/learn/article/10-essential-onshape-tips

Thank you....  I guess I need to do this....  "Tabs to 40 or fewer. As portions of your design mature, you can move those Tabs into their own Documents." 

Will I be able to have tabs from other documents in one assembly?

Will doing this ..."When a product is defined in multiple Documents, make links (or references) from objects in one Document to objects in a Version in another. You control when they update. This prevents the assembly corruption issues seen in file-based CAD systems."

does that allow other documents to be in one assembly .....is there a video about this?

NeilCooke

Just right-click a part or assembly tab and select move to document to see what it does. You can always undo it if you don't like the results.

rick_randall

NeilCooke said:

@don_b looks like you've got a lot of data in one document. Split it up. 

Good advice here: https://learn.onshape.com/learn/article/10-essential-onshape-tips

Thanks Neil for you're explanation. I too have seen that error label,(that don_b showed),  in some large files - mine was caused by sub assemblies being in a roll back state,creating some kind of weird feedback loop that became a resource hog and onshape didn't like it. All my own fault and it corrected itself once I rolled to end.

  I think the root cause was what you described though. (too much data in one document)  I'm getting better at managing large assemblies now, (and it's always better to get it right from the beginning instead of fixing it later).

don_b

NeilCooke said:

Just right-click a part or assembly tab and select move to document to see what it does. You can always undo it if you don't like the results.

Thanks for the help and I was able to move stuff into more documents .....and the project is moving along. 

One problem I am now having with this scheme is that there are different versions for multiple assemblies/ subassemblies and If I update to the latest version in all the documents/assemblies I lose parts, parts go out of position, and backtracking version history or further update complicates the problem....After finding and making a former version current and other massage of the assembly/part studios I currently have correct assemblies, part studios, plots etc. but they are of different versions.

Is there a way to fix this so an inadvertent update does not screw up the works?  

 

nick_papageorge073

don_b said:

NeilCooke said:

Just right-click a part or assembly tab and select move to document to see what it does. You can always undo it if you don't like the results.

Thanks for the help and I was able to move stuff into more documents .....and the project is moving along. 

One problem I am now having with this scheme is that there are different versions for multiple assemblies/ subassemblies and If I update to the latest version in all the documents/assemblies I lose parts, parts go out of position, and backtracking version history or further update complicates the problem....After finding and making a former version current and other massage of the assembly/part studios I currently have correct assemblies, part studios, plots etc. but they are of different versions.

Is there a way to fix this so an inadvertent update does not screw up the works?  

 

If you right click on an asm instance in the asm tree, there is an option called "pin reference". This will lock it to whatever version it is, even if you "update to latest" the rest of the parts in the assembly. The pin reference option will only show up if the part is referenced to a version. This could be what you are asking for.

don_b

Thank you.

I pinned the noted instance that showed "later version" (blue circle)  I am not sure what happens if I need to edit that part considering it is in multiple  version of assemblies or sub assemblies...and I do not understand how this different version problem occurred...perhaps because the part studios were referenced at different times when building a new sub-assembly. or delete an instance in an assembly that is in the assembly twice.....I found in help "updating references" which explains a lot of stuff....