Script control of parametric text fails after last F360 update on 2025-01-28

[osvacneo]

I do have a script, which alters the user parameters "MaleDiameterInner" and "FemaleDiameterInner" for values 25, 32, 36, 40 and 50mm in any possible permutation of the two user parameters and writes an stl-file for each permutation. After the F360-update yesterday, the embossed text will not update properly any more (see screen shot below).

To reproduce open the f360 design and run the script, please note, it takes 1-3minutes per file to process. File will be written to
"destFolder = "D:\tmp\F360"

You may change that destination in line 160.

Test data can be found here:
https://forums.autodesk.com/t5/fusion-support/parametric-text-fails-after-last-update-on-2025-01-28/td-p/13288361

I will also try to attach it here. If desired, I can provide a simplified version, which runs faster.

Software

• OS: Win10

• Fusion 360 version:
  

• ParametricText version: 2.4.0

[osvacneo]

`#Author-
#Description-

import adsk.core, adsk.fusion, adsk.cam, os, traceback

###########################################################################################
def get_immediate_children(component):
# Get the child occurrences (components) directly under the specified component
child_occurrences = component.occurrences

# Extract the actual component objects from the occurrences
child_components = [occ.component for occ in child_occurrences if occ.isVisible]

return child_components

###########################################################################################
def _generateIteratedDataSet( inputDataSets, oneDataLine, iteratedData ):
index = len(oneDataLine)

if( index < len(inputDataSets) ):
    inputDataSet = inputDataSets[index][1]

    for data in inputDataSet:
        oneDataLine.append( data )
        _generateIteratedDataSet( inputDataSets, oneDataLine, iteratedData )
        oneDataLine.pop(index)
else:
    tmp = oneDataLine.copy()
    iteratedData.append(tmp)

###########################################################################################
def generateIteratedDataSet( inputDataSets ):
names = []

for inputDataSet in inputDataSets:
    names.append( inputDataSet[0] )

interatedData=[]
_generateIteratedDataSet( inputDataSets, [], interatedData)

return( (names, interatedData) )

###########################################################################################
def verifyUserParameters(app, design, names):
ui = app.userInterface
userParameters = design.userParameters

for name in names:
    userParameter = userParameters.itemByName(name)

    if userParameter:
        dummy = 1
    else:
        ui.messageBox('User-Parameter "{}" nicht gefunden.'.format(parameterName), 'Fehler')
        return

###########################################################################################
def setUserParameters(app, design, names, data):
ui = app.userInterface
userParameters = design.userParameters

length = len(names)

for index in range(0, length, 1):
    name = names[index]
    val = data[index]
    userParameter = userParameters.itemByName(name)
    userParameter.expression = str(val)

# update parametric text plugin
app.fireCustomEvent('thomasa88_ParametricText_Ext_Update')            
adsk.doEvents()
adsk.doEvents()
design.computeAll()
dummy = 1

###########################################################################################
def generateFileName( componentName, names, data ):
length = len(names)
text = ""

for index in range(0, length, 1):
    name = names[index]
    val = data[index]

    if( len(text) != 0 ):
        text = text + "-"

    text = text + name + "=" + str(val)

text = componentName + "-" + text

dummy = 1
return( text )

###########################################################################################
def exportStl( exportMgr, component, destFolder, fnBody ):
fn = os.path.join( destFolder, fnBody + '.stl')

stlOptions = exportMgr.createSTLExportOptions(component, fn)
stlOptions.sendToPrintUtility = False # Setze auf True, wenn du die Exportdatei direkt drucken möchtest

# Körper als STL exportieren
exportMgr.execute(stlOptions)

###########################################################################################
def run(context):
ui = None
try:
print("Hello")
dummy=1

    # Zugriff auf Fusion 360 UI
    app = adsk.core.Application.get()
    ui = app.userInterface

    # Dokument und Design erhalten
    product = app.activeProduct
    design = adsk.fusion.Design.cast(product)

    if not design:
        ui.messageBox('Kein aktives Fusion 360 Design.', 'Fehler')
        return
    
    # Get the root component
    root_component = design.rootComponent
    
    # Get the immediate child components under the root component
    immediate_children = get_immediate_children(root_component)

    ###################################################################################
    # change to your personal data here
    inputData1 = (
        ("height", (10, 20)),
        ("width", (30, 40)),
        ("length", (50,60))
    )
    inputData2 = (
        ("MaleDiameterInner", (25, 32, 36, 40, 50)),
        ("FemaleDiameterInner", (25, 32, 36, 40, 50))
    )
    inputData3 = (
        ("Hoehe", (22,)),
        ("BeschriftungsfeldWinkel", (45, 90)),
        ("BreiteEinheiten", (0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0)),
        ("TiefeEinheiten", (0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0))
    )

    inputData = inputData2

    destFolder = "D:\\tmp\\F360"
    # end of personal data
    ###################################################################################


    iteratedDataSet = generateIteratedDataSet( inputData )
    names = iteratedDataSet[0]
    iteratedData = iteratedDataSet[1]

    verifyUserParameters( app, design, names )

    for data in iteratedData:
        setUserParameters( app, design, names, data )

        exportMgr = design.exportManager 

        for component in immediate_children: 
            fnBody = generateFileName( component.name, names, data )
            exportStl( exportMgr, component, destFolder, fnBody )
            dummy = 0

    dummy=1
    return

    # dead old code below
    # User-Parameter ändern
    parameterName = 'HoseDiameterInner'  # Name des zu ändernden Parameters
    parameterObj = ui.inputBox("Bitte geben Sie den Namen des Parameters ein:", "Parameter Name", "HoseDiameterInner")
    parameterName = parameterObj[0]

    # Überprüfen, ob der Benutzer einen Namen eingegeben hat
    if not parameterName:
        ui.messageBox("Es wurde kein Parametername eingegeben.")
        return

    for parameterValue in [25, 32, 36]:
        set_parameter(app, design, parameterName, parameterValue)
        
        # Export
        exportMgr = design.exportManager        
        for component in immediate_children: 
            export_stl(exportMgr, component, parameterValue)

    ui.messageBox('Export erfolgreich abgeschlossen.')

except:
    if ui:
        ui.messageBox('Fehler aufgetreten:\n{}'.format(traceback.format_exc()))`

