So because I found a lot of posts from people asking how to build uwp games, here is a short guide:
check this link: https://docs.unrealengine.com/latest...alStudioSetup/
1. Download Visual Studio
2. Open Visual Studio Installer
3. Modify your Visual Studio installation and add all needed components
(You get most components when you simply add the following workloads:
-Universal Windows Platform development
-Desktop development with C++
-Game development with C++
Check individual components and make sure that VC++ toolset, C++ Support, .Net Framework targeting pack & Windows SDK's are selected!)
4. Install Visual Studio
check this link: https://docs.unrealengine.com/latest...gUnrealEngine/
5. Download/clone the uwp unreal engine version you need from github
(links and instructions in first post: https://forums.unrealengine.com/deve...-now#post90679)
6. Unzip and run Setup.bat
7. Run GenerateProjectFiles.bat
(If you need to build any plugins from source, you can copy them now to \Engine\Plugins)
8. Open UE4.sln with Visual Studio
9. Right Click on UE4 and build
(optional: Go to \Engine\Binaries\Win64 and run UnrealVersionSelector-Win64-Shipping.exe)
Now you can start Unreal Engine by running UE4Editor.exe located in \Engine\Binaries\Win64
errors i know so far:
-warning MSB3245: Could not resolve this reference. Could not locate the assembly "Windows"
-error CS0246: The type or namespace name 'Windows' could not be found
try this: https://forums.unrealengine.com/deve...unreal-release
-missing toolchain or toolset
try this: install correct vc toolset or reinstall
-Errors everywhere
Try this: open visual studio installer and repair your installation. If this doesn't work, you should try to uninstall everything and reinstall again.
you can also try this tool: https://github.com/Microsoft/VisualS...aller/releases
Also try to install visual studio and all components to your c: drive. Splitting the Installation between hard drives can cause problems.
If you can't read the errors of setup.bat and GenerateProjectFiles.bat because the windows close too fast, then try to run them via command prompt.
check this link: https://docs.unrealengine.com/latest...alStudioSetup/
1. Download Visual Studio
2. Open Visual Studio Installer
3. Modify your Visual Studio installation and add all needed components
(You get most components when you simply add the following workloads:
-Universal Windows Platform development
-Desktop development with C++
-Game development with C++
Check individual components and make sure that VC++ toolset, C++ Support, .Net Framework targeting pack & Windows SDK's are selected!)
4. Install Visual Studio
check this link: https://docs.unrealengine.com/latest...gUnrealEngine/
5. Download/clone the uwp unreal engine version you need from github
(links and instructions in first post: https://forums.unrealengine.com/deve...-now#post90679)
6. Unzip and run Setup.bat
7. Run GenerateProjectFiles.bat
(If you need to build any plugins from source, you can copy them now to \Engine\Plugins)
8. Open UE4.sln with Visual Studio
9. Right Click on UE4 and build
(optional: Go to \Engine\Binaries\Win64 and run UnrealVersionSelector-Win64-Shipping.exe)
Now you can start Unreal Engine by running UE4Editor.exe located in \Engine\Binaries\Win64
errors i know so far:
-warning MSB3245: Could not resolve this reference. Could not locate the assembly "Windows"
-error CS0246: The type or namespace name 'Windows' could not be found
try this: https://forums.unrealengine.com/deve...unreal-release
-missing toolchain or toolset
try this: install correct vc toolset or reinstall
-Errors everywhere
Try this: open visual studio installer and repair your installation. If this doesn't work, you should try to uninstall everything and reinstall again.
you can also try this tool: https://github.com/Microsoft/VisualS...aller/releases
Also try to install visual studio and all components to your c: drive. Splitting the Installation between hard drives can cause problems.
If you can't read the errors of setup.bat and GenerateProjectFiles.bat because the windows close too fast, then try to run them via command prompt.
Comment