part missing in scene and drawing

[Anonymous]

I have a fairly large assembly that is calling out one
assembly(pct-00237-001) that has another assembly(pca-00237-001) under it.
We originally had a panel assembled in PCA-00237-001, we have decided to
have it add later in pct-00237-001. For some reason in my highest level
assembly the panel shows up in model space but not in the scene or the
drawing. It is marked as visible in the scene.

In what I think is an unrelated issue I am now getting a error when I do a
recover on the top level assembly (otl-00237-001) I am told there are no
errors in the database. Then MDT starts to regenerate the model and I get
this warning 27 times:
Warning: Incomplete assembly data was detected. Attempting database
recovery.
(8)

Finally I am told there are 57 errors found and 57 errors fixed.
Auditing Mechanical desktop Data complete

pca-00237-001.dwg performed audit of feature suppression data in 53 updated
xref(s).
Performed audit of feature suppression data in 1 updated Xref file(s).
Please save otl-00237-001.dwg to preserve audit result.

I save the file and do a recover on pca-00237-001 (no errors found),
pct-00237-001 (no errors found) and tol-00237-001
no errors found.

I still can not see my panel in the otl-00237-001 scenes.

Glenn Freeman

[Anonymous]

Oh yeah the original panel was created using either mdt 4 or 5. I then
modified the panel in 6.

Glenn Freeman

"Glenn Freeman" wrote in message
news:30ECC4BF20F1F9AF83E535D8970BA0A8@in.WebX.maYIadrTaRb...
> I have a fairly large assembly that is calling out one
> assembly(pct-00237-001) that has another assembly(pca-00237-001) under it.
> We originally had a panel assembled in PCA-00237-001, we have decided to
> have it add later in pct-00237-001. For some reason in my highest level
> assembly the panel shows up in model space but not in the scene or the
> drawing. It is marked as visible in the scene.
>
> In what I think is an unrelated issue I am now getting a error when I do
a
> recover on the top level assembly (otl-00237-001) I am told there are no
> errors in the database. Then MDT starts to regenerate the model and I get
> this warning 27 times:
> Warning: Incomplete assembly data was detected. Attempting database
> recovery.
> (8)
>
> Finally I am told there are 57 errors found and 57 errors fixed.
> Auditing Mechanical desktop Data complete
>
> pca-00237-001.dwg performed audit of feature suppression data in 53
updated
> xref(s).
> Performed audit of feature suppression data in 1 updated Xref file(s).
> Please save otl-00237-001.dwg to preserve audit result.
>
> I save the file and do a recover on pca-00237-001 (no errors found),
> pct-00237-001 (no errors found) and tol-00237-001
> no errors found.
>
> I still can not see my panel in the otl-00237-001 scenes.
>
> Glenn Freeman
>
>

[Anonymous]

Did you recently localize the panel you can't see in Scene mode? I turned in a bug the
other day that sounds similar, but it happened after localizing subs. The fix was to
update the scenes before localizing, and I think I could externalize and they would show
up in scene mode, so maybe try externalizing, updating the scene, and then localizing it
again.

--
Kent


"Glenn Freeman" wrote in message
news:30ECC4BF20F1F9AF83E535D8970BA0A8@in.WebX.maYIadrTaRb...
> I have a fairly large assembly that is calling out one
> assembly(pct-00237-001) that has another assembly(pca-00237-001) under it.
> We originally had a panel assembled in PCA-00237-001, we have decided to
> have it add later in pct-00237-001. For some reason in my highest level
> assembly the panel shows up in model space but not in the scene or the
> drawing. It is marked as visible in the scene.
>
> In what I think is an unrelated issue I am now getting a error when I do a
> recover on the top level assembly (otl-00237-001) I am told there are no
> errors in the database. Then MDT starts to regenerate the model and I get
> this warning 27 times:
> Warning: Incomplete assembly data was detected. Attempting database
> recovery.
> (8)
>
> Finally I am told there are 57 errors found and 57 errors fixed.
> Auditing Mechanical desktop Data complete
>
> pca-00237-001.dwg performed audit of feature suppression data in 53 updated
> xref(s).
> Performed audit of feature suppression data in 1 updated Xref file(s).
> Please save otl-00237-001.dwg to preserve audit result.
>
> I save the file and do a recover on pca-00237-001 (no errors found),
> pct-00237-001 (no errors found) and tol-00237-001
> no errors found.
>
> I still can not see my panel in the otl-00237-001 scenes.
>
> Glenn Freeman
>
>

[Anonymous]

Nope. I opened the file pca-00237-001 and deleted the part and a couple of
screws. After updated the scenes and 2d drawings in that file, I opened up
the pct-00237 file. I added the panel and screws, updated the scenes and 2d
views. When I opened otl-00237-001, I was able to see the panel in the
model space but not in the scene. I have since been able to create a new
scene and the panel appears. I do not want to create the 2d views over
again due to the additional loss of time. I have already spent about 2 and
a half hours trying to solve this problem and if I have to recreate the 2d
views it is going to cost me another hour and a half. Makes me I wish I was
paid by the hour.

