Loading...
> >

How to Update My Custom Actions Path After Relocating my Content Library?

JamesJames Posts: 1,003
edited December 2023 in Daz Studio Discussion

I migrated my contents to another drive. Things get broken.
Is there a faster way to change the path of my custom actions.
Maybe there's a file containing the path which I could change?

Post edited by James on

Comments

  • crosswindcrosswind Posts: 6,831

    Open File Browser, go to the path: %AppData%\DAZ 3D\Studio4\, there's a file : customactions.dsx. Open it with Notepad++ and check it.
    Some actions use "absolute path", so you need to modify the path as per the one on your new drive.

  • JamesJames Posts: 1,003
    edited December 2023

    Woohoooo, it works. Thank you.

    Post edited by James on
  • crosswindcrosswind Posts: 6,831

    James said:

    Woohoooo, it works. Thank you.

    Don't mention it buddy ! Good day !

  • barbultbarbult Posts: 24,223
    That's a great tip.
  • Richard HaseltineRichard Haseltine Posts: 100,488

    Actions that were in a content directory when created should use relative paths, those that have absolute paths can be edited through the Window>Workspace>Customise dialogue by right-click on the action itself (under Custom, on the left).

  • stefan.humsstefan.hums Posts: 132

    Richard Haseltine said:

    Actions that were in a content directory when created should use relative paths

    No, they are always created with absolute paths - for the path to the file as well as the path to the icon.

  • crosswindcrosswind Posts: 6,831
    edited December 2023

    Normally user-defined actions are with relative paths for the user-facing files. If there's a variable in dsx defined as "sRelativePath", that's a relative one. But icons are always with "absolute paths".

    Well, most of actions with "absolute paths" were added by the script from the vendors, like RiversoftArt, and mostly by batch, e.g. Camera Doctor, 20+ actions. After switching to different Lib location, they won't be funtional in action list, menu items and toolbar.

    Usually replacing "old paths" with "new paths" in dsx file will be much faster... a couple of seconds...

    Post edited by crosswind on
  • stefan.humsstefan.hums Posts: 132

    Ok, I have to correct myself.

    Custom actions created from .DUF assets have the "sRelativePath" variable (with a relative path assigned) but also contain another variable "sPreferredPath" that then again contains the absolute path with drive letter. After moving them to a different (mapped) content directory, although the icons are broken but at least the actions are still working.

    But all custom actions created from script assets (.dsa / .dse) are created with absolute paths.

    <CustomAction Accel="" Icon="K:/DAZ3D/Studio/DAZeigene/Scripts/CamLock2022V2.png" ShowTextWithIcon="false" Description="Camera Lock" Name="9fff59aa-de16-4ee5-bb42-ff32b2fb36a6" File="K:/DAZ3D/Studio/DAZeigene/Scripts/CamLock2022V2.dsa" Text="Camera Lock"/>

    Moving them breaks the action completely.

  • crosswindcrosswind Posts: 6,831

    stefan.hums said:

    Ok, I have to correct myself.

    Custom actions created from .DUF assets have the "sRelativePath" variable (with a relative path assigned) but also contain another variable "sPreferredPath" that then again contains the absolute path with drive letter. After moving them to a different (mapped) content directory, although the icons are broken but at least the actions are still working.

    But all custom actions created from script assets (.dsa / .dse) are created with absolute paths.

    <CustomAction Accel="" Icon="K:/DAZ3D/Studio/DAZeigene/Scripts/CamLock2022V2.png" ShowTextWithIcon="false" Description="Camera Lock" Name="9fff59aa-de16-4ee5-bb42-ff32b2fb36a6" File="K:/DAZ3D/Studio/DAZeigene/Scripts/CamLock2022V2.dsa" Text="Camera Lock"/>

    Moving them breaks the action completely.

    Yeah ~ that's right.

Sign In or Register to comment.