topic Re: Autodesk PowerMill 2025.0.2 Update is now available for download in PowerMill Forum

Autodesk PowerMill 2025.0.2 Update is now available for download

claire.louise.davies — Wed, 11 Sep 2024 06:49:25 GMT

Customers using any product from the PowerMill 2025 range with an active subscription or maintenance plan can now download and install the PowerMill 2025.0.2 Update through Autodesk Access :

Alternatively, you can download the PowerMill 2025.0.2 Update from the Product Updates area of your Autodesk Account. The associated PowerMill_2025.0.2.exe file is 87.4 MB in size on disk.

Details of the fixes and enhancements included in the PowerMill 2025.0.2 Update are listed here.

To confirm that you've successfully installed the PowerMill 2025.0.2 Update, select the ? > About menu option in your PowerMill 2025 software and check that you're working in Version: 2025.0.2.2025028.

You can download the latest version of Autodesk Access from here.

Kind regards,

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

dsmits — Wed, 11 Sep 2024 17:04:07 GMT

We don't have Autodesk Access installed on all of our computers because we want to ensure everyone remains on the same software version. This helps prevent users from accidentally clicking update, etc.

Previously, when updates were released as .msp files, we were able to automate the process using a script to deploy the .msp files. However, the latest updates are distributed as .exe files.

I’ve tried extracting the .msp from the .exe using:

PowerMill_2025.0.2.exe /e .\PowerMill_2025.0.2.msp

But that didn’t work. I also tried running:

PowerMill_2025.0.2.exe /? PowerMill_2025.0.2.exe /quiet

Neither of these showed available parameters or allowed silent installation.

Is there another way to automate the installation of this .exe update across multiple machines without having to manually install on each one? Preferably, I’d like to avoid downloading any third-party software.

Any advice would be appreciated!

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

dsmits — Thu, 12 Sep 2024 18:48:56 GMT

nvm i figured it out

回复： Autodesk PowerMill 2025.0.2 Update is now available for download

Always-Love-CNC — Fri, 13 Sep 2024 09:20:55 GMT

In the POWERMILL2025.02 version of macro has become very slow, what is the reason for this?

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

Benjamin.Br — Fri, 13 Sep 2024 09:28:20 GMT

Hello @Always-Love-CNC, we are not aware of an issue with reduce performance of macros in this update. Are you able to supply an example macro that shows the problem please.

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

Always-Love-CNC — Fri, 13 Sep 2024 09:35:32 GMT

You can use a macro to rename the toolpath name to test, the macro execution speed on Powermill 2024 and Powermill 2025, which is very obvious! Can use 30 tool paths

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

Benjamin.Br — Fri, 13 Sep 2024 09:37:34 GMT

Thank you. We will investigate.

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

ken.poyner — Fri, 13 Sep 2024 10:34:04 GMT

@Always-Love-CNC I've tried investigating this and I don't find what you've described.
I've written a very simple macro that creates 30 toolpaths, starts timing, renames all 30 of them then print what the timer reads.
I've ran it 5 times in 2024.0.3 and 5 times in 2025.0.2 and can't see a meaningful difference

2024039 (2024.0.3)	2025028 (2025.0.2)
0.501000	0.498000
0.497000	0.437000
0.432000	0.503000
0.469000	0.469000
0.479000	0.475000

This means either I need to try with something more complicated (these were all in just an empty project) or that there is something environmental occurring on your machine, are there any plugins active in 2025 and not 2024 perhaps? Can you run the same macro in a fresh environment and see if you get the same findings as me?

