Announcement

Collapse
No announcement yet.

Unreal Engine 4 is available for Win10 UWP app dev now

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Actually, I forget to enable the Online Subsystem Live plugin. But now I'm getting an unresolved external NtoHS from the UDPEchoImpl class. Searching for it fails too.

    Leave a comment:


  • replied
    When I include OnlineSubsystemLive in my Build.cs, while debugging, my game doesn't load, it hangs at the splash icon being displayed. Is my setup below correct?

    Code:
    PublicDependencyModuleNames.AddRange(new string[]
            {
                "Core",
                "CoreUObject",
                "Engine",
                "InputCore",
                "InputDevice",
                "AIModule",
                "GameplayTasks",
                "UMG",
                "XmlParser",
                "OnlineSubsystem"
            });
    
            // Uncomment if you are using Slate UI
            PrivateDependencyModuleNames.AddRange(new string[]
            {
                "Slate",
                "SlateCore",
                "OnlineSubsystem"
            });
    
            DynamicallyLoadedModuleNames.Add("OnlineSubsystemLive");

    Additionally, in DefaultEngine.ini I have the following:

    Code:
    [OnlineSubsystem]
    DefaultPlatformService=OnlineSubsystemLive

    Leave a comment:


  • replied
    Originally posted by jsyarrow View Post
    I haven't yet pushed the change to pull the UWP UBT and UAT dependencies from the Windows SDK and/or VS2017, so there's currently a requirement to have VS2015 installed (after which you can go back to using VS2017). From the look of things that's what you're missing. Proper fix should be in soon.
    Is it alright if you let me know when its available Private Message please?

    Leave a comment:


  • replied
    Originally posted by ErnestoEFL View Post
    Does anyone know how to fix this?
    I haven't yet pushed the change to pull the UWP UBT and UAT dependencies from the Windows SDK and/or VS2017, so there's currently a requirement to have VS2015 installed (after which you can go back to using VS2017). From the look of things that's what you're missing. Proper fix should be in soon.

    Leave a comment:


  • replied
    Does anyone know how to fix this?

    Click image for larger version

