I was having isue's with SP1 on severa machines. Any medium to large assemblies and to be saved and opened several times and hour to avoid crashing.
Now we have that issue resolved with SP1.1 ... now I can't hatch ..it uses up all of the resources and ram till it crashes/lockes up the pc's.
This is on more than one ... and they are all I7, 8 gig systems ..with great cards in them ... so it's not the pc's
Thanks for the response. I was able to make your 1st option work. In 2013, I went to Application Options and set my Content Center path to my 2012 location and all assemblies open up with their respective hardware - AWESOME - THANK YOU!
I also understand what you are saying about having the Content Center on a server in a central location. I am the only Mech Designer at my company and have been pulling Content Center parts from my harddrive.
What I don't understand is why I need to copy my 2012 Content Center Files to this central location - I mean, when a new release of Inventor comes out, do I need to keep copying the previous years Content Center to this location?
Is there a way to make my OLD Content Center assemblies work with the latest release Content Center???
I'm a bit ignorant on this aspect of Inventor, apologies in advance if I'm not understanding you. . .
What we're working with is two different locations. One is the libraries location, where all the "recipes" are kept. The other is the generated components that actually get made from the recipes and appear in your assemblies.
The first is, in your case, the Desktop Content Libraries, which are installed on your hard drive when Inventor is installed. It's fine right where it is, as long as you backup any custom libraries you create, and migrate them from one version to the next.
The second is where you ran into problems, because the default location for the generated components is on your hard drive under your User profile, by version. So when you get a new version, you have to start over, or copy the stuff from the previous version's repository. That's why I recommend establishing another location for those components, either with the other project stuff, or in a more central location, depending on the kind of work you do.
Ohhhhh. . .
That was a really good explanation. Makes a lot more sense - I'll try to set this up as you are recommending.