How to Build Unreal Engine From Source
Ғылым және технология
In this video, we go over how to download and build the unreal engine source code. First, we go over the hardware and software prerequisites. Then, we connect our Epic Games account to our Github account. After that, we download the source code via Git, run the prebuild Setup scripts, build the source code in Visual Studio, and run the editor.
How to support the channel:
Get a shirt or sweatshirt with free shipping (Use code "SHIP" at checkout): teespring.com/stores/flopperam
Become a member: / @flopperam
Support us on Patreon: / flopperam
Donate to our PayPal: www.paypal.me/flopperam
Sponsor us on Github: github.com/sponsors/chris-gong
Social media links:
Discord: / discord
Twitter: / flopperam
Instagram: / flopperam
Facebook: / flopperam
****IMPORTANT LINKS****
Unreal's recommendations for hardware specs: docs.unrealengine.com/latest/...
Git: git-scm.com/downloads
Python: www.python.org/downloads/
Compatible Visual Studio versions for Unreal Engine 5: docs.unrealengine.com/latest/...
Compatible Visual Studio versions for Unreal Engine 4: docs.unrealengine.com/4.27/en...
Latest version of Visual Studio: visualstudio.microsoft.com/do...
Older versions of Visual Studio: visualstudio.microsoft.com/vs...
Log in to Epic Games: www.unrealengine.com/
Log in to GitHub: github.com/
GitHub organizations: github.com/settings/organizat...
Epic Games GitHub page: github.com/EpicGames/
Other Visual Studio configuration settings: docs.unrealengine.com/latest/...
docs.unrealengine.com/latest/...
****IMPORTANT COMMANDS****
To zoom out or in: Ctrl + or Ctrl -
git clone github.com/EpicGames/UnrealEn...
cd UnrealEngine
clear
git branch -a
git tag
You can use arrow keys to scroll up and down the branches and tags from 'git branch -a' and 'git tag' respectively
Press q to get out of the 'git branch -a' or 'git tag' command
git checkout [name-of-branch-or-tag]
./Setup.bat
./GenerateProjectFiles.bat
0:00 Hardware requirements
1:13 Software requirements
3:20 Connecting Epic Games & GitHub accounts
4:32 Downloading source code via Git
6:47 Building source code in Visual Studio
8:09 Creating a new project
#unrealengine #unrealengine5 #ue5
Пікірлер: 21
Looks like 2024 is the year of comebacks, welcome back boss!
thankyou you made the information very clear :)
Yay welcome back!
thank you
welcome back!
Im new on this channel but i will be watching u from now on
@Flopperam
3 ай бұрын
We’re glad to have you here!
Is this the comeback we've been waiting for?
@Flopperam
3 ай бұрын
Yes
Please be active on KZread bro.. we need to learn this series
@Flopperam
3 ай бұрын
That is the plan! We will be active going forward :)
it's ridiculous... i'm using AVS plugin which need to replace the bugged Default UE-Landscape.dll with a new one, which need the Source Code to work. otherwise i can't package my game with the new landscape.dll From what i understand, you can't use the binary version and the Source Code version of Unreal. i mainly code in the binary version using blueprint. i dont like C++. but if i want to modify the landscape.dll and using it in my packaged game, i have to use the Source version. and of course XD... the binary version is 19gb, while the Source version is 300gb. Why not 2Tb at this point..... Something is missing somewhere.. this is ridiculous.
Missing your old background music lol
@Flopperam
3 ай бұрын
Out of curiosity, would you prefer if there was background music?
@kameenavery9616
3 ай бұрын
@@Flopperam it was kinda relaxing with the background music. I liked it, but if your new direction does not go that route that is cool too
Floppy Flopper
building engine cost me 2 hours.. 32gb ram, cpu ryzen 5 3.60ghz
btw WOW UE5 needs 32 gigs of ram?!?
@Flopperam
3 ай бұрын
I think so. I tried with 16gb and my PC kept crashing while trying to build it. I didn't have anything else running in the background at the time either.
@IamNeighborlee
3 ай бұрын
32 gb in Mac M1 Max, and its working like a dream.
@sithmaster
6 күн бұрын
As a game developer, I can honestly tell you that some of our current maps are opening fine with 128 GB of ram. Don't underestimate the work you have with higher mesh models during import “before” they get converted to Nanite. Yes, 128 GB is my recommendation. It sounds much at first, but by the end of the day it's just 4x 32 GB sticks on a motherboard. And it's not that pricey either when going AM4 and DDR4 still. It also kills a lot of other bottlenecks quickly. Video production, Sound Design, Photoshop. They all love to use it.