Glenn Freeman


"Kent Keller" wrote in message
news:4CD907F722FE50C39C332490BE949906@in.WebX.maYIadrTaRb...
> Did you recently localize the panel you can't see in Scene mode? I
turned in a bug the
> other day that sounds similar, but it happened after localizing subs.
The fix was to
> update the scenes before localizing, and I think I could externalize and
they would show
> up in scene mode, so maybe try externalizing, updating the scene, and then
localizing it
> again.
>
> --
> Kent
>
>
> "Glenn Freeman" wrote in message
> news:30ECC4BF20F1F9AF83E535D8970BA0A8@in.WebX.maYIadrTaRb...
> > I have a fairly large assembly that is calling out one
> > assembly(pct-00237-001) that has another assembly(pca-00237-001) under
it.
> > We originally had a panel assembled in PCA-00237-001, we have decided to
> > have it add later in pct-00237-001. For some reason in my highest level
> > assembly the panel shows up in model space but not in the scene or the
> > drawing. It is marked as visible in the scene.
> >
> > In what I think is an unrelated issue I am now getting a error when I
do a
> > recover on the top level assembly (otl-00237-001) I am told there are no
> > errors in the database. Then MDT starts to regenerate the model and I
get
> > this warning 27 times:
> > Warning: Incomplete assembly data was detected. Attempting database
> > recovery.
> > (8)
> >
> > Finally I am told there are 57 errors found and 57 errors fixed.
> > Auditing Mechanical desktop Data complete
> >
> > pca-00237-001.dwg performed audit of feature suppression data in 53
updated
> > xref(s).
> > Performed audit of feature suppression data in 1 updated Xref file(s).
> > Please save otl-00237-001.dwg to preserve audit result.
> >
> > I save the file and do a recover on pca-00237-001 (no errors found),
> > pct-00237-001 (no errors found) and tol-00237-001
> > no errors found.
> >
> > I still can not see my panel in the otl-00237-001 scenes.
> >
> > Glenn Freeman
> >
> >
>
>

[Anonymous]

Glenn

You are sure the visibility is turned on for the part in Scene mode? If you can post it I
would take a look.

--
Kent


"Glenn Freeman" wrote in message
news:056D20C26B0F08DB57B3396AB376F2F8@in.WebX.maYIadrTaRb...
> Nope. I opened the file pca-00237-001 and deleted the part and a couple of
> screws. After updated the scenes and 2d drawings in that file, I opened up
> the pct-00237 file. I added the panel and screws, updated the scenes and 2d
> views. When I opened otl-00237-001, I was able to see the panel in the
> model space but not in the scene. I have since been able to create a new
> scene and the panel appears. I do not want to create the 2d views over
> again due to the additional loss of time. I have already spent about 2 and
> a half hours trying to solve this problem and if I have to recreate the 2d
> views it is going to cost me another hour and a half. Makes me I wish I was
> paid by the hour.
>

[Anonymous]

Yes, the part is visible. I just got a call from our local reseller who
called Autodesk and I was told I am SOL. I can not move a part from a
subassembly of a subassembly to the subassembly and expect the part to show
up in an original scene of the top level assembly unless I use the
amresctructure command and move the part from the subassembly of the sub
assembly up to the sub assembly from inside the highest level assembly.
(Say that 5 times fast)

I would post the file but it is about 40 meg unzipped and in order to upload
it would take about 3 years.

Glenn Freeman


"Kent Keller" wrote in message
news:CD7F47D5FC9F48D7D2962FC5C9A7807D@in.WebX.maYIadrTaRb...
> Glenn
>
> You are sure the visibility is turned on for the part in Scene mode? If
you can post it I
> would take a look.
>
> --
> Kent
>
>
> "Glenn Freeman" wrote in message
> news:056D20C26B0F08DB57B3396AB376F2F8@in.WebX.maYIadrTaRb...
> > Nope. I opened the file pca-00237-001 and deleted the part and a couple
of
> > screws. After updated the scenes and 2d drawings in that file, I opened
up
> > the pct-00237 file. I added the panel and screws, updated the scenes
and 2d
> > views. When I opened otl-00237-001, I was able to see the panel in the
> > model space but not in the scene. I have since been able to create a
new
> > scene and the panel appears. I do not want to create the 2d views over
> > again due to the additional loss of time. I have already spent about 2
and
> > a half hours trying to solve this problem and if I have to recreate the
2d
> > views it is going to cost me another hour and a half. Makes me I wish I
was
> > paid by the hour.
> >
>
>
>

[Anonymous]

Hmmm I think I am not understanding something nothing new. It seems to me it should
work, but then I haven't tried it. I have never used amrestructure, I have always just
dragged them in the browser. They said there is a difference between doing it in the
browser and doing it with amrestructure?

Maybe Chuck will straighten us out if he sees this.

3 years huh..... I will check back. Till then.......

--
Kent


"Glenn Freeman" wrote in message
news:546F70DDDCB2CE883F74E2AABEF27F53@in.WebX.maYIadrTaRb...

