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.
beams 2.0
colin_manson
Member Posts: 2 ✭
Hi there
for some reason the custom profile giving an error it good last time i use it.
invalid number (NaN) .
I,m sure i do some wrong .
also thank you to the person that made the script it great.
for some reason the custom profile giving an error it good last time i use it.
invalid number (NaN) .
I,m sure i do some wrong .
also thank you to the person that made the script it great.
Tagged:
0
Comments
There are plenty on this forum who can help diagnose the issue, but it will require posting a link to a public document. See the stickied forum post checklist for more info.
thank you john for the idea
I have another feature that is showing it is broke.
I'll take a closer look this time
Nothing is showing up in the debug window.
Nothing much showing in mouseover tooltip
It looks like it is on V7
Updating to V8 fixes whatever happened.
I believe it was a different profile that broke last time too. On V6 and was fixed by updating to V7
Edit:
I just did a selective update on this feature going back one version at a time, it breaks only on V7 it looks like.
I'll test other profiles and see if I can find the other one that broke.
and v7 is working fine in other part studios in the same document.
Every profile on v7 in that part studio is showing the error. Even one that is literally just a circle.
I'm just trying to give you some debug insight in case there is a deeper problem.
I added a new beam feature to the bottom of the tree, and it was fine in every version.
now those other features that were breaking are stable in every previous version, including 7...
It appears adding another feature to the tree was enough to fix the entire part studio...
But at the same time, no other custom feature had any problems. (well they were not updated in the last day either..)
I don't have any other FSs that use document linking like beam profiles to test though