SW2009 Mismatched Origins Of Inserted Part

[CorBlimeyLimey]

Anyone noticed that the origins aren't aligned correctly when inserting a part into an assy, or when creating an assy from a part? I'm using the 'Click the Tick' method to accepth the default placement.

Didn't this also happen with a previous release?

 

[CorBlimeyLimey]

Using SW2009-SP1 and didn't notice a problem on SP0. Will have to go back and check other assys.

 

[mncad]

I have this problem sometimes with SW2007 SP2.1. I don't remember it always happening though. Seems like it started about 8 months to a year ago, and now happens randomly.

mncad

 

[ctopher]

I have seen this issue since 2006.

I brought it up to my VAR and SW and it didn't seem to be a problem with them at the time.
They suggested that I don't determine design around the origin!

Chris
SolidWorks/PDMWorks 08 3.1
AutoCAD 08
ctopher's home (updated Aug 5, 2008)
ctopher's blog
SolidWorks Legion

 

[CorBlimeyLimey]

"They suggested that I don't determine design around the origin!"

Say WHAT!!!

 

[Timelord]

CBL is right! Huh?? WTF??

Design intent literally forces me to design around the origin. Glad I have never had the problem.

Timelord

 

[ctopher]

WTF is correct.
One reason why I'm happy not to be with that VAR anymore.

Chris
SolidWorks/PDMWorks 08 3.1
AutoCAD 08
ctopher's home (updated Aug 5, 2008)
ctopher's blog
SolidWorks Legion

 

[osweeks]

I have only worked with SW 2006 and 2007 but at 2 different companies and 5 different computers and have always had this problem. It was one of my biggest pains when I first changed jobs and went from PRO/E to SW. In PRO/E you can place parts by default for those that have never used it. I just assumed that was the way SW was and assemble everything using the base planes. Would be nice to be able to skip all those mate steps.

Scott

http://www.earthtrucks.com

Solidworks 2007 sp2.2
Nvidia Quadro FX 1500
Dual PentiumD 3.00ghz 2 Gig Ram

 

[CorBlimeyLimey]

There was a previous version which had this problem, but it was fixed. I've only just noticed that it is happening again.

I discovered last night, that if an empty assy document and part(s) for insertion are tiled when inserting a part, the origins align correctly.

I will be submitting an SPR later today.

 

[CorBlimeyLimey]

Problem resolved by resetting the registry.
faq559-507

 

[uGlay]

This has always been an issue. You plop your part in an assembly and it ends up 20 feet behind all the planes.


SW2008 Office Pro SP4.0
Intel Core 2 Duo CPU
2.2GHz, 2.00GB RAM
QuadroFX 3700
SpacePilot

 

[Theophilus]

Hmmm. I'll not reset all my toolbars, etc. just to solve this little (new) issue in old v2007. Any chance the export settings tool would avoid bringing the problem back after clearing the registry?



Jeff Mowry

http://www.industrialdesignhaus.com

A people who value security over freedom will soon find they have neither.

 

[CorBlimeyLimey]

uGlay,

It's only an issue on some PCs. The vast majority of users have never experienced the problem.

It also depends how the part is created with respect to its own origin, and how the part is "plopped" into an assy.

Are you talking about the first part placed into an assy?
If so, how are you placing it?

 

[uGlay]

There's a couple of ways of inserting it, i use a different method depending on the kind of situation i am in. I usually do "Float" right after I insert it and proceed to mate it my own way.

Yes, it doesnt happen all the time but it has definitely happened to me. I am aware that if i create a solid away from my origin it will insert itself away from the origin in the assembly but this happens also with parts that are origin-centric.

This is one of those things you just learn to accept and live with, kind of like "Failed to Save".

SW2008 Office Pro SP4.0
Intel Core 2 Duo CPU
2.2GHz, 2.00GB RAM
QuadroFX 3700
SpacePilot

 

[CorBlimeyLimey]

If, after selecting the first component to insert, you just 'Click the Tick', the parts origin should be placed at the assy origin. If this is not working for you, try re-setting the registry key.

 

[e2Pro]

Most of the methods are acceptable at handling this problem. I personally use the float method as uGlay does. But the real reason this happens is when you insert your first part component in an assembly and pick any area of the sheet view when inserting the model and or assembly, that is the selected origin that it uses, but if drag your mouse over to the area where you have the tree docked, then it will snap directly to the origin with no problems.

 

[CorBlimeyLimey]

Finally found the cause (or one of them at least) for the mismatched origin. I can reproduce the problem by setting the Status Bar to NOT show. Re-enabling the Status Bar fixes the problem without playing with the registry.

Can anyone else repeat this?