SW 2005 SP0.0 how safe?
SW 2005 SP0.0 how safe?
(OP)
Hi all
As an experienced CAD user and Design and Development manager, I never use the first releases of software to work.
The thing is that I've been testing SW2005 and it has some improvements with significant impact in our work.
So I am trying to compare the risks and the benefits of an imidiate transition from SW2004 to SW2005. I personally didn't detect any problem until now.
Does anyone experienced problems (speed, bugs, compatibility,..) with SW2005? How safe Sw2005 SP0 is?
Regards
As an experienced CAD user and Design and Development manager, I never use the first releases of software to work.
The thing is that I've been testing SW2005 and it has some improvements with significant impact in our work.
So I am trying to compare the risks and the benefits of an imidiate transition from SW2004 to SW2005. I personally didn't detect any problem until now.
Does anyone experienced problems (speed, bugs, compatibility,..) with SW2005? How safe Sw2005 SP0 is?
Regards






RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
The other problem that I have not been able to nail down yet is with Textures and configurations. I have been finding that if I specify only certain configs have this texture, then it should only be on those configs. But out of 34 Configs, half of them have that texture applied. What makes this more strange is that not I only picked 4 configs and it changed it for say 10-12 of them. But the others are fine. If the Specify for Config didn't work then it should have made it for the configs. But that wasn't the case at all. It made for the configs I told it too, just some configs went ahead and excepted it too.
Still working on that one.
Otherwise it's stable. I have a single crash in 3-4 weeks of using it and that was the old click ahead while SW is working unhandled error.
If I think or find anymore I'll post them.
You should really test SW05 throughly! Download the Website version and run some of your models through it. Our Opinions are not going to tell you much then what we have already seen and found. You should test your products in it to make sure there are not any major bugs or flaws in your processes. You might find something that we would not see.
Regards,
Scott Baugh, CSWP
http://www.3dvisiontech.com
http://www.scottjbaugh.com
If you are in the SW Forum Check out the FAQ section
To make the Best of Eng-Tips Forums FAQ731-376
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
Regards,
Scott Baugh, CSWP
http://www.3dvisiontech.com
http://www.scottjbaugh.com
If you are in the SW Forum Check out the FAQ section
To make the Best of Eng-Tips Forums FAQ731-376
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
Regards
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
- When working with multiple (more than 1) break lines in broken drawing views the distance between the break lines is not maintained. If the distance is set to a small value most of the breaks are overlapping.
- Explode lines in shaded drawing views can not be printed. They even do not show up when the drawing is opened view only.
- When printing solid hatches the hatches are always printed in black rather than the specified color.
Unfortunately I haven't found any workarounds for those very basic issues.
RE: SW 2005 SP0.0 how safe?
Some text is shifted to the right, making it having 2 lines instead of 1. The result is a mess.
Editing the text as no efect. I need to clear the text and creat it again.
Regards
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
Regards
RE: SW 2005 SP0.0 how safe?
RE: SW 2005 SP0.0 how safe?
I observed also crashes when opening a sat file as assembly.
After several attemts to open this sat-file I recognized that 2005 is only crashing with a specific part template.
After recreating that template from an old 2004 template I did not had crashes anymore.
RE: SW 2005 SP0.0 how safe?
I have not had any crashing issues, but lots of stuff with new functionality not working and SP's from 2004 not yet integrated.
The revision control through PDMWorks is a bit of a disaster. I worked through a bunch of work-arounds with our VAR, but in general it does not work very well at all. Whoever created the code for the revision control has probably never made a drawing before and it really shows. If anyone out there is using the rev control let me know and I can bring you up to date with specifics. Too many issues to write down right now and I'm waiting from feedback from the VAR and SW on a fix time.
Generally 2005 is stable, but SW corporate will be feilding questions on bugs for the next 2-3 months.
wtait
RE: SW 2005 SP0.0 how safe?
i am using the rev control in 2004 have not loaded 2005.
thanks
cliff
RE: SW 2005 SP0.0 how safe?
When selecting a fitting with tolerance, in a dimension,the fitting is OK but the tolerance shows +0 and -0 instead of the fitting deviations.
Regards
RE: SW 2005 SP0.0 how safe?
The rev control in PDMWorks does not control the one on the drawing as stated. Even though we have a numeric rev scheme configured in PDMW2005 the SW revision table defaults to the alphabetic scheme. If you were at rev 02 in PDMWorks and added a rev to the table it would come out as rev "C" not 03 as you would expect. The selection inside PDMW to not show the working copy in the table does not work as well....it still shows up and you have to delete it.
You have to be very procedural as well. The revision table on the drawing does not update until after you check the document into PDMW so you can't add revision symbols until you've checked in the document for the rev you want to see. You can either configure PDMWorks to enable you to overwrite the last revision and then force the rev to stay the same after you add the rev symbols or add a revision directly to the table.
If you add a revision directly to the table you will need to change it from a letter to a number (if using 00,01,02 etc.) and then check in the document. When you add a revision to the table PDMW does not know you have changed the rev so you will have to make sure it is set properly on check-in. The "Description" property in the revision table is actually the "Note" column on check in. If you enter something directly into the table it will be overwritten upon checkin by what is placed in the Note for that file.
It basically does not work as you would think.
wtait