Im at a loss. vst3 is not working in FL Studio (Access Violation)
- 
 Some things to check. Does it work in any other DAW? Reaper for example. 
 Does it work standalone?Sometimes different DAWs give you better debug output. 
- 
 .exe will not open at all, nothing happens. 
 It does not show up in Reaper. 
- 
 @Lindon wasn‘t there something that caused your plugin to crash when using the copy protection flags? 
- 
 Did you use any scriptnode? If you left any network at Allow Compilation and exported that way, it results in a broken plugin that doesn't load. 
- 
 @aaronventure said in Im at a loss. vst3 is not working in FL Studio (Access Violation): ? If you left any network at Allow Compilation I did mess around with a stereo effect at some point. But removed it again. How can i see if there is anything leftover? 
- 
 Could this be the cause of it? 
 From HISE Activate:
 Warning: default font used for getStringWidth() method (might cause race conditions on Windows)
- 
 I painstakingly spent the whole night, copying my project and removing code and UI elements one by one, and exporting every time i did a change. I added +1 to every version to make sure if was a "new" vst3 export that i could test in my DAW. It only worked when i deleted absolutely everything except a background image. 
 BUT, one time i deleted "Sampler1" and it worked while still having some code and UI elements. I tried again, because it seemed weird, but it only happened once.I'm at a loss. 
 Something is messed up beyond recognition.
- 
 @ThinkTank You can try to remove the line in your code. Make sure to always clean the build folder for a clean build. 
- 
 @Christoph-Hart said in Im at a loss. vst3 is not working in FL Studio (Access Violation): @Lindon wasn‘t there something that caused your plugin to crash when using the copy protection flags? if there was I cant for the life of me recall what it was... sorry. I never use copy protection flags - unless Im misunderstanding this... 
- 
 @ThinkTank -- ok I looked thru the old topics - and found the one Christoph was referring to I think... I also think you may have found it too, but just in case:##try removing your Presets code... dont load a preset on start up, and make sure that FL Studio is using fixed buffer sizes... 
- 
 



