Downloaded 4.3 from Github after 4.3 was released, and after I saw that it says “Release” on the git hub page
“This branch contains source code for
the 4.3 release. You’ll need to
download dependency files per the
instructions below in order to build
and run the engine.”
#I downloaded the source code as the zip file, with the cloud symbol on it
Maybe the above was not updated from the beta version of 4.3 to the full release?
I downloaded the dependencies
I compiled the engine
I updated my plugins
I sent them to clients
2/3 clients are saying its not working for them with the downloaded installer version of 4.3
1 client is saying it is working!
The one client who got their plugin working reported
“It’s the released version, but I compiled the plugin in my vs project.”
So that’s why there’s works!
#This means that the Downloader Version is not Up to Date With Github Version
cause I can’t sort out what else it could be!
#Solus
Hourences is reporting that the installer version of 4.3 is not working with my Github 4.3 version as well, and I explain just above the steps I used to download 4.3 Github full release.
The assumption is that you are using a GitHub build you are going to change the engine, and if you do that your modules will not be binary compatible with the official 4.3 release.
I would recommend compiling your plugin against the same engine that your clients are using, or giving the source code to them so that they may do it themselves.
If you are determined to subvert the version checks, and can guarantee that your engine is compatible with the release version and does not change any public facing API, you can change the MODULE_API_VERSION define in your GitHub build (in ModuleVersion.h) to 2215663 (the changelist number of the release).
Be very careful though; the definition of “any public facing API” is a very subtle one - you cannot add/remove/reorder any virtual functions, add/remove/change any exported function definitions, or add/remove/change any exposed class or struct layouts in the engine. It is much easier to compile with the same engine that they are using.
“I would recommend compiling your plugin against the same engine that your clients are using, or giving the source code to them so that they may do it themselves.”
Thanks Ben!
This is what I ended up doing after realizing it was an option. I’ve never used an installer version of the engine before with clients! It was never an issue before 4.3 !
