Drive Constraint performance vs assembly update method

[Brett.G]

Hello,

   I know this has been asked before (reference), but I have been unable to find an answer.  I'm trying to drive two Parameters by assigning Parameter.value to something and then update the assembly with Activedocument.update.   The assemblies I'm using tend to have many mates and the update method tends to take some time.  Comparing this to the Drive Constraint tool, the performance is much worse. 

Does anyone know what makes the Drive Constraint tool much faster than the Update method?  Alternately, is there any way to make the Update method faster or only update the Parameters that I'm modifying?  Any hints would be appreciated.  Thanks!

[bradeneuropeArthur]

The activedocument.update could be the problem.
Could you please upload your code as text file.

[Brett.G]

Thanks for the suggestion, the code is broken up into different subs with more details and error checking, but here is the gist:

1. Disable user interaction
2. Assign a value to the vertical parameter
3. Assign a value to the horizontal parameter
4. update the assembly
5. when finished looping, reenable user interaction

the code to do that is as follows:

gInvApp.UserInterfaceManager.UserInteractionDisabled = True

VertName.Value = (gdblPosArray(gintCurrentIndex, 2) + CDbl(txtVertOffset.Text)) / 10
HorizName.Value = (gdblPosArray(gintCurrentIndex, 3) + CDbl(txtHorizOffset.Text)) / 10
'update model and ignore errors
gAssyDoc.Update2(True)

Previously, instead of gAssyDoc.Update2(True)  I was accessing the active document each time via gInvApp.ActiveDocument.Update2(True) which I thought may be slower based on your comment, so I assigned gAssyDoc =  gInvApp.ActiveDocument in the "New" sub so I wouldn't have to find it each time.  In an assembly with 180 constraints this did not seem to make much difference.  Driving one of my constraints is still faster than my addin that drives both or even when I only control one constraint with my addin. 

[bradeneuropeArthur]

try this:

gInvApp.UserInterfaceManager.UserInteractionDisabled = True

gInvApp.screenupdating = false

VertName.Value = (gdblPosArray(gintCurrentIndex, 2) + CDbl(txtVertOffset.Text)) / 10
HorizName.Value = (gdblPosArray(gintCurrentIndex, 3) + CDbl(txtHorizOffset.Text)) / 10
'update model and ignore errors
gAssyDoc.Update2(True)

InvApp.screenupdating = true

[Brett.G]

Hmm, I tried your suggestion and did not notice a difference.  I did have to place the screen update line before the AssyDoc.Update line to get the "animation"  but did not notice any significant change in the performance on the assembly I'm trying. 

I appreciate the suggestions, I've been thinking about this for awhile now and cannot seem to figure it out.  At this point any idea is appreciated.

[liminma8458]

"ThisApplication.ActiveDocument.Rebuild" may work.