Closed stephbellemare closed 1 year ago
Noted, I think I've gone to 0.2 there so I need to check what's gone on.
On Thu, 12 May 2022, 03:59 stephbellemare, @.***> wrote:
Macro LOAD_MESH_TEMP is calling version check on variable setup_version. macro should be v0.1 same as setup_version in save_variables.cfg to ensure macro loads well.
or a separate macro should be created in save_variables.cfg to save the specific version of auto_mesh.cfg
— Reply to this email directly, view it on GitHub https://github.com/strayr/strayr-k-macros/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKIYU2BAG5YUAEL4ZEF44W3VJRXYZANCNFSM5VWZMA6A . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I think this has been fixed
Macro LOAD_MESH_TEMP is calling version check on variable setup_version. macro should be v0.1 same as setup_version in save_variables.cfg to ensure macro loads well.
or a separate macro should be created in save_variables.cfg to save the specific version of automesh.cfg ///// EDIT ADD BELOW
actually after checking it's the whole variable section missing as LOAD_MESH_TEMP seems to be calling setup_mesh_lifespan which seems to be missing.