(The file upload won't let me upload the macro, so I've just pasted it's contents)

IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR IMPORT TEMPLATE ENTITY TOOLPATH TMPLTSELECTORGUI "Finishing/Raster-Finishing.002.ptf" FORM CANCEL STRATEGYSELECTOR echo on TOOLBAR COMMANDBAR RAISE clock init clock reset clock on quit RENAME Toolpath "1" "meow1" RENAME Toolpath "2" "meow2" RENAME Toolpath "3" "meow3" RENAME Toolpath "4" "meow4" RENAME Toolpath "5" "meow5" RENAME Toolpath "6" "meow6" RENAME Toolpath "7" "meow7" RENAME Toolpath "8" "meow8" RENAME Toolpath "9" "meow9" RENAME Toolpath "10" "meow10" RENAME Toolpath "11" "meow11" RENAME Toolpath "12" "meow12" RENAME Toolpath "13" "meow13" RENAME Toolpath "14" "meow14" RENAME Toolpath "15" "meow15" RENAME Toolpath "16" "meow16" RENAME Toolpath "17" "meow17" RENAME Toolpath "18" "meow18" RENAME Toolpath "19" "meow19" RENAME Toolpath "20" "meow20" RENAME Toolpath "21" "meow21" RENAME Toolpath "22" "meow22" RENAME Toolpath "23" "meow23" RENAME Toolpath "24" "meow24" RENAME Toolpath "25" "meow25" RENAME Toolpath "26" "meow26" RENAME Toolpath "27" "meow27" RENAME Toolpath "28" "meow28" RENAME Toolpath "29" "meow29" RENAME Toolpath "30" "meow30" clock off quit clock print quit

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

Always-Love-CNC — Fri, 13 Sep 2024 10:43:14 GMT

Simple naming doesn't reveal any issues! Please try the macro I uploaded,It contains various parameters that need to be read

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

ken.poyner — Fri, 13 Sep 2024 10:59:52 GMT

Running that macro in both versions still isn't conclusive

I added a "clock init clock reset clock on" to line 4 and "clock print" to the last line

2024039 (2024.0.3) 2025028 (2025.0.2)
0.711000 0.246000
0.731000 0.301000
0.971000 0.569000
0.679000 0.467000
0.666000 0.386000

But that was in a very simple project. Can you repeat that in a project with a simple toolpath, then in the one you're seeing the issue in?

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

1713314072 — Fri, 13 Sep 2024 11:21:09 GMT

Indeed, in February 2025, the speed of some macros is not as fast as that in 2024. I tested the macro on the upper floor and recorded a video!!!!

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

ken.poyner — Fri, 13 Sep 2024 11:37:02 GMT

@1713314072 are you able to share the macro being used here? It's clear there's something more than just renaming as I can't reproduce this. Without a reliable way of reproducing it myself we've no hope of fixing it.

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

ken.poyner — Fri, 13 Sep 2024 11:45:12 GMT

@Always-Love-CNC what locale/language do you run PowerMill in?

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

Always-Love-CNC — Fri, 13 Sep 2024 11:46:10 GMT

chinese lang

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

ken.poyner — Fri, 13 Sep 2024 11:50:55 GMT

That might explain why I can't see it (and gives me something to investigate)

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

1713314072 — Fri, 13 Sep 2024 11:50:59 GMT

DIALOGS MESSAGE OFF
DIALOGS ERROR OFF

GRAPHICS LOCK

STRING ACTIVATEtp = toolpath.name

DEACTIVATE TOOLPATH

EDIT TOOLPATH LEADS LEADOUT2 RAMPOPT ZAGANGLE "1.79"
EDIT PAR NOQUERY SELECTED
Connections.LeadOut.Second.Ramp.ZagAngle.Value

STRING LIST TpNames = {}
INT b =1
FOREACH c IN folder('TOOLPATH') {
if entity('toolpath',$c.name).Connections.LeadOut.Second.Ramp.ZagAngle.Value == 1.79 {
INT Size = add_last(TpNames, c.name)
}
}

if size(TpNames)==0 {

FOREACH c IN folder('TOOLPATH') {

STRING q= c.Tool.Name

STRING p= c.Tool.TipRadius

STRING jc= c.Tool.HolderName

REAL sc= c.Tool.Overhang

REAL rc= c.Tool.Length

STRING j= c.Thickness

STRING z= c.AxialThickness

STRING cc= c.name

if $c.UseAxialThickness ==1 {

STRING d = b+"-"+q+"("+j+"~"+z+")"+"_"+"L"+sc

rename TOOLPATH $c.Name $d

}

if $c.UseAxialThickness ==0 {

STRING d = b+"-"+q+"("+j+"~"+j+")"+"_"+"L"+sc

rename TOOLPATH $c.Name $d

}

$b=b+1
}

} else {

FOREACH c IN folder('TOOLPATH') {
if entity('toolpath',$c.name).Connections.LeadOut.Second.Ramp.ZagAngle.Value == 1.79 {
EDIT PAR NOQUERY "entity('toolpath',$c.name).Connections.LeadOut.Second.Ramp.ZagAngle.Value" 1

STRING q= c.Tool.Name

STRING p= c.Tool.TipRadius

STRING jc= c.Tool.HolderName

REAL sc= c.Tool.Overhang

REAL rc= c.Tool.Length

STRING j= c.Thickness

STRING z= c.AxialThickness

STRING cc= c.name

if $c.UseAxialThickness ==1 {

STRING d = b+"-"+q+"("+j+"~"+z+")"+"_"+"L"+sc
rename TOOLPATH $c.Name $d

}

if $c.UseAxialThickness ==0 {

STRING d = b+"-"+q+"("+j+"~"+j+")"+"_"+"L"+sc

rename TOOLPATH $c.Name $d

}

}
$b=b+1
}

}

ACTIVATE TOOLPATH $ACTIVATEtp

EDIT TOOLPATH LEADS LEADOUT2 RAMPOPT ZAGANGLE "1"

GRAPHICS UNLOCK
DIALOGS MESSAGE ON
DIALOGS ERROR ON

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

Always-Love-CNC — Fri, 13 Sep 2024 11:54:32 GMT

Do you mean that macros in different language environments have different execution speeds?
But I think this is only a situation that appears on Powermill 2025

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

ken.poyner — Fri, 13 Sep 2024 12:04:25 GMT

I'm going to investigate if we could have introduced such a difference in the 2025 release.

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

936619531 — Fri, 13 Sep 2024 12:42:06 GMT

can you Angle cleaning fine process Max blank

Re: Autodesk PowerMill 2025.0.2 Update is now available for download

936619531 — Fri, 13 Sep 2024 12:51:26 GMT

powermill2025