• Hello Guest!

    We have recently updated our Site Policies regarding the use of Non Commercial content within Paid Content posts. Please read the new policy here.

    An offical announcement about this new policy can be read on our Discord.

    ~The VaMHub Moderation Team
  • Hello Guest!

    We posted an announcment regarding upcoming changes to Paid Content submissions.

    Please see this thread for more information.

HAL9001
Reaction score
330
Reactions
330

Profile posts Latest activity Postings Media Albums Resources About

  • Hello there! I just opened a scene in which I edited some CUA assets with your plugin, but I found the changes weren't saved😅
    HAL9001
    HAL9001
    Hm, if you look at the .JSON of the scene and search for the plugin data, does it have a list of the elements that were supposed to be removed?
    like this:

    Code:
    ...
    {
      "id" : "CustomUnityAsset",
      "on" : "true",
      "type" : "CustomUnityAsset",
      "position" : {
    ...
      "storables" : [
      {
        "id" : "asset",
        "assetName" : "Assets/staff.unity",
        "assetUrl" : "SELF:/Custom/Assets/TCCArchive/Props/staff.assetbundle"
      },
      {
    ...
      },
      {
        "id" : "plugin#0_HAL9001.CUA_Editor",
        "enabled" : "false",
        "G_thenameofsomeoftheelementsyouremovedhere1" : "false",
        "G_thenameofsomeoftheelementsyouremovedhere2" : "false",
        "G_thenameofsomeoftheelementsyouremovedhere3" : "false"
      }
    ]
    If yes, it has saved and has a retrieval problem. If not, something went wrong when saving indeed.
    Is the CUA large and takes a long time loading? Or is it small and is rather fast?
    HAL9001
    HAL9001
    Also, we should have this discussion in the plugin discussion thread, not on my profile ;-)
    HAL9001
    HAL9001
    Ok, I was able to replicate this..., well, it's not strictly an error, but a sequence of steps one should not (need to) do:
    - Create CUA and select asset
    - Add Plugin
    - Plugin should automatically populate the elements.
    - When it does, the toggles remember the state that each CUA element initially had (on/off) as default value.
    - When saving the scene after editing, it will only save values that have changed from the default (saves space in the file)
    - So, when you edit, and then press "Rescan CUA", it will rediscover the structure and assume all the changed elements as the new default...
    - ...which then means, all those settings, as they are the new default, will not be saved next time.

    To avoid this, never press "Rescan CUA" unless you just chose another asset package and/or something went really wrong. To be sure, select "none" as a CUA, "Rescan the CUA" (which will end up empty, basically flushing all wrong default values), then select the proper asset again and things should be fine.

    Hope this makes sense? I'll add this to the information page... Thanks for stumbling over this... bug? feature?
  • Loading…
  • Loading…
  • Loading…
  • Loading…
  • Loading…
  • Loading…
Back
Top Bottom