Name:	Captureue4.PNG
Views:	1
Size:	29.3 KB
ID:	1129226

    Leave a comment:


  • replied
    Originally posted by jsyarrow View Post
    Yes, you should check the 'Is Creators Program Title' box. Do you have commit f5362d5? That should have addressed some problems with newer settings persisting across editor sessions. I should also note that if you're using this fork with the Creators Program you're blazing a trail (and we appreciate it!)

    For coding against Live features I'd recommend starting with the existing functionality that's wrapped to the standard UE4 online interfaces, e.g. IOnlineLeaderboards. The MS docs are still great for building an understanding of Xbox Live concepts, but less useful for code in UE unless you find yourself needing to extend what's already there.
    1. I just refreshed from the repo and rebuilding now. I've been working locally for the past 15 days so I'm not sure what level my version was at.

    2. My upload to the Store worked flawlessly which was nice to see.

    3. I should have known about the IOnlineLeaderboards Hopefully I'll have something working by tomorrow.

    Better yet, it would be nice to get my game published under UE UWP. So I appreciate all the help. Thank you.

    Leave a comment:


  • replied
    Originally posted by Jerry.Richards View Post
    I'm back, now trying to make use of the Xbox Live Services. On the UWP page should I check:

    Is Creators Program Title?

    When exiting and restarting the UE Editor it appeared that my setting for it was lost.

    I'm performing a UWP build and will upload it to the Store to see if the process works. Additionally, I have my sandbox setup, and if I understood correctly, I should be able to perform testing without the upload to the Store. I just need to start with the items that I would like to include in my project such as Social, Leaderboards, and Achievements.

    Currently, I'm reviewing the documentation to save results to the Leaderboards. That appears to be the easiest place to start. The trick is how to tie in UWP libraries to access the Microsoft Parallel Programming Library, as shown at the bottom of this page: https://developer.microsoft.com/en-u...s/leaderboards

    Or is there another set of API's we should be using from UE4, C++ (unmanaged)?
    Yes, you should check the 'Is Creators Program Title' box. Do you have commit f5362d5? That should have addressed some problems with newer settings persisting across editor sessions. I should also note that if you're using this fork with the Creators Program you're blazing a trail (and we appreciate it!)

    For coding against Live features I'd recommend starting with the existing functionality that's wrapped to the standard UE4 online interfaces, e.g. IOnlineLeaderboards. The MS docs are still great for building an understanding of Xbox Live concepts, but less useful for code in UE unless you find yourself needing to extend what's already there.

    Leave a comment:


  • replied
    I'm back, now trying to make use of the Xbox Live Services. On the UWP page should I check:

    Is Creators Program Title?

    When exiting and restarting the UE Editor it appeared that my setting for it was lost.

    I'm performing a UWP build and will upload it to the Store to see if the process works. Additionally, I have my sandbox setup, and if I understood correctly, I should be able to perform testing without the upload to the Store. I just need to start with the items that I would like to include in my project such as Social, Leaderboards, and Achievements.

    Currently, I'm reviewing the documentation to save results to the Leaderboards. That appears to be the easiest place to start. The trick is how to tie in UWP libraries to access the Microsoft Parallel Programming Library, as shown at the bottom of this page: https://developer.microsoft.com/en-u...s/leaderboards

    Or is there another set of API's we should be using from UE4, C++ (unmanaged)?

    Leave a comment:


  • replied
    The build and automation tools have some extra dependencies in the UWP fork that are currently sourced from VS2015 (or the Windows 8 SDK, but that's probably less relevant). I should update the paths to support pulling from VS2017 and/or the Windows 10 SDK, but in the meantime you can probably work around the problem by installing VS2015 but continuing to build/package using VS2017.

    Leave a comment:


  • replied
    PS: my log file is somethng like this

    Code:
    UATHelper: Packaging (UWP (x86-32bit)): Running AutomationTool...
    UATHelper: Packaging (UWP (x86-32bit)): Automation.ParseCommandLine: Parsing command line: -ScriptsForProject="C:/Users/io/Documents/Unreal Projects/MyProject/MyProject.uproject" BuildCookRun -nocompileeditor -nop4 -project="C:/Users/io/Documents/Unreal Projects/MyProject/MyProject.uproject" -cook -stage -archive -archivedirectory=C:/Users/io/Desktop/2222 -p
    ackage -clientconfig=Development -ue4exe=UE4Editor-Cmd.exe -pak -prereqs -nodebuginfo -targetplatform=UWP32 -build -utf8output -compile
    UATHelper: Packaging (UWP (x86-32bit)): Automation.Process: Setting up command environment.
    UATHelper: Packaging (UWP (x86-32bit)): ScriptCompiler.FindAndCompileScriptModules: Compiling scripts.
    LogSlate: Took 0.000222 seconds to synchronously load lazily loaded font '../../../Engine/Content/Editor/Slate/Fonts/DroidSansMono.ttf' (77K)
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   DotNETUtilities -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\DotNETUtilities.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   UnrealBuildTool -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\UnrealBuildTool.exe
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   AutomationUtils.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationUtils.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   AllDesktop.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\AllDesktop\AllDesktop.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   Localization.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Localization.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   OneSkyLocalization.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\OneSkyLocalization.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   AutomationScripts.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\AutomationScripts.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   Android.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Android\Android.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   BuildGraph.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\BuildGraph.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   HTML5.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\HTML5\HTML5.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   MobileDeviceInterface -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\IOS\MobileDeviceInterface.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   IOS.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\IOS\IOS.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   Linux.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Linux\Linux.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   Mac.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Mac\Mac.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   TVOS.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\TVOS\TVOS.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild: UWPPlatform.Automation.cs(26,4): error CS0246: The type or namespace name 'Windows' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild: UWPPlatform.Automation.cs(26,63): error CS0246: The type or namespace name 'Windows' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild: UWPPlatform.Automation.cs(37,63): error CS0103: The name 'Windows' does not exist in the current context [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild: UWPPlatform.Automation.cs(47,68): error CS0103: The name 'Windows' does not exist in the current context [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild: UWPPlatform.Automation.cs(52,58): error CS0103: The name 'Windows' does not exist in the current context [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   Win.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Win.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): MSBuild:   XLocLocalization.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\XLocLocalization.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): CommandUtils.Run: Run: Took 4,6423879s to run MSBuild.exe, ExitCode=1
    UATHelper: Packaging (UWP (x86-32bit)): Program.Main: ERROR: AutomationTool terminated with exception: AutomationTool.AutomationException: Failed to build "C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\Scripts\UAT.proj":
    UATHelper: Packaging (UWP (x86-32bit)):   DotNETUtilities -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\DotNETUtilities.dll
    UATHelper: Packaging (UWP (x86-32bit)):   UnrealBuildTool -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\UnrealBuildTool.exe
    UATHelper: Packaging (UWP (x86-32bit)):   AutomationUtils.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationUtils.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   AllDesktop.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\AllDesktop\AllDesktop.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   Localization.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Localization.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   OneSkyLocalization.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\OneSkyLocalization.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   AutomationScripts.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\AutomationScripts.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   Android.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Android\Android.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   BuildGraph.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\BuildGraph.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   HTML5.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\HTML5\HTML5.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   MobileDeviceInterface -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\IOS\MobileDeviceInterface.dll
    UATHelper: Packaging (UWP (x86-32bit)):   IOS.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\IOS\IOS.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   Linux.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Linux\Linux.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   Mac.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Mac\Mac.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   TVOS.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\TVOS\TVOS.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)): UWPPlatform.Automation.cs(26,4): error CS0246: The type or namespace name 'Windows' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): UWPPlatform.Automation.cs(26,63): error CS0246: The type or namespace name 'Windows' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): UWPPlatform.Automation.cs(37,63): error CS0103: The name 'Windows' does not exist in the current context [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): UWPPlatform.Automation.cs(47,68): error CS0103: The name 'Windows' does not exist in the current context [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)): UWPPlatform.Automation.cs(52,58): error CS0103: The name 'Windows' does not exist in the current context [C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
    UATHelper: Packaging (UWP (x86-32bit)):   Win.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Win.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):   XLocLocalization.Automation -> C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\XLocLocalization.Automation.dll
    UATHelper: Packaging (UWP (x86-32bit)):    at AutomationTool.ScriptCompiler.FindAndCompileScriptModules(String ScriptsForProjectFileName, List`1 AdditionalScriptsFolders) in C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\ScriptCompiler.cs:line 180
    UATHelper: Packaging (UWP (x86-32bit)):    at AutomationTool.ScriptCompiler.FindAndCompileAllScripts(String ScriptsForProjectFileName, List`1 AdditionalScriptsFolders) in C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\ScriptCompiler.cs:line 82
    UATHelper: Packaging (UWP (x86-32bit)):    at AutomationTool.Automation.Process(String[] Arguments) in C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\Automation.cs:line 500
    UATHelper: Packaging (UWP (x86-32bit)):    at AutomationTool.Program.MainProc(Object Param) in C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\Program.cs:line 135
    UATHelper: Packaging (UWP (x86-32bit)):    at AutomationTool.InternalUtils.RunSingleInstance(Func`2 Main, Object Param) in C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\Utils.cs:line 704
    UATHelper: Packaging (UWP (x86-32bit)):    at AutomationTool.Program.Main() in C:\Users\io\Downloads\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\Program.cs:line 59
    UATHelper: Packaging (UWP (x86-32bit)): Program.Main: AutomationTool exiting with ExitCode=1 (Error_Unknown)
    UATHelper: Packaging (UWP (x86-32bit)): BUILD FAILED
    PackagingResults:Error: Error Unknown Error

    Leave a comment:


  • replied
    hi all, i've installed the last github ue4 with the UWP, than i have visual studio community 2017 and these platform versions:
    10.0.10240.0
    10.0.10586.0
    10.0.14393.0
    10.0.15063.0
    but i can't package anything, and with anything i mean that i can't package win32, win64, UWP32 and UWP64.
    Anyone have some ideas? I need to recompile the github UE4 with VS2015?

    Leave a comment:


  • replied
    It seems the blank UWP github project finally compiled with my VS2015, i've installed 10.0.10586.212. Thanks.

    Leave a comment:


  • replied
    I'd suggest removing (and not replacing) 26624. Despite having the largest build number, it's the oldest. And it's possible that the out of order numbering is confusing the build system.

    Leave a comment:


  • replied
    I have:
    10.0.26624
    10.0.15063.137
    10.0.10586.212
    which version exactly should I remove and install ?

    Leave a comment:


  • replied
    ---------------------------
    Windows Software Development Kit - Windows 10.0.10586.212
    ---------------------------
    You must uninstall the Windows Software Development Kit - Windows 10.0.10586.212 before you can install the latest version of the kit.
    ---------------------------
    OK
    ---------------------------
    Sounds like a plan, will try it )

    Leave a comment:

Working...
X