>I can not move a part from a
> subassembly of a subassembly to the subassembly and expect the part to show
> up in an original scene of the top level assembly unless I use the
> amresctructure command and move the part from the subassembly of the sub
> assembly up to the sub assembly from inside the highest level assembly.
> (Say that 5 times fast)
>
> I would post the file but it is about 40 meg unzipped and in order to upload
> it would take about 3 years.
>
> Glenn Freeman

[Anonymous]

Glenn,

I could be totally wrong, but I think someone is pulling your leg and you
have a data base problem. I routinely drag components from one assy to the
next from within any level in the assembly, delete a part from one sub and
add it to another, etc. etc. and do not loose, in the top assy, parts from
scenes or dwg views. I've never heard of amrestructure, until you mentioned
it.

Some things I'd look at:

Have you manually forced an update of the scenes and are you sure they
aren't locked?

Do you put part or subassy Definitions or Instances (emphasis on both of
them) on layers other than 0? You open a can of worms if you do and you
need to check the layer status, etc. for all your parts and assy's. This
can apply to the scenes also, as they have some strange ties to the layer
that's current when they are created.

I strongly suggest you set audit control to always if you haven't.

Have you gone through any external parts or assy's with audit control on,
done an amupdate all, possibly an audit, etc.?

A long shot is to instance your top level assy into a new assy, localize it,
externalize it and see what happens. Keep backup copies of everything in
case dwg views are lost, etc.

Good luck with it,
Jeff
-------------------------------------------

"Glenn Freeman" wrote in message
news:546F70DDDCB2CE883F74E2AABEF27F53@in.WebX.maYIadrTaRb...
Yes, the part is visible. I just got a call from our local reseller who
called Autodesk and I was told I am SOL. I can not move a part from a
subassembly of a subassembly to the subassembly and expect the part to show
up in an original scene of the top level assembly unless I use the
amresctructure command and move the part from the subassembly of the sub
assembly up to the sub assembly from inside the highest level assembly.
(Say that 5 times fast)

I would post the file but it is about 40 meg unzipped and in order to upload
it would take about 3 years.

Glenn Freeman

[Anonymous]

Kent/Jeff/Glenn,

Just so we are all clear on amrestructure:

When you drag components from one subassembly in the browser to another
location (up or down the
assembly tree), this is using the amrestructure command is used. This would
be the same as if you
had typed in the command, amrestructure.

I'm in the process of trying to reproduce Glenn's problem with respect to
doing a restructure OUTSIDE of
the context of the top level assembly and losing graphics in the top level
assembly as a result of it.
I'll reply to this thread if I find anything out.

--
Chuck.Savatsky@Autodesk.com

Chuck Savatsky
MDT developer
Autodesk

Chuck.Savatsky@Autodesk.com
"Jeff Howard" wrote in message
news:4D7F3029DA32B26A9BDF44791671C370@in.WebX.maYIadrTaRb...
> Glenn,
>
> I could be totally wrong, but I think someone is pulling your leg and you
> have a data base problem. I routinely drag components from one assy to
the
> next from within any level in the assembly, delete a part from one sub and
> add it to another, etc. etc. and do not loose, in the top assy, parts from
> scenes or dwg views. I've never heard of amrestructure, until you
mentioned
> it.
>
> Some things I'd look at:
>
> Have you manually forced an update of the scenes and are you sure they
> aren't locked?
>
> Do you put part or subassy Definitions or Instances (emphasis on both of
> them) on layers other than 0? You open a can of worms if you do and you
> need to check the layer status, etc. for all your parts and assy's. This
> can apply to the scenes also, as they have some strange ties to the layer
> that's current when they are created.
>
> I strongly suggest you set audit control to always if you haven't.
>
> Have you gone through any external parts or assy's with audit control on,
> done an amupdate all, possibly an audit, etc.?
>
> A long shot is to instance your top level assy into a new assy, localize
it,
> externalize it and see what happens. Keep backup copies of everything in
> case dwg views are lost, etc.
>
> Good luck with it,
> Jeff
> -------------------------------------------
>
> "Glenn Freeman" wrote in message
> news:546F70DDDCB2CE883F74E2AABEF27F53@in.WebX.maYIadrTaRb...
> Yes, the part is visible. I just got a call from our local reseller who
> called Autodesk and I was told I am SOL. I can not move a part from a
> subassembly of a subassembly to the subassembly and expect the part to
show
> up in an original scene of the top level assembly unless I use the
> amresctructure command and move the part from the subassembly of the sub
> assembly up to the sub assembly from inside the highest level assembly.
> (Say that 5 times fast)
>
> I would post the file but it is about 40 meg unzipped and in order to
upload
> it would take about 3 years.
>
> Glenn Freeman
>
>
>

[Anonymous]

I verified that we do indeed have a bug relating to this. If I do a
restructure outside
of the assembly, I am losing graphics in the scene for the components I
restructured.
As of this point, I do not know a better workaround than recreating the
scene. Externalize/localize
does not help. I'm still looking for a better workaround. The bug is
definitely something
that should be fixed in SP2.

