Re: solidworks2006 vs inventor11

Hi Ed,

I am sure we are on the same wave length.

Thank you,

Igor.

--
To reply please use igor@xxxxxxxxxxxx address
"Ed" <ed.thompson@xxxxxxxxxxx> wrote in message news:1157879143.670837.61360@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Igor Mironenko wrote:
What kind of assemblies do you create? How many parts in them and how do
they interact with each other? Or are you confined to one off part (albeit
an intricate one) at a time?

Igor, I believe that you have a point. Almost everything that I do is
involved with medium size and up assemblies. When I was using IV there
were a couple of things that happened fairly routinely. The first was
that I would save an assembly, be sure to rebuild etc. and that there
were no errors etc. But, it periodically happened that when I opened
the project the next time that there would be little red flags, almost
always involving some constraint problem that didn't not show up before
closing IV. I don't think that this has ever happened to me with SW.

But, my all time favorite, "free" feature with IV is when I go into a
part, (usually a fairly simple part) and change one of the dimensions
only to find that the rebuild of the part resulted in an number of
constraint errors.

Now I realize that the assumption is the operator and it may have been
but somehow when I switched over to SW these types of issues just went
away. I have tried to look at what methods that I used could have
caused these types of problems and when something is messed up with SW
I can usually find out what I did to confuse the program. And most of
the time the number of errors are less then 10. However, with IV I
have seen 20 to 30 errors show up on totally unrelated parts from the
one that I made a minor modification to. After 45 minutes of looking
to find the problem I would typically start to suppress, basically at
random various constraints and after a few of these, all of the error
flags would disappear.

A few weeks ago a buddy of mine asked me to help him on a very small
assembly where he was learning how to use IV11. No doubt many of the
issues that he was having were because he was new, but talk about
reliving old experineces...uggg. I especially loved the one where we
saved the project carefully and the next day when he opened it, there
were parts flying all over the place! The word that I use for IV is
that it is much more "fragile" then SW. And, yes the bigger the
assemblies the more problems that I have seen with IV.

Ed


.

Relevant Pages

  • Re: solidworks2006 vs inventor11
    ... Igor Mironenko wrote: ... the project the next time that there would be little red flags, ... always involving some constraint problem that didn't not show up before ... assemblies the more problems that I have seen with IV. ...
    (comp.cad.solidworks)
  • Re: Debugging 3rd party (or Microsoft) assemblies
    ... debugging 3rd party components. ... may occur within that 3rd party component. ... disassemble the 3rd party assembly and then rebuild it with debug ... don't have to rebuild a large tree of assemblies. ...
    (microsoft.public.dotnet.general)
  • Re: Mates breaking?
    ... > CTRL-Q does a forced rebuild. ... This is sometimes limited in assemblies. ... 'forces rebuild of top assembly and all subassemblies ...
    (comp.cad.solidworks)
  • Re: SerializationException: Cannot find the assembly... - Wrapper.zip [1/1]
    ... >> client is called FooClient and connects to FooServer. ... >> the server. ... >> class that existed in two different assemblies instead ... I can rebuild and change ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Auto Increment Version in VB 2005
    ... I agree with his statement 99%, especially when you don't rebuild all ... related projects at the same time. ... You want the referencing assemblies to break if you make ... Is also a bug waiting to happen, if you make a "material" change in one ...
    (microsoft.public.dotnet.languages.vb)
Loading