First delete the binary and intermediate folder
Then rebuild the project.
Youbwill have a build error. Check the log from the saved/log folder projects.

Probable cause:
Build.cs are using the old system for building. The log gives you a hint about what biuld.cs files you must edit and what change.

Other possible cause: the documentation is confusing and misleading.
You must copy the spine c folder that is inside of the spine c folder in your plugin folder

@InnerChild, we keep the old build in place so the runtime works with older UE4 versions. There aren't preprocessor defines exposed in the build system, so we can't have separate code for different versions. Until the deprecation is complete, we'll keep it as is. There shouldn't be any problems stemming from this, except for warning messages in the build log.

How would you say is the documentation misleading? It says

Copy the folder spine-runtimes/spine-c/spine-c to your project's Plugins/SpinePlugin/Source/SpinePlugin/Public/ folder.

Happy to formulate it in a different way.

@Osamsa, let us know what the log says!

badlogic yazdı

@[silindi], we keep the old build in place so the runtime works with older UE4 versions. There aren't preprocessor defines exposed in the build system, so we can't have separate code for different versions. Until the deprecation is complete, we'll keep it as is. There shouldn't be any problems stemming from this, except for warning messages in the build log.

How would you say is the documentation misleading? It says

Copy the folder spine-runtimes/spine-c/spine-c to your project's Plugins/SpinePlugin/Source/SpinePlugin/Public/ folder.

Happy to formulate it in a different way.

@Osamsa, let us know what the log says!

http://es.esotericsoftware.com/spine-ue4

1-The download link is broken
2- epic sent a email to plugin developer for updating their pluguins to 4.16 because there will be relevants changes on the engine. I know this because i have made plugins and i got this email and i had to update my plugin

3. If you are using 4.14 you should not push on git a readme saying "updated to 4.16". The build.cs rules have changed and is the minimal change that you need to make with your plugins.
4. The instructions say that must copy the contents of spine-c in "Sources" .
   I guess you mean "Source" .and it is not the folder spine-c but the spine-c inside of it.
5. If you want the plugin and/or the example you must download the whole repository including repos for all runtimes. You should have different repos for every runtime properly ordered. That is more confusing and a waste of time and discourage to the community to help with the source code
6. I could keep going with more situations because we are on it trying to bring the really good advantages of spine to ue4 but for that we need cooperation. And the least we expect is some love for the customer of ue4. The differences of ux on the ue4 plugin vs unity plugin are huge.

Osamsa yazdı

hello! thank you for helping me.
i try again cleanly

i attached 2 file.
log file and my folder inside.

SpineUE4.log

i think text '????' is 'My Documents'
another broken text i don't know.. should i open it with a different extension? i open text file

Osama
You need to install visual Studio2017 with c++ game components.
There is a error about missing windows sdk 8.1 that makes me suspect that.
Please uninstall vs2015. Ue4 4.16 works only with 2017.
Searchnon epic webpage they updated the procedure of ibstalling visual. Studio for the new version of unreal.

For the build.cs warnings you must change the way that target is defined. I am on my phone so i cannot show you how i changed it on my project but please check this example

https://github.com/gameDNAstudio/MobileUtils/tree/master/Source/MobileUtils

@[silindi]

Let me answer each point of yours

1-The download link is broken

Ah, you are correct, the download link in the Spine UE4 guide was pointing to the old branch. Sorry, oversight, fixed!

2- epic sent a email to plugin developer for updating their pluguins to 4.16 because there will be relevants changes on the engine. I know this because i have made plugins and i got this email and i had to update my plugin

Yes, we received that email as well, and we plan on acting on it once Epic has fully deprecated the old build system API.

3. If you are using 4.14 you should not push on git a readme saying "updated to 4.16". The build.cs rules have changed and is the minimal change that you need to make with your plugins.

Yes, the changes are minimal, but will prevent people on UE < 4.16 to use the plugin. There's no way to have a < 4.16 and a >= 4.16 of the build files live side by side. The deprecation warnings currently being displayed in the build log are not harming a build apart from polluting the build output. We will update fully to the new build once Epic fully deprecates it, i.e. the warnings become errors.

4. The instructions say that must copy the contents of spine-c in "Sources" .
I guess you mean "Source" .and it is not the folder spine-c but the spine-c inside of it.

Ah, you refer to the README.md in the repository, not the guide. Fixed!

5. If you want the plugin and/or the example you must download the whole repository including repos for all runtimes. You should have different repos for every runtime properly ordered. That is more confusing and a waste of time and discourage to the community to help with the source code

We can package the plugin like we do package the Unity plugin, pulling in spine-c and zipping it up. That will make it easier for people who just want the plugin.

For people who want to work on the sources and contribute changes, the current layout is the best we can do. Spine UE4 depends on spine-c, which itself is used by other runtimes. Git sub-modules are broken, so a single monolithic repo is the best option for now in our opinion. It's the same for the Unity plugin.

6. I could keep going with more situations because we are on it trying to bring the really good advantages of spine to ue4 but for that we need cooperation. And the least we expect is some love for the customer of ue4. The differences of ux on the ue4 plugin vs unity plugin are huge.

[/quote]

And we do want to improve the UE4 plugin. We know it's not at the same level as the Unity plugin The reason being that it's the youngest runtime we have, while the Unity runtime is the oldest, and therefor most robust runtime. I'm sorry things take time. But we also need your feedback on improving things, be it bug reports or feature requests.