--
Chuck.Savatsky@Autodesk.com

Chuck Savatsky
MDT developer
Autodesk

Chuck.Savatsky@Autodesk.com
"Chuck Savatsky" wrote in message
news:6DFEA5E6864D6CE7F6CF49EA5D0D9F27@in.WebX.maYIadrTaRb...
> Kent/Jeff/Glenn,
>
> Just so we are all clear on amrestructure:
>
> When you drag components from one subassembly in the browser to another
> location (up or down the
> assembly tree), this is using the amrestructure command is used. This
would
> be the same as if you
> had typed in the command, amrestructure.
>
> I'm in the process of trying to reproduce Glenn's problem with respect to
> doing a restructure OUTSIDE of
> the context of the top level assembly and losing graphics in the top level
> assembly as a result of it.
> I'll reply to this thread if I find anything out.
>
> --
> Chuck.Savatsky@Autodesk.com
>
> Chuck Savatsky
> MDT developer
> Autodesk
>
> Chuck.Savatsky@Autodesk.com
> "Jeff Howard" wrote in message
> news:4D7F3029DA32B26A9BDF44791671C370@in.WebX.maYIadrTaRb...
> > Glenn,
> >
> > I could be totally wrong, but I think someone is pulling your leg and
you
> > have a data base problem. I routinely drag components from one assy to
> the
> > next from within any level in the assembly, delete a part from one sub
and
> > add it to another, etc. etc. and do not loose, in the top assy, parts
from
> > scenes or dwg views. I've never heard of amrestructure, until you
> mentioned
> > it.
> >
> > Some things I'd look at:
> >
> > Have you manually forced an update of the scenes and are you sure they
> > aren't locked?
> >
> > Do you put part or subassy Definitions or Instances (emphasis on both of
> > them) on layers other than 0? You open a can of worms if you do and you
> > need to check the layer status, etc. for all your parts and assy's.
This
> > can apply to the scenes also, as they have some strange ties to the
layer
> > that's current when they are created.
> >
> > I strongly suggest you set audit control to always if you haven't.
> >
> > Have you gone through any external parts or assy's with audit control
on,
> > done an amupdate all, possibly an audit, etc.?
> >
> > A long shot is to instance your top level assy into a new assy, localize
> it,
> > externalize it and see what happens. Keep backup copies of everything
in
> > case dwg views are lost, etc.
> >
> > Good luck with it,
> > Jeff
> > -------------------------------------------
> >
> > "Glenn Freeman" wrote in message
> > news:546F70DDDCB2CE883F74E2AABEF27F53@in.WebX.maYIadrTaRb...
> > Yes, the part is visible. I just got a call from our local reseller who
> > called Autodesk and I was told I am SOL. I can not move a part from a
> > subassembly of a subassembly to the subassembly and expect the part to
> show
> > up in an original scene of the top level assembly unless I use the
> > amresctructure command and move the part from the subassembly of the sub
> > assembly up to the sub assembly from inside the highest level assembly.
> > (Say that 5 times fast)
> >
> > I would post the file but it is about 40 meg unzipped and in order to
> upload
> > it would take about 3 years.
> >
> > Glenn Freeman
> >
> >
> >
>
>

[Anonymous]

Thanks for the feedback Chuck.

Would undoing the steps in the lower assembly, and then redoing them in the upper
assembly work. Or maybe I am not understand what "outside of the assembly" means. I
will have to try it if I get a chance.

--
Kent


