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

    After starting the debugger, the APPX folder was generated, and it does have the two files of interest present:

    AppX\xboxservices.config (0 KB)
    AppX\Engine\Plugins\Online\XboxOne\OnlineSubsystemLive\ThirdParty\XSAPI\UWP\build\native\lib\x64\v140\release\Microsoft.Xbox.Services.dll (9,778 KB)
    AppX\Engine\Plugins\Online\XboxOne\OnlineSubsystemLive\ThirdParty\XSAPI\UWP\build\native\lib\x64\v140\release\cpprest140_uwp_2_8.dll (1,310 KB)

    And stepping through FOnlineSubsystemLive::Init() threw an Unhandled Exception:

    Click image for larger version

Name:	LiveException.jpg
Views:	1
Size:	137.9 KB
ID:	1129270

    Comment


      0 bytes for xboxservices.config is not a good sign. Does your output by any chance contain an error something like "Xbox Live Title Id was not in a recognized format. Specify a 32 bit hex number (without leading 0x)"? As for the Appx/Engine folder, that is created as part of the Visual Studio Deploy step. Build on its own wouldn't create one.

      Comment


        Originally posted by jsyarrow View Post
        0 bytes for xboxservices.config is not a good sign. Does your output by any chance contain an error something like "Xbox Live Title Id was not in a recognized format. Specify a 32 bit hex number (without leading 0x)"?
        That is funny, because it does ring a bell. Where would I see the message? In the Log\files or Output window?

        EDIT: I see it in the Output window


        Originally posted by jsyarrow View Post
        As for the Appx/Engine folder, that is created as part of the Visual Studio Deploy step. Build on its own wouldn't create one.
        Yes, I noticed that above

        Comment


          That would show up in the Visual Studio output window during the deploy step (might need to select Deploy explicitly in the Show output from combo). It should also show up in the Unreal Editor output log window when running in-editor deployment. It really should be fatal, but I guess it's not, and on initial inspection it's the only code path I see where xboxservices.config gets created but not filled in.

          Comment


            I changed the decimal value for Title Id to hex, without the leading 0x, and retrying.

            Comment


              Thank you James, I saw the XboxLive Login Screen

              Now I have to integrate the services into my game. . . That is a good thing.

              Comment


                Hello,

                After the previous error I had I resolved it with Visual Studio 2015 and I installed the Windows 8.1 sdk from Visual Studio 2015 itself.

                So after trying to generate the project the command prompt thing popped up and it started installing somethings I also saw something about Xbox Live in yellow that
                it was not found I personally don't care about Xbox live so that's that..

                It created a UE4 Visual Studio Solution file on the folder.

                Is that all that needs to be done, did it work?

                Comment


                  I seem to be having this error when packaging in UE4, any help would be much appreciated.

                  Helper: Packaging (UWP (x64-64bit)): 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:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
                  UATHelper: Packaging (UWP (x64-64bit)): 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:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
                  UATHelper: Packaging (UWP (x64-64bit)): UWPPlatform.Automation.cs(37,63): error CS0103: The name 'Windows' does not exist in the current context [C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
                  UATHelper: Packaging (UWP (x64-64bit)): UWPPlatform.Automation.cs(47,68): error CS0103: The name 'Windows' does not exist in the current context [C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
                  UATHelper: Packaging (UWP (x64-64bit)): UWPPlatform.Automation.cs(52,58): error CS0103: The name 'Windows' does not exist in the current context [C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\UWP\UWP.Automation.csproj]
                  UATHelper: Packaging (UWP (x64-64bit)): Win.Automation -> C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\Win.Automation.dll
                  UATHelper: Packaging (UWP (x64-64bit)): XLocLocalization.Automation -> C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Binaries\DotNET\AutomationScripts\XLocLocalization.Automation.dll
                  UATHelper: Packaging (UWP (x64-64bit)): at AutomationTool.ScriptCompiler.FindAndCompileScriptModules(String ScriptsForProjectFileName, List`1 AdditionalScriptsFolders) in C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\ScriptCompiler.cs:line 180
                  UATHelper: Packaging (UWP (x64-64bit)): at AutomationTool.ScriptCompiler.FindAndCompileAllScripts(String ScriptsForProjectFileName, List`1 AdditionalScriptsFolders) in C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\ScriptCompiler.cs:line 82
                  UATHelper: Packaging (UWP (x64-64bit)): at AutomationTool.Automation.Process(String[] Arguments) in C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\Automation.cs:line 500
                  UATHelper: Packaging (UWP (x64-64bit)): at AutomationTool.Program.MainProc(Object Param) in C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\Program.cs:line 135
                  UATHelper: Packaging (UWP (x64-64bit)): at AutomationTool.InternalUtils.RunSingleInstance(Func`2 Main, Object Param) in C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\AutomationUtils\Utils.cs:line 704
                  UATHelper: Packaging (UWP (x64-64bit)): at AutomationTool.Program.Main() in C:\MICROSOFT_UWP_UNREAL-release_uwp\Engine\Source\Programs\AutomationTool\Program.cs:line 59
                  UATHelper: Packaging (UWP (x64-64bit)): Program.Main: AutomationTool exiting with ExitCode=1 (Error_Unknown)
                  UATHelper: Packaging (UWP (x64-64bit)): BUILD FAILED

                  Comment


                    No one is trying to create some basic universal apps for Hololens? I know that Hololens API is missing, but you think that Microsoft will provide something usable to integrate hololens with unreal and not just unity? The only app that i can create is a 2D screen with inside my unreal screen but not 3d holographs.

                    Thanks for answers!

                    Comment


                      [MENTION=29977]ErnestoEFL[/MENTION] - that sounds right. When you open the sln, do you have UWP64 and UWP32 configurations available? If so, then you're in good shape.
                      [MENTION=770243]Anvar_[/MENTION] - what commit are you at, and what versions of Visual Studio and the Windows SDK do you have installed? Depending on the answer there are a number of places the missing reference might come from. In particular if you're on a slightly older commit and building UAT using VS2017 I can see how you'd hit this.
                      [MENTION=808466]balzar29[/MENTION] - I'd suggest taking a look at the new dev_MixedReality branch that's now part of the UWP fork.

                      Comment


                        Open the sln? what on earth is that? you mean the engine itself? if that's the case no there is no UWP supported platform in there at all

                        Comment


                          Originally posted by ErnestoEFL View Post
                          Open the sln? what on earth is that? you mean the engine itself? if that's the case no there is no UWP supported platform in there at all
                          sln is the file extension for Visual Studio Solution Files. If you open up UE4.sln and you can't select UWP64 or UWP32 as your build platform that would indicate you don't have all the perquisites for building UWP. Are you running on Windows 10, with at least one version of the Windows 10 SDK installed?

                          Comment


                            Well, I am having some success but I encounter an error after pressing Let's Play:

                            Click image for larger version

Name:	XboxLiveLetsPlay.jpg
Views:	2
Size:	21.4 KB
ID:	1129310

                            Click image for larger version

Name:	LetsPlayError.jpg
Views:	2
Size:	31.7 KB
ID:	1129311

                            Comment


                              Originally posted by Jerry.Richards View Post
                              Well, I am having some success but I encounter an error after pressing Let's Play:
                              The troubleshooting page may help here.

                              Also, many of the error codes have helpful descriptions in comments in the Xbox Live SDK headers. Find them in Engine\Plugins\Online\XboxOne\OnlineSubsystemLive\ThirdParty\XSAPI\Microsoft.Xbox.Live.SDK.WinRT.UWP.2016.12.20170107.01\build\native\include\xsapi\errors.h

                              Comment


                                Those are very useful. I believe some of the information applies specifically to the XDK. Do I need to put my Windows 10 into a specific Sandbox:

                                For Windows 10 Desktop, you can use the SwitchSandbox.cmd script that’s located in the Tools directory of the Xbox Live SDK installation.
                                I couldn't find it on my computer. Should I have it?

                                [EDIT 2017.06.09 @ 15:00]
                                The discussions on those links don't seem to help or not accessible.

                                Do I need to associate my app with the Store:

                                Click image for larger version

Name:	AssociateAppStore.jpg
Views:	1
Size:	78.8 KB
ID:	1129315
                                Last edited by Jerry.Richards; 06-09-2017, 05:04 PM.

                                Comment

                                Working...
                                X