Hi , thanks for your answer!
I’ve some more tests and these are the results
-
I’ve tried, with a different computer, the same installation process described in my previous post but the same behaviour still occurs: if packaged for Shipping 32 or 64 that error appears when launching the exe file in the root folder and, to solve i have to use the workaround. Packaging for development instead doesn’t have any kind of problem.
-
I’ve also tried with a clean windows 10 installation on my main computer but the problem persists
-
Finally, using the same steps used to install the 4.11 plugin version, i made some tests with the 4.12 plugin version and, no problem occurred. should mean that i follow the instruction correctly and that the problem may be in the 4.11 plugin version itself, what do you think?
More details about my setup:
The 4.11 plugin version i’ve downloaded is one: VictoryPlugin11
Can you confirm that it is the most up to date plugin version for 4.11.2 Engine?
I’ve Visual Studio 2015 Community installed
**The workaround seems to have no limitations at but i would prefer to have a proper .exe file in my root folder if possible!
Anyway thanks for your support and keep up the good work! **
**
here two screenshots, one for the plugin installation folder and one with my package settings**