When I continue working on a plugin that has been exported as VST3, edits to the gui are not always picked up consistently. I’m not sure exactly what happens. It seems like the DAW keeps the unedited gui, even if I save the DAW project, close the DAW and reopen the project. If I delete the plugin and use “undo”, it also will not update. If I delete the plugin and add it manually again, it will update. Sorry to say I’m not 100% sure this is the way it works every time, but it seems so.
I assume you’re using Reaper? Are you opening the .csd file that has been saved to the ProgramData/CabbageAudio/PLUGIN_NAME folder? Perhaps you are working on the original file instead?
After export, I work on the file in ProgramData/CabbageAudio/PLUGIN_NAME
It’s strange, because the plugins are loaded in the same way by the host as they always have been, let me take a look. It’s not something I can recreate.
I can recreate the problem! I can’t believe I didn’t spot this before. Looking at a fix now. First I have to find the problem 
Right, it’s the session save data that is overwriting the new UI updates. That makes sense. I guess I can put in a timestamp and cross reference it with the .csd file when loading. Let me see if that works.
[edit] but this will mean losing session saved states if you tweak some of your Csound code.. looking for another solution..
New build available: 3.0.29-beta This addresses the issue you faced. The only session data that gets saved now are values, and anything that has been touched by cabbageSet. Note that you will need to resave the session to see these changes, as the structure of the sesion data has been updated. From now on you can simply reload a saved session, or reload the plugin to refresh its UI. 
Nice. Thank you again. Blazingly fast 
1 Like