Skip to main content
L
lylebeidler1-Visitor
1-Visitor
January 24, 2012
Question

offset lines don't go away?

  • January 24, 2012
  • 5 replies
  • 1183 views
I thought I recalled in earlier builds of Pro/E that if you create offset
lines for an explode state, when you unexpolde the assembly, the offset
lines automatically hide. However, I discovered today that's not working.
Is there a config setting I'm missing, or is this a bug or intended
behavior? Or am I just remembering incorrectly?

We're using WF3, M160

Thanks



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

5 replies

B
bokm96061-Visitor
1-Visitor
January 24, 2012

i was experiencing the same issue on Win & WF 5.0 m100 just the other day.


Almost behaving like the Offset lines were in a graphic cache. I think a Regeneration of the assembly made the them dissappear.



But yes, very annoying.

B
BobSchwerdlin1-Visitor
1-Visitor
January 24, 2012
I'm on WF 5 - M040
It works correctly for me. Use it all the time.

Bob
B
bokm96061-Visitor
1-Visitor
January 24, 2012

do you utilize combined states?


Maybe it has something to do with combine the rep state, explode, and view orientation into a "combined" state?

B
bokm96061-Visitor
1-Visitor
January 24, 2012

also what OS? we are on x64-win7.

B
BobSchwerdlin1-Visitor
1-Visitor
January 24, 2012
WF5 - M040

We use exploded states, simplified reps and style on drawings.
WinXP-64 on my machine. Others use a mixture of (Win7-64 and WF 5 - M080) and (Win7-64 and WF5 M110). No real issues.
Terms & ConditionsAccessibility statement