PDF Publishing in v9.2 and general performance issues
I just upgraded to AD v9.2, but overall performance seems to be, well, shall we say, in the toilet.. There are several times when AD just goes away for minutes at a time and I have no idea what it is doing, if it has locked up, or what is going on. This is way worse than I had with v9.1. What has happened to AD with v9.2? It's performance has gone totally into the basement from what it was with v9.1. If this has something to do with the so called adaptations to run under Windows Vista, then something is very wrong. I am running Windows XP Professional with all current updates.
Now, on to PDF publishing, which I am starting to use as the only means of publishing my robot models in forums and on my website. The published models do not show all components of my models. There are always parts missing as soon as I start rotating the model in published PDFs. Before I start manipulating the model in the PDF, it looks like the model is displayed as it should be. I am just using the Publish to PDF option. I have not yet tried the two new PDF publishing options.
It's been awhile since I got over here. I've been and still am knee deep in redesigning my W.A.L.T.E.R. octagonal shaped two wheeled rover and building a new robot I am calling The Bipod, and its larger sibling, Mega Scout, which are two legged hybrid biped walkers. I could not accomplish my designs as quickly without Alibre Design, but it does get in my way sometimes and there are still things that need to be fixed ASAP. AD still goes in and out of constraint mode when it shouldn't, and it just refuses to make valid connections (nothing happens) a lot of times. I should not have to fight with AD to accomplish what I need to do - it is supposed to make my design tasks easier, not more difficult and frustrating..
Whenever I change even the slightest part of an assembly that has configurations, I have to redo every single configuration. This is just rediculous. Why do I have to reset all my configurations when an assembly is changed? I now have some subassemblies that have eight configurations and that count will grow.
I just upgraded to AD v9.2, but overall performance seems to be, well, shall we say, in the toilet.. There are several times when AD just goes away for minutes at a time and I have no idea what it is doing, if it has locked up, or what is going on. This is way worse than I had with v9.1. What has happened to AD with v9.2? It's performance has gone totally into the basement from what it was with v9.1. If this has something to do with the so called adaptations to run under Windows Vista, then something is very wrong. I am running Windows XP Professional with all current updates.
Now, on to PDF publishing, which I am starting to use as the only means of publishing my robot models in forums and on my website. The published models do not show all components of my models. There are always parts missing as soon as I start rotating the model in published PDFs. Before I start manipulating the model in the PDF, it looks like the model is displayed as it should be. I am just using the Publish to PDF option. I have not yet tried the two new PDF publishing options.
It's been awhile since I got over here. I've been and still am knee deep in redesigning my W.A.L.T.E.R. octagonal shaped two wheeled rover and building a new robot I am calling The Bipod, and its larger sibling, Mega Scout, which are two legged hybrid biped walkers. I could not accomplish my designs as quickly without Alibre Design, but it does get in my way sometimes and there are still things that need to be fixed ASAP. AD still goes in and out of constraint mode when it shouldn't, and it just refuses to make valid connections (nothing happens) a lot of times. I should not have to fight with AD to accomplish what I need to do - it is supposed to make my design tasks easier, not more difficult and frustrating..
Whenever I change even the slightest part of an assembly that has configurations, I have to redo every single configuration. This is just rediculous. Why do I have to reset all my configurations when an assembly is changed? I now have some subassemblies that have eight configurations and that count will grow.