SP3.3

I am seeing this too

"CS" wrote in news:1140178502.960941.82700 @g47g2000cwa.googlegroups.com:

Can a design table still control these settings?

If this is true, this is bad news. I use this feature all the time, it's in most of my Templates.

SolidWorks please test your software prior to release.

Best Regards, Devon T. Sowell

Is the option just gone?

I was just told this will be fixed in SP4.0. Sorry folks, at this point I suggest avoiding 3.3, unless you require the PDF fixes, and don't care about part numbers in the BOM..

WT

It's really difficult to understand how they release software with so many obvious bugs. I mean come on. 3.3 is out for one day and already serious problems were found, some within MINUTES.

This is really a weak spot in an otherwise good company.

Best Regards, Devon T. Sowell

It can still be set through the API. I just tested. I had created a custom property manager that emulated that section of the Configuration Property Manager Page and mine still works.

Corey

Software is the ONLY product they sell! Most remember SW market BS for adding more beta testers and reducing the frequency of SP releases. What happened, where are the results they promised?

Who are the individuals responsible for releasing pollutants into the water supply?

Kman

Those that feel they don't have to release SP's without going thru the EV testing again. The last 2 point SPs did not go thru EV testing and both of these have been crap releases. And it probably wont stop there. They fix one thing and F&CK up 20 others.

I still see the Bill of Materials Options on new configurations but it's gone for existing configs.

We only updated to sp3.3 from sp2 because the pdf problems were fixed. This is absolute crap. I am sick and tired of wasting my time testing their software and finding stuff that is broken. We pay good money each year for so called maintenance. Who is going to pay me for the time now wasted because we have to now roll back to a previous service pack and then when sp4 is available, install that. SolidWorks this is just not good enough and maybe some acknowledgement that there are problems is required.

rant over....

This is not the only thing missing in SP3.3. There is now no option TO EXCLUDE FROM BOM in an assembly when you RMB on a part or subassembly to change the configurations of that part/subassembly.

You have got to be kidding me!!!

I'm curious! I have never used any other 3D modeling package another than SW (since 1997). Would someone out there that regularly uses another package, comment on their success with their service packs? Does the competition regularly take 2 steps forward and 1 step back like SW does?

Don't get me wrong. I still like SW in general. But it is getting to the point that I may need to start "eye-balling" other packages.

Well that option is part of the same area of the config dialogue that's missing. So it's the same problem not really two.

If I'm not mistaken, "j" is talking about right clicking on a part or sub-assembly within an assembly, going to properties, and the "exclude from BOM" option is missing. If so, than this IS different than the missing options in the configuration property dialog, that has already been mentioned.

Seth is correct. This is in the assembly. The funny thing about this is if I pick more than one part at a time this option is available. Single parts are not allowed to be excluded.

Now that's crazy!

But if that's the case, I wonder if a workaround would be to insert another version of the part or sub-assembly, selecting both of them to exclude from BOM, and then deleting the extra one you just inserted?!?! I am not using

I have to say that from a programming standpoint it is very easy to cause a Property Manager Page to be missing sections. If one item causes an exception the PMP will load up until that point and skip the rest but give no errors. Don't flame me for this but there is alot of behind the scenes changes going on in solidworks in 2006 (I believe the modeling kernel underwent alot of changes to speed up large assemblies among other things) they are in the beta process of implementing 64 bit, the change from BlueBeam to Acrobat among other things. These are huge implementations that touch every part of the rest of the software.

This and the other config problem are reported to be fixed for SP3.4