"Chuck Savatsky" wrote in message
news:8FF55B2E8687EDDD426917B4B4CDA7CE@in.WebX.maYIadrTaRb...
> I verified that we do indeed have a bug relating to this. If I do a
> restructure outside
> of the assembly, I am losing graphics in the scene for the components I
> restructured.
> As of this point, I do not know a better workaround than recreating the
> scene. Externalize/localize
> does not help. I'm still looking for a better workaround. The bug is
> definitely something
> that should be fixed in SP2.
>
> --
> Chuck.Savatsky@Autodesk.com
>
> Chuck Savatsky
> MDT developer
> Autodesk
>
> Chuck.Savatsky@Autodesk.com
> "Chuck Savatsky" wrote in message
> news:6DFEA5E6864D6CE7F6CF49EA5D0D9F27@in.WebX.maYIadrTaRb...
> > Kent/Jeff/Glenn,
> >
> > Just so we are all clear on amrestructure:
> >
> > When you drag components from one subassembly in the browser to another
> > location (up or down the
> > assembly tree), this is using the amrestructure command is used. This
> would
> > be the same as if you
> > had typed in the command, amrestructure.
> >
> > I'm in the process of trying to reproduce Glenn's problem with respect to
> > doing a restructure OUTSIDE of
> > the context of the top level assembly and losing graphics in the top level
> > assembly as a result of it.
> > I'll reply to this thread if I find anything out.
> >
> > --
> > Chuck.Savatsky@Autodesk.com
> >
> > Chuck Savatsky
> > MDT developer
> > Autodesk
> >
> > Chuck.Savatsky@Autodesk.com
> > "Jeff Howard" wrote in message
> > news:4D7F3029DA32B26A9BDF44791671C370@in.WebX.maYIadrTaRb...
> > > Glenn,
> > >
> > > I could be totally wrong, but I think someone is pulling your leg and
> you
> > > have a data base problem. I routinely drag components from one assy to
> > the
> > > next from within any level in the assembly, delete a part from one sub
> and
> > > add it to another, etc. etc. and do not loose, in the top assy, parts
> from
> > > scenes or dwg views. I've never heard of amrestructure, until you
> > mentioned
> > > it.
> > >
> > > Some things I'd look at:
> > >
> > > Have you manually forced an update of the scenes and are you sure they
> > > aren't locked?
> > >
> > > Do you put part or subassy Definitions or Instances (emphasis on both of
> > > them) on layers other than 0? You open a can of worms if you do and you
> > > need to check the layer status, etc. for all your parts and assy's.
> This
> > > can apply to the scenes also, as they have some strange ties to the
> layer
> > > that's current when they are created.
> > >
> > > I strongly suggest you set audit control to always if you haven't.
> > >
> > > Have you gone through any external parts or assy's with audit control
> on,
> > > done an amupdate all, possibly an audit, etc.?
> > >
> > > A long shot is to instance your top level assy into a new assy, localize
> > it,
> > > externalize it and see what happens. Keep backup copies of everything
> in
> > > case dwg views are lost, etc.
> > >
> > > Good luck with it,
> > > Jeff
> > > -------------------------------------------
> > >
> > > "Glenn Freeman" wrote in message
> > > news:546F70DDDCB2CE883F74E2AABEF27F53@in.WebX.maYIadrTaRb...
> > > Yes, the part is visible. I just got a call from our local reseller who
> > > called Autodesk and I was told I am SOL. I can not move a part from a
> > > subassembly of a subassembly to the subassembly and expect the part to
> > show
> > > up in an original scene of the top level assembly unless I use the
> > > amresctructure command and move the part from the subassembly of the sub
> > > assembly up to the sub assembly from inside the highest level assembly.
> > > (Say that 5 times fast)
> > >
> > > I would post the file but it is about 40 meg unzipped and in order to
> > upload
> > > it would take about 3 years.
> > >
> > > Glenn Freeman
> > >
> > >
> > >
> >
> >
>
>

[Anonymous]

Kent,

What I mean by outside the top level assembly is as follows:

Assembly looks as follows where all subs are external:

A
Sub1
Sub2
Sub3
P1
P2

Create a scene in A.
Save, close A.

Open Sub1 drawing.
Restructure Sub3 to be directly underneath Sub1. (Sub 2 is now empty of
parts).
Save, close Sub1.

Open up A.

Assembly looks as follows:

A
Sub1
Sub2 (empty)
Sub3
P1
P2

Activate scene.
Graphics for P1 and P2 are not visible, even though in the browser, P1 and
P2 are visible.

If the restructure happens while A is open, this problem does not occur.
However, it should be
ok for the user to do this while Sub1 is open. The graphics should
reappear.

I believe what product support is referring to is that ALL REFERENCES to P1
and P2 in the top level
assembly will be lost when this occurs. That is if there are refdims in a
view of the scene that are
referring to P1 or P2, they will be orphaned. This is also true of 3D
constraints and tweaks. This is as designed,
however loss of graphics in the scene is not.

In general, it is not recommended to do things like restructure outside of
the top level assembly,
but for various reasons, I'm sure it must be done at times.
No competitor that I know of supports the maintaining of such references
when a restructure occurs outside
of the assembly where the references reside. Last time I checked,
SolidWorks did not even support
maintaining dimension references when restructure occurred inside the
assembly.
Maintaining such references is a difficult problem, to say the least.


--
Chuck.Savatsky@Autodesk.com

Chuck Savatsky
MDT developer
Autodesk

Chuck.Savatsky@Autodesk.com
"Kent Keller" wrote in message
news:090DF7DFFD7CD8D03112D8F1E2A4A428@in.WebX.maYIadrTaRb...
> Thanks for the feedback Chuck.
>
> Would undoing the steps in the lower assembly, and then redoing them in
the upper
> assembly work. Or maybe I am not understand what "outside of the
assembly" means. I
> will have to try it if I get a chance.
>
> --
> Kent
>
>
> "Chuck Savatsky" wrote in message
> news:8FF55B2E8687EDDD426917B4B4CDA7CE@in.WebX.maYIadrTaRb...
> > I verified that we do indeed have a bug relating to this. If I do a
> > restructure outside
> > of the assembly, I am losing graphics in the scene for the components I
> > restructured.
> > As of this point, I do not know a better workaround than recreating the
> > scene. Externalize/localize
> > does not help. I'm still looking for a better workaround. The bug is
> > definitely something
> > that should be fixed in SP2.
> >
> > --
> > Chuck.Savatsky@Autodesk.com
> >
> > Chuck Savatsky
> > MDT developer
> > Autodesk
> >
>

