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.
Configured variables not properly rendering in assembly
In one of my medium-size assemblies I have been having issues with configured variables rendering. It is a PVC-based assembly, and I have 1 PVC part with a configured variable length inserted everywhere. I did not have this issue until I completed the assembly and made drawings and different view states, but now it happens frequently. Seemingly at random, all PVC pipes will revert to their default 1 inch length, leaving massive gaps throughout the assembly. When I select them in the instance manager, they still show their correct configured length, but if I try to edit any of them in context, they appear as the default length. Sometimes it fixes itself after a minute or two, but the best way I've found to fix it is to look at an older version where the pipes are rendered correctly and then pull up my current workspace to find all the pipes as they should be (even this only works sometimes). I'm not suffering any major performance issues, and it happens in both the main assembly and in drawings. I did just start using a custom tool to handle wiring, but I don't think this is the cause of the issue. There are many other configured parts and even other configured variables that do not suffer from this issue, and I can't find anything strange in the original PVC part studio. I'm still fairly new to Onshape, so I don't know if this kind of thing is a common issue, but so far it has only been happening in this assembly. I've submitted a support ticket, but any other advice would be appreciated!
Comments
ust heard back from my support ticket, I was told to clear the graphics cache and force reload. While this helped for the assembly I first found the issue in, it did not consistently work. I started a new assembly today and when one piece of PVC became bugged, I cleared the cache and did the reload, which caused every piece of PVC to become bugged. I will submit another support ticket, but here is what I have found so far:
-sometimes every piece of PVC renders incorrectly, sometimes it is only pieces contained in subassemblies
-viewing the subassemblies in a new tab renders the pipes correctly, but it does not change the bugged ones in the main assembly
-inserting a new instance of the same subassembly does not fix the issue, the new instance renders in with bugged PVC too
-sometimes persists through multiple cache clear/force reload cycles, subassembly PVC is especially persistent
-sometimes solved by looking at older versions, but appeared in my new assembly before I created any versions so this is off the table
-checking mates and mate connectors does not solve the issue, neither does any sort of "show all" function
-editing in context shows a 1 inch length while the instance manager in the assembly shows the correct length
-the model is still rigid and there are no issues with the mates
-most likely not a processing issue, it still happens with only 2 tabs open
-I have experienced other graphical glitches before but they were all solved by clearing the cache and reloading
-tried hard and soft reloads with and without clearing the cache, none helped
-changing the version of the subassembly did not do anything to help; pipes partially or incorrectly rendered in and could not be selected but could be rotated about, and restoring it back to the correct version did not fix the bug
-I am running the most recent version of Microsoft edge
-navigating away from the file, opening in a new tab, duplicating tab, etc. don't help
-opening the file in Firefox makes no difference
I'm not sure if this is happening on other computers at my company, but it is disrupting my workflow and could really get in the way of a briefing I have to give in a few days. I'm now even more stumped on what to do, but at this point I am happy to try anything
For reference: top section is a subassembly inserted from another document (bugged pipes), and the bottom section was all built in this workspace (correct pipes). There is one pipe of the correct length up top but it is not part of the subassembly. This is what the top subassembly looks like when opened in another tab: