You arenāt going to be able to use Flow, Hair or Flex with the launcher version. Blast can be used as a plugin, but I think (someone correct me if Iām wrong) even that needs some source code modifications. These things require modified versions of the engine. means either rolling your own and incorporating Nvidiaās changes, directly using their specific branches, or using the versions from the likes of above, where someone else has taken the time to merge the various bits of GameWorks together.
How to do has been covered in topic, but it really is down to programming knowledge in general. Diffāing files and merging in those changes, linking to external libraries and including headers and suchā¦ If youāve never even whipped up a C++ āhello worldā and set up a stable development environment, is quite the task to take on when just starting out. Not saying donāt do it- just saying be prepared to pull your hair out.
's fork/branch has the most up-to-date versions of anything Iāve come across, and compiles without (at least, last I tried!). If youāve ever compile the engine from source, itās pretty much the same process. More thorough instructions are actually over at the Github repos. So again, your options are to either use one of these lovely pre-made versions and not use what you donāt want, or roll your own and not incorporate the things you donāt need. Flex isnāt available for 4.19 yet (as of writing), but as pointed out, he has a 4.18.3 version with that included.
Documentation is your friend. If you were searching for how to compile Unreal Engine, surely you would have seen near or the top of your search results: .unrealengine/en-us/ā¦ngUnrealEngine
Also, beastly thread (as of writing, 308 pages) is full of knowledge related to various aspects of GameWorks! It might take some time, but itās totally worth it to dedicate some time pouring over it with a magnifying glass. Itās how Iāve solved many of my own issues, matter-of-factly. With that said, youāll see several questions from me in thread as well, haha. As far as making custom builds of the engine that ditches some of the stuff you might not want, Iāve found it to be more of a headache than itās worth. For plugins, I just disable what I donāt use. For other features of the engine, I just donāt use them. Performance has never suffered, and I have no problem packaging and shipping projects that weigh in at 50mb all said and done.
Iām using a modified version of one of 's builds, with the addition of other changes to the engine source, and dozens of external plugins. Iām not having any issues, but that comes with time and getting to know what works and what doesnāt. You just have to experiment, piece by piece, until you land on something that is stable. Then slowly build from there. Itās no fun sitting on the other side of the fence, seeing the big kids get to play with the big toys, but if you a project you are working on is having too many issues with custom builds of the engine, you might have to look the other way, heh. Tinker with madness on the side as an experiment, and stick to stability for serious projects- itās the safe route!
i originally wanted a launcher like plug because of all the updates that are being pushed and ease of use but hey, itās not like i cant do without, it would have been helpful though. Hey you mentioned Blast could be used as a plugin right? I mean i can just compile that in the launcher build as if i were to rebuild the plugin right. because that plugin im really interested in as its way better than Apex standard plug. As for hair and the others not a Priority in my opinion. Oh And yes i have a little know how with c++. Not my first time. Anyway thank you very much Mate. Now i am really interested in the Blast plugin.