[Anonymous]

Chuck,

I'm confused.... I am not seeing the same behavior. All of my subs and
parts are external. Are your parts and sub2, sub3 local to sub1?

Jeff
------------------------------------------
"Chuck Savatsky" wrote in message
news:133E881EBBA666DA1C69206D1A4B6ADF@in.WebX.maYIadrTaRb...
Kent,

What I mean by outside the top level assembly is as follows:

Assembly looks as follows where all subs are external:

A
Sub1
Sub2
Sub3
P1
P2

Create a scene in A.
Save, close A.

Open Sub1 drawing.
Restructure Sub3 to be directly underneath Sub1. (Sub 2 is now empty of
parts).
Save, close Sub1.

Open up A.

Assembly looks as follows:

A
Sub1
Sub2 (empty)
Sub3
P1
P2

Activate scene.
Graphics for P1 and P2 are not visible, even though in the browser, P1 and
P2 are visible.

If the restructure happens while A is open, this problem does not occur.
However, it should be
ok for the user to do this while Sub1 is open. The graphics should
reappear.

I believe what product support is referring to is that ALL REFERENCES to P1
and P2 in the top level
assembly will be lost when this occurs. That is if there are refdims in a
view of the scene that are
referring to P1 or P2, they will be orphaned. This is also true of 3D
constraints and tweaks. This is as designed,
however loss of graphics in the scene is not.

In general, it is not recommended to do things like restructure outside of
the top level assembly,
but for various reasons, I'm sure it must be done at times.
No competitor that I know of supports the maintaining of such references
when a restructure occurs outside
of the assembly where the references reside. Last time I checked,
SolidWorks did not even support
maintaining dimension references when restructure occurred inside the
assembly.
Maintaining such references is a difficult problem, to say the least.


--
Chuck.Savatsky@Autodesk.com

Chuck Savatsky
MDT developer
Autodesk

Chuck.Savatsky@Autodesk.com
"Kent Keller" wrote in message
news:090DF7DFFD7CD8D03112D8F1E2A4A428@in.WebX.maYIadrTaRb...
> Thanks for the feedback Chuck.
>
> Would undoing the steps in the lower assembly, and then redoing them in
the upper
> assembly work. Or maybe I am not understand what "outside of the
assembly" means. I
> will have to try it if I get a chance.
>
> --
> Kent
>
>
> "Chuck Savatsky" wrote in message
> news:8FF55B2E8687EDDD426917B4B4CDA7CE@in.WebX.maYIadrTaRb...
> > I verified that we do indeed have a bug relating to this. If I do a
> > restructure outside
> > of the assembly, I am losing graphics in the scene for the components I
> > restructured.
> > As of this point, I do not know a better workaround than recreating the
> > scene. Externalize/localize
> > does not help. I'm still looking for a better workaround. The bug is
> > definitely something
> > that should be fixed in SP2.
> >
> > --
> > Chuck.Savatsky@Autodesk.com
> >
> > Chuck Savatsky
> > MDT developer
> > Autodesk
> >
>

[Anonymous]

Opps! Never mind. I was able to get it to happen.

Well, I know not to do THAT anymore.

Jeff

"Jeff Howard" wrote in message
news:C5F133A2DBE3C45E3EA08A930572D272@in.WebX.maYIadrTaRb...
Chuck,

I'm confused.... I am not seeing the same behavior. All of my subs and
parts are external. Are your parts and sub2, sub3 local to sub1?

[Anonymous]

A few observations, for what they're worth:

You can seemingly drag parts around to your heart's content within the
directory structure, from anywhere in the directory structure, without
causing the problem. Side note, though: if you open the top assy and try to
save before updating the scene(s ?) and possibly the dwg views mdt is gone
without so much as a wave. This is at least true for moving a bunch (10)
parts.

Altering the directory structure from anywhere other than the top assy gets
you the booby prize. Every time, without fail. I was able to recover it in
all cases (5 times) by a seemingly random pattern of unloading / reloading
the subassemblies (catalog), but the process is extremely prone to crashing
(again, update the scene before trying to save) and if the scene and views
can be regenerated in a reasonable amount of time that may be the way to go.

The assy model I used was

AssyTop
part5
part5a
sub4
part4
part4a
sub3
part3
part3a
sub2
part2
part2a
sub1
part1
part1a

at least at the start. All parts and assemblies were external.

Good luck with it,
Jeff

[Anonymous]

This is what I did:
Starting file structure
OTL-00237-001
PCT-00237-001
Hrd-00023-001
PCA-00237-001
PCB-00231-001
PNL-00058-001
HRD-00270-001
Opened PCA-00237-001 (by itself) deleted PNL-00058-001.
Updated scenes and 2d drawings
Saved and closed

Opened PCT-00237-001 (by itself) Added PNL-00058-001
Constrained PNL-00058-001
Updated scenes and 2d drawings
Saved and Closed

Final file structure
Otl-00237-001
pct-00237-002
hrd-00023-001
pnl-00058-001
pca-00237-001
hrd-00270-001