[osvacneo]

osVACneo Master v317.zip

[thomasa88]

Hi,

Do you get any error messages? What happens if you open the Text Commands pane, switch it to Py and write 1? Do you see any errors printed?
Do parametric texts that are not controlled by your script still update correctly?

[osvacneo]

Thanks for your response. I had a look at your code. I understand only small parts of it. But it looks like a solid piece of work :-)

To some of your questions:

No error messages at all. I do not see yellow marked items in the time line either.

[osvacneo]

For the rest I am still working on understanding, what you mean.

"Do parametric texts that are not controlled by your script still update correctly?":
I only change the user parameters and leave it to parametric text to make the changes. I am not trying to to alter any embossed text directly in my text.

[osvacneo]

In the meantime, I changed "MaleDiameterInner" and "FemaleDiameterInner" to a few different values manually directly in F360. That works.

[osvacneo]

I am not sure, whether this images will show. FemaleDiameterInner is set to 40 by my script, the embossment shows the old value of 36

[osvacneo]

I made a very simple version of my test file. I try to include it here.

simpleTestFile v0.zip

[thomasa88]

In the meantime, I changed "MaleDiameterInner" and "FemaleDiameterInner" to a few different values manually directly in F360. That works.

It was this that I wanted you to try. So it sounds like ParametricText runs fine if it is not triggered by a script.

So I guess it is this step that for some reason does not trigger ParametricText to update:

# update parametric text plugin
app.fireCustomEvent('thomasa88_ParametricText_Ext_Update')            
adsk.doEvents()
adsk.doEvents()

Maybe the new Fusion version requires even more doEvents() 😅 or that the event call is delayed, by firing the custom event after a delay from a separate thread.

What if you run your script and let it update the values once. Then you run
app.fireCustomEvent('thomasa88_ParametricText_Ext_Update') from the Python console in Fusion. Does it have any effect?

Also, you might want to try with an app_.log("External trigger") in the following function in ParametricText.py, to see if it runs at all:

def ext_call_update_handler(args: adsk.core.CustomEventArgs):
    update_texts()

It is supposed to unconditionally update all texts.

[osvacneo]

"It was this that I wanted you to try. So it sounds like ParametricText runs fine if it is not triggered by a script.":
I apologize, I did not understand, what you asked for.

As you found out: yes, it works fine, if you change it manually.

There is other news:
In the meantime I got another update from Autodesk and now, it runs better. Which means it works for 24 of the 25 permutations, the script runs through. Only for the very first iteration the text update fails.

I will look into your suggestion to see, whether they will help. Thanks a lot for your help.

[thomasa88]

Sorry, I did not mean to be rude/aggressive 😅.

It definitely sounds like a Fusion timing problem. Fusion must be given enough time / "ticks" to process the events and perform the changes requested by your script, before the values can be read out.

EventsManager in thomasa88lib has the ability to do the workaround by creating a sleep in another thread and then firing a user event after the timeout. I don't have enough time to explain how it works, but the implementation is here: https://github.com/thomasa88/fusion360-thomasa88lib/blob/master/events.py#L112

Possibly, you could have another Fusion event as a trigger to start the update of ParametricText.

[mr-potato-head]

I have te exact same issue... !
I tried :

# update parametric text plugin
app.fireCustomEvent('thomasa88_ParametricText_Ext_Update')            
adsk.doEvents()
adsk.doEvents()

without success. :(

[mr-potato-head]

I also tried to add app_.log("External trigger") in ext_call_update_handler and nothing is displayed in the logs.

[mr-potato-head]

Looks like these lines work well :

# Choose diameter and refresh
design.userParameters.itemByName("generic_diameter").expression = str(float(diameter)) + " mm"
design.userParameters.itemByName("label_generic").comment = str(float(diameter-3.0)) + "/" + str(float(diameter+3.0))

app.activeViewport.refresh()

app.fireCustomEvent('thomasa88_ParametricText_Ext_Update')     
adsk.doEvents()
adsk.doEvents()
adsk.doEvents()

app.activeViewport.refresh()

Not sure to understand why but it is ok... More a hack than a real solution though.