Need help on exporting custom C++ plugin

[tobitdsm]

So I made a plugin with custom C++ code following this tutorial. In the beginning he advises to compile the skeleton plugin to confirm there are no issues to begin with, so I did. Everything fine up to there.
Then I went on to creating my actual plugin. It uses some FFT's and complex math which is why I chose to do it in C++ as opposed to FAUST or other scripting tools available. I still wanted to use HISE over bare ProJucer as it gives very easy access to simple but effective interface design.
Now my plugin is done, and it works perfectly fine inside HISE. However, if I compile it and load it into a DAW (Reaper), it seems as if it is still the old export from before I started coding. I have one knob, which does absolutely nothing. My interface is there, just the C++ code doesn't seem to have compiled with my plugin for some reason, although it is listed in the section of things it will compile...
I thought the problem was that I was running HISE Debug from VS (as advised in the tutorial, to get access to breakpoints etc.), but saving and opening in a normal HISE instance worked fine, except again the export...
I would attach a snippet, but I have no clue what the minimum setup is to recreate this problem.

Is there anyone with any tips towards where the issue could be? Many thanks in advance!

[HISEnberg]

@tobitdsm There's quite a lot going on here which raises suspicion regarding your setup and workflow.

First the workflow in that video is a touch out dated, but I believe for all intents and purposes it should work. Just create the C++ node, write your code then Compile the DSP networks as DLL. From there you can load the C++ node in an FX Slot or inside of Scriptnode and attach the parameters to your UI.

Secondly, do any HISE based plugins work for you inside of Reaper or any other DAW? Say for example if you attach your one knob to a gain node, does it function properly? It could have something to do with your setup.

Third, easiest way to have someone help you debug this would be to share the C++ script or a very minimal version of it. This way someone here could rebuild the plugin on their end and test it.

Fourth point you can disregard if you feel like it, but FFT is a pretty complex topic. An external C++ is definitely the way to go but I would recommend starting with something simpler if you are just beginning.

Last point is to make sure to get rid of the old plugin binary versions in your VST3/AU folder. Use Export>Clean build directory before compiling the plugin in order to clear your build folder. Also maybe try changing the plugin code in the project settings.