Opened OTL-00237-001 (by itself) Tried to update scenes and 2d drawings
PNL-00058-001 is visible in model space but not in original scenes or 2d
drawings
Create a new scene and pnl-00058-001 is visible.


If I read the previous post correctly, I should have opened OTL-00237-001
and dragged PNL-00058-001 from the PCA-00237-001 assembly into the
PCT-00237-001 assembly. What happens if I have another assembly say
OTL-00237-002 that also calls out PCT-00237-001, am I going to have to
recreate all the scenes and drawing views in that file because I did not do
the transfer in that assembly? I can not believe no one has had this
problem before.

I am not as upset about the loss of dimensions for the PNL-00058 in the OTL
drawing as I am that I loss the info on the scene. If I only lost the
dimensions I would only have to recreate about 10 dimensions. With having
to recreate the scene and all the views I have to recreate about 30
dimensions. Half of which are non referenced dimensions (dimordinate used)
that were needed to dimension to the mid line of some connectors and IC's.

Actually now that I think of it, is there any way you can get a reference
dimension to snap to the mid point of a feature? This would make a lot of
things easier for us. I have not tried to do this with any other package
before but it would definitely be a nice feature for dimensioning the center
of non circular openings. Instead of having to use dimordinate and then
change the dimension if you are not using a 1:1 scale and then using
amannote to attaching the dimension to the view in case you decided to
change the view location.

Glenn Freeman


"Jeff Howard" wrote in message
news:6C61DDD41415EC3A0AE70F880886AF3A@in.WebX.maYIadrTaRb...
> A few observations, for what they're worth:
>
> You can seemingly drag parts around to your heart's content within the
> directory structure, from anywhere in the directory structure, without
> causing the problem. Side note, though: if you open the top assy and try
to
> save before updating the scene(s ?) and possibly the dwg views mdt is gone
> without so much as a wave. This is at least true for moving a bunch (10)
> parts.
>
> Altering the directory structure from anywhere other than the top assy
gets
> you the booby prize. Every time, without fail. I was able to recover it
in
> all cases (5 times) by a seemingly random pattern of unloading / reloading
> the subassemblies (catalog), but the process is extremely prone to
crashing
> (again, update the scene before trying to save) and if the scene and views
> can be regenerated in a reasonable amount of time that may be the way to
go.
>
> The assy model I used was
>
> AssyTop
> part5
> part5a
> sub4
> part4
> part4a
> sub3
> part3
> part3a
> sub2
> part2
> part2a
> sub1
> part1
> part1a
>
> at least at the start. All parts and assemblies were external.
>
> Good luck with it,
> Jeff
>
>

[Anonymous]

Give it a try...you will be pleasantly surprised.

--
Kent


"Glenn Freeman" wrote in message >
> Actually now that I think of it, is there any way you can get a reference
> dimension to snap to the mid point of a feature? This would make a lot of
> things easier for us. I have not tried to do this with any other package
> before but it would definitely be a nice feature for dimensioning the center
> of non circular openings. Instead of having to use dimordinate and then
> change the dimension if you are not using a 1:1 scale and then using
> amannote to attaching the dimension to the view in case you decided to
> change the view location.
>

[Anonymous]

If I try to place a reference dimension in my 2d views using the mid of snap
feature when the dimension is placed it moves to one of the corners. I
would like it to stay attached to the mid point of "line" in the drawing. I
can do this using non reference dimensions but not as easily as desired.

Glenn Freeman


"Kent Keller" wrote in message
news:01270F6EBB0BCA514EB2712C55AD6A3E@in.WebX.maYIadrTaRb...
> Give it a try...you will be pleasantly surprised.
>
> --
> Kent
>
>
> "Glenn Freeman" wrote in message >
> > Actually now that I think of it, is there any way you can get a
reference
> > dimension to snap to the mid point of a feature? This would make a lot
of
> > things easier for us. I have not tried to do this with any other
package
> > before but it would definitely be a nice feature for dimensioning the
center
> > of non circular openings. Instead of having to use dimordinate and then
> > change the dimension if you are not using a 1:1 scale and then using
> > amannote to attaching the dimension to the view in case you decided to
> > change the view location.
> >
>
>
>

[Anonymous]

Glenn,

Loss of graphics in the scene due to altering the assembly hierarchy from
anywhere other than
the top level assembly is a bug. We will make all attempts to resolve this
for SP2.
This would deal with the situation where you have two different top level
assemblies referencing the
same subassembly where you wanted to alter the assembly structure in.

As you stated, the dimensions will be lost in the second top level assembly,
but at least altering the structure
from one of the top level assemblies would preserve that top level
assembly's dimensions.

--
Chuck.Savatsky@Autodesk.com

Chuck Savatsky
MDT developer
Autodesk

