Autodesk Mechanical Desktop
Brian
Are you sure they have to overlap? As I remember it was just the sequence of
dimensioning one view and then dimensioning the other that is a different scale.
--
Kent Keller
http://kwik-mcad.scriptmania.com/
Check out the Mechanical Desktop FAQ @
http://mymcad.com/
See the MDT/ Inventor wishlists!
www.cadsense.co.nz/wishmain.htm
"Brian Corbin (CAD Sense)" wrote in message
news
B3496F0F586BC3FFD6F3421AB67ACD6@in.WebX.maYIadrTaR
>
>
> Gary,
>
> I have seen and reported (verifed) a serious bug with MDT6 dimensioning. I'm
> not sure if this is the same as the trouble you are having but it is worth
> mentioning anyway.
>
> If you have 2 overlapping MDT6 views which are at different scales, MDT
>
Are you sure they have to overlap? As I remember it was just the sequence of
dimensioning one view and then dimensioning the other that is a different scale.
--
Kent Keller
http://kwik-mcad.scriptmania.com/
Check out the Mechanical Desktop FAQ @
http://mymcad.com/
See the MDT/ Inventor wishlists!
www.cadsense.co.nz/wishmain.htm
"Brian Corbin (CAD Sense)"
news
B3496F0F586BC3FFD6F3421AB67ACD6@in.WebX.maYIadrTaR>
>
> Gary,
>
> I have seen and reported (verifed) a serious bug with MDT6 dimensioning. I'm
> not sure if this is the same as the trouble you are having but it is worth
> mentioning anyway.
>
> If you have 2 overlapping MDT6 views which are at different scales, MDT
>
Brian,
Overlapping view ports makes about as much sense as anything else I could
come up with. Your right, I never had this happen in MDT5 or prior.
This an extremely serious bug whatever the cause. It makes it very difficult
to have confidence in dimensions. I posted previously how difficult it is to
find the problems dims if the scales used are very close to one another.
The text message for SP1 was vague about the actual fixes. Does anyone know
if this was addressed? Perhaps views from Sp1 on won't have this problem.
But Sp1 does not seem to fix existing dimension scale factor inaccuracies.
Gary Cross
gcross@crossdesign.com
"Brian Corbin (CAD Sense)" wrote in message
newsB3496F0F586BC3FFD6F3421AB67ACD6@in.WebX.maYIadrTaR
>
>
> Gary,
>
> I have seen and reported (verifed) a serious bug with MDT6 dimensioning.
I'm
> not sure if this is the same as the trouble you are having but it is worth
> mentioning anyway.
>
> If you have 2 overlapping MDT6 views which are at different scales, MDT
> power dimensioning will sometimes get confused about which view the
> dimension is attached to and set the linear scale for the dimension off
the
> wrong viewport. So in effect your dimension value is wrong. I discovered
> this AFTER the fact that it cost my company a lot of down time and money.
>
> So the moral is if you have overlapping views in MDT6 keep a eye on your
> dimensions as they could be wrong. MDT5 never done this BTW.
> And yes I have plenty of examples of this that I can post if req.
>
> Brian Corbin
> CAD Sense
>
> "Gary Cross" wrote in message
> news:8651D8D10C4DE01FE71E1E528041612C@in.WebX.maYI
> > That should read DIMLFAC not dimscale-big difference
> > And, I can't seem to change it by changing the DIMLFAC & updating the
dim.
> >
> > It's normally automatic but does anyone know how to correct the DIMLFAC
on
> > pardims like this as a work around?
> >
> > Gary Cross
> > gcross@crossdesign.com
> >
> >
> > "Gary Cross" wrote in message
> > news:46834B4F8C3E7FEDCA37C535B5051C23@in.WebX.maYI
> > > Is there any other one else having this problem or is it just me?
> > >
> > > Some pardims have the wrong dim scale factor in a views (
example-scale
> is
> > > 1:2 but dimscale factor lists as is -4 ) & it's causing me headaches.
> > >
> > > I can't verify if it was before or after SP1.
> > >
> > > Gary Cross
> > > gcross@crossdesign.com
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>
Overlapping view ports makes about as much sense as anything else I could
come up with. Your right, I never had this happen in MDT5 or prior.
This an extremely serious bug whatever the cause. It makes it very difficult
to have confidence in dimensions. I posted previously how difficult it is to
find the problems dims if the scales used are very close to one another.
The text message for SP1 was vague about the actual fixes. Does anyone know
if this was addressed? Perhaps views from Sp1 on won't have this problem.
But Sp1 does not seem to fix existing dimension scale factor inaccuracies.
Gary Cross
gcross@crossdesign.com
"Brian Corbin (CAD Sense)"
news
B3496F0F586BC3FFD6F3421AB67ACD6@in.WebX.maYIadrTaR>
>
> Gary,
>
> I have seen and reported (verifed) a serious bug with MDT6 dimensioning.
I'm
> not sure if this is the same as the trouble you are having but it is worth
> mentioning anyway.
>
> If you have 2 overlapping MDT6 views which are at different scales, MDT
> power dimensioning will sometimes get confused about which view the
> dimension is attached to and set the linear scale for the dimension off
the
> wrong viewport. So in effect your dimension value is wrong. I discovered
> this AFTER the fact that it cost my company a lot of down time and money.
>
> So the moral is if you have overlapping views in MDT6 keep a eye on your
> dimensions as they could be wrong. MDT5 never done this BTW.
> And yes I have plenty of examples of this that I can post if req.
>
> Brian Corbin
> CAD Sense
>
> "Gary Cross"
> news:8651D8D10C4DE01FE71E1E528041612C@in.WebX.maYI
> > That should read DIMLFAC not dimscale-big difference
> > And, I can't seem to change it by changing the DIMLFAC & updating the
dim.
> >
> > It's normally automatic but does anyone know how to correct the DIMLFAC
on
> > pardims like this as a work around?
> >
> > Gary Cross
> > gcross@crossdesign.com
> >
> >
> > "Gary Cross"
> > news:46834B4F8C3E7FEDCA37C535B5051C23@in.WebX.maYI
> > > Is there any other one else having this problem or is it just me?
> > >
> > > Some pardims have the wrong dim scale factor in a views (
example-scale
> is
> > > 1:2 but dimscale factor lists as is -4 ) & it's causing me headaches.
> > >
> > > I can't verify if it was before or after SP1.
> > >
> > > Gary Cross
> > > gcross@crossdesign.com
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>
