MSVC only: Error C3203: unspecialized class template ... (works fine on MAC)
- 
 @Lindon wicked. It does look like it's not a problem of the node but the network. If I disable the AllowCompilation in the Network Node properties the third party nodes do at least compile independent of that. So it might indeed throw a false positive on the polyphonic thing as Christoph suggested and therefor not properly build the DspNetworks.h 
- 
 @Morphoice Yeah you're missing the node_properties.json file so the code generator doesn't know whether your C++ node should be polyphonic (as it should as your DECLARE_AIR_WINDOWS macro creates a class with a voice number template) so it makes an educated guess which appears to be wrong. Whenever you paste in a ThirdParty code, always create the C++ template through the HISE menubar first, then replace the file content of the autogenerated file with your code. This ensures that it creates the proper flags in the node_properties.jsonfile.When you do so you should see something like this in ThirdParty/node_properties.json."Disintegrate": [ "IsPolyphonic", "AllowPolyphonic" ]Oh and yeah, use Git, then remove all the build files from the source control system, Dropbox is the complete wrong tool for the job. 
- 
 @Christoph-Hart I will check that out. Thanks 
- 
 @Christoph-Hart is there a list somewhere which folders/files exatcly to ignore in git? 
- 
 **/Binaries/ PooledResources/ AdditionalSourceCode/ Samples/ AudioFiles/ *.hip *.hxi *.hxp *.hr* *.ch* .DS_Store user_info.xml
- 
 @d-healey said in MSVC only: Error C3203: unspecialized class template ... (works fine on MAC): **/Binaries/ 
 PooledResources/
 AdditionalSourceCode/
 Samples/
 AudioFiles/
 *.hip
 *.hxi
 *.hxp
 .hr
 .ch
 .DS_Store
 user_info.xmlbueno! let's see how that goes. 
 atm HISE is complaining the source isnt the same commit hash as the build, although I just built it from the source.... narf
- 
 @Morphoice said in MSVC only: Error C3203: unspecialized class template ... (works fine on MAC): although I just built it from the source.... narf How many copies of HISE and the source code do you have? 
- 
 @d-healey one. it'a a freshly installed pc, HISE has just been pulled from github and built 
- 
 @Morphoice Did you build the develop branch? 
- 
 @d-healey yes sir 
- 
 @Morphoice In that case it could be just that Christoph hasn't updated the git hash so don't worry about it. 
- 
 @d-healey well it does produce hundreds of compiler errors though ... 
- 
 @d-healey if I forget to update the git it will not show this message, it just doesnât show the correct git in the about window. That message means that there is a mismatch between the source code git hash and the compiled version. 
- 
 @Christoph-Hart but how can I resolve this? I just compiled it again from the sourcecode and it still shows the message... 
- 
 @Morphoice where does your HisePath setting point to? 
- 
 @Christoph-Hart C:\HISE which is where github put the source... I'm just doing it again from scratch 
- 
 @Morphoice And when you run HISE you're running it from within that same folder? 
- 
 @d-healey yes directly from the build directory.... I did it all over again, now github complains there is a filename too long when I try to clone my project onto the new pc. 
 I have to give up for the day, I need to go to work now. barkeeping. drinking. and vice versa.
- 
 @d-healey so the c++ error could be fixed thanks to christoph, there was actually a json file missing to hold some info about the third party node hence the DspNetworks.h was created wrongly... as suggested by christoph to work with github rather than dropbox i managed to compile the the network on the pc, now attempting to compile the final plugin. fingers crossed, third day's the charm ;) (hopefully) 
- 
 @d-healey deleting shit multiple times and fetching it all over, compiling it all over in the end resolved the hash mismatch error.... though I wish I could exactly pinpoint what went wrong the first time, I guess it just is what it is sometimes, just fidding about 