Chuck.Savatsky@Autodesk.com
"Glenn Freeman" wrote in message
news:85CEB39737D8B32E1E11752CD957E5A1@in.WebX.maYIadrTaRb...
> This is what I did:
> Starting file structure
> OTL-00237-001
> PCT-00237-001
> Hrd-00023-001
> PCA-00237-001
> PCB-00231-001
> PNL-00058-001
> HRD-00270-001
> Opened PCA-00237-001 (by itself) deleted PNL-00058-001.
> Updated scenes and 2d drawings
> Saved and closed
>
> Opened PCT-00237-001 (by itself) Added PNL-00058-001
> Constrained PNL-00058-001
> Updated scenes and 2d drawings
> Saved and Closed
>
> Final file structure
> Otl-00237-001
> pct-00237-002
> hrd-00023-001
> pnl-00058-001
> pca-00237-001
> hrd-00270-001
>
> Opened OTL-00237-001 (by itself) Tried to update scenes and 2d drawings
> PNL-00058-001 is visible in model space but not in original scenes or 2d
> drawings
> Create a new scene and pnl-00058-001 is visible.
>
>
> If I read the previous post correctly, I should have opened OTL-00237-001
> and dragged PNL-00058-001 from the PCA-00237-001 assembly into the
> PCT-00237-001 assembly. What happens if I have another assembly say
> OTL-00237-002 that also calls out PCT-00237-001, am I going to have to
> recreate all the scenes and drawing views in that file because I did not
do
> the transfer in that assembly? I can not believe no one has had this
> problem before.
>
> I am not as upset about the loss of dimensions for the PNL-00058 in the
OTL
> drawing as I am that I loss the info on the scene. If I only lost the
> dimensions I would only have to recreate about 10 dimensions. With having
> to recreate the scene and all the views I have to recreate about 30
> dimensions. Half of which are non referenced dimensions (dimordinate
used)
> that were needed to dimension to the mid line of some connectors and IC's.
>
> Actually now that I think of it, is there any way you can get a reference
> dimension to snap to the mid point of a feature? This would make a lot of
> things easier for us. I have not tried to do this with any other package
> before but it would definitely be a nice feature for dimensioning the
center
> of non circular openings. Instead of having to use dimordinate and then
> change the dimension if you are not using a 1:1 scale and then using
> amannote to attaching the dimension to the view in case you decided to
> change the view location.
>
> Glenn Freeman
>
>
> "Jeff Howard" wrote in message
> news:6C61DDD41415EC3A0AE70F880886AF3A@in.WebX.maYIadrTaRb...
> > A few observations, for what they're worth:
> >
> > You can seemingly drag parts around to your heart's content within the
> > directory structure, from anywhere in the directory structure, without
> > causing the problem. Side note, though: if you open the top assy and
try
> to
> > save before updating the scene(s ?) and possibly the dwg views mdt is
gone
> > without so much as a wave. This is at least true for moving a bunch
(10)
> > parts.
> >
> > Altering the directory structure from anywhere other than the top assy
> gets
> > you the booby prize. Every time, without fail. I was able to recover
it
> in
> > all cases (5 times) by a seemingly random pattern of unloading /
reloading
> > the subassemblies (catalog), but the process is extremely prone to
> crashing
> > (again, update the scene before trying to save) and if the scene and
views
> > can be regenerated in a reasonable amount of time that may be the way to
> go.
> >
> > The assy model I used was
> >
> > AssyTop
> > part5
> > part5a
> > sub4
> > part4
> > part4a
> > sub3
> > part3
> > part3a
> > sub2
> > part2
> > part2a
> > sub1
> > part1
> > part1a
> >
> > at least at the start. All parts and assemblies were external.
> >
> > Good luck with it,
> > Jeff
> >
> >
>
>

[Anonymous]

You are doing ordinate dims right? They are a little different. Regular linear
powerdims work by just snapping to the middle but with ordinate you have to run amautodim.
Choose ordinate and place some ord dims, then after picking the origin, you can snap to
the middle of objects. I think it can also be done with ampowercopy.

--
Kent


"Glenn Freeman" wrote in message
news:C2C2D343F2B16DA5F007D8A9FFA9D823@in.WebX.maYIadrTaRb...
> If I try to place a reference dimension in my 2d views using the mid of snap
> feature when the dimension is placed it moves to one of the corners. I
> would like it to stay attached to the mid point of "line" in the drawing. I
> can do this using non reference dimensions but not as easily as desired.
>
> Glenn Freeman
>
>
> "Kent Keller" wrote in message
> news:01270F6EBB0BCA514EB2712C55AD6A3E@in.WebX.maYIadrTaRb...
> > Give it a try...you will be pleasantly surprised.
> >
> > --
> > Kent
> >
> >
> > "Glenn Freeman" wrote in message >
> > > Actually now that I think of it, is there any way you can get a
> reference
> > > dimension to snap to the mid point of a feature? This would make a lot
> of
> > > things easier for us. I have not tried to do this with any other
> package
> > > before but it would definitely be a nice feature for dimensioning the
> center
> > > of non circular openings. Instead of having to use dimordinate and then
> > > change the dimension if you are not using a 1:1 scale and then using
> > > amannote to attaching the dimension to the view in case you decided to
> > > change the view location.
> > >
> >
> >
> >
>
>