the 2.7 version is not ready, so here is a new 2.5 version, that should work better than the previous one, as the new fill_angle_template setting (vector field) mess the previous one.
I'll probably do another 2.5 version in 2024, just with bugfixes and translation updates, to be able to have a stable one.

known issues

• changing infill connection length cause a crash. fixed in next nightly.
• problem with windows 11, you may want to remove the opengl32.dll from the mesa dir if you have problem with your graphic card, as a stop gap (this disable the 3D acceleration).
• still no mac build, will do that after 2.7 merge. For now, you can grab the mac-intel nightly from here, it's the same but without the translations.

New

• only one perimeter on top now also with arachne (thanks to orca, vovodroid).
• now the thumbnails header can omit the type, to adapt to creality firmware #3989
  • new setting: thumbnails_tag_format (bool)
  • old default is to have it deactivated for png (windows power tools only show the thubnails if it's png and no tag)
  • old default is to have it activated for all others (but creality wants jpg without tag)

Bugfixes

• fix modifiers #4016
• fix post process script #4016
• fix cooling slowdown (wasn't working) #4015
• fix monotonic ordering #3770
• fix travel acceleration #3821
• apply max_gcode_per_seconds for travels #3534
• gui: fix slider ticks #3975
• gui: fix missing "revert" buttons for filaments

notes

I haven't tested the linux & macos build.
The mac arm isn't built anymore (until I find the will to reinstall & reconfigure the VM again).
The mac intel version will ask you for permission. You may need to do xattr -cr /Applications/SuperSlicer.app.
For Windows automatic installer/updates: https://community.chocolatey.org/packages/superslicer . Note that it has some days of delay, for the validation process. (I'll try to add superslicer also into winget)
You can have daily builds in the action menu of github.
You can support me with the "sponsor" button

note: sorry, I pushed this release initially on the wrong label, so maybe some repo may have build the 59.4 instead of the 59.5