Unreal Engine 4 is available for Win10 UWP app dev now

[ZeJudge]

Hmm, that's a new one. It suggests that UBT can't work out what VS version to use (which in turn affects what Windows SDK is supported). Perhaps try explicitly requesting VS2017 (required for the 16299 SDK) via GenerateProjectFiles -2017.

Yes that worked, you legend

[jsyarrow]

Any ideas?

Hmm, that's a new one. It suggests that UBT can't work out what VS version to use (which in turn affects what Windows SDK is supported). Perhaps try explicitly requesting VS2017 (required for the 16299 SDK) via GenerateProjectFiles -2017.

[ZeJudge]

Hey guys I'm currently experiencing this error when trying to generate project files:

Setting up Unreal Engine 4 project files...
Binding IntelliSense data... 0%ERROR: Unexpected compiler setting when trying to determine Windows SDK folder

I have Windows SDK 10.0.16299.0 installed so not sure whats going on here.

Any ideas?

[som3on3]

I would imagine you're getting a device removed error returned from the CreatePipelineLibrary call in the D3D12 RHI. Right now that's the expected state of things when trying to use UE's D3D12 RHI for UWP on Xbox.

To your other question: when building a UWP game UE only uses Xbox hardware features that are addressable via the normal D3D interface. ESRAM is not used. If your project needs more then you can always consider applying to the ID@Xbox program

Thanks for the info, as for ID@Xbox my game is in early progress state
you can view here:
https://forums.unrealengine.com/comm...e-scroller-wip
i have more from the cave part done, but results on XB1 under UWP are around 20fps@720p with 85% resolution scale.
i loose a bunch of details for those settings ... and since id@xbox is offered for a more complete game, hard to guess what to optimize...

[jsyarrow]

I would imagine you're getting a device removed error returned from the CreatePipelineLibrary call in the D3D12 RHI. Right now that's the expected state of things when trying to use UE's D3D12 RHI for UWP on Xbox.

To your other question: when building a UWP game UE only uses Xbox hardware features that are addressable via the normal D3D interface. ESRAM is not used. If your project needs more then you can always consider applying to the ID@Xbox program

[som3on3]

Also, in "game" mode is ESRAM "touchable" or Unreal only "touches" it with full dev access?

[som3on3]

Is your game deployed as a game or an app:

https://docs.microsoft.com/en-us/win...rce-allocation

If its deployed as an app, the performance will suffer.

Apps do not support DirectX 12 but games do. Also with Games you get full access to the GPU and 4 exclusive CPU cores. On your Xbox if you go the details view of your deployed game you should see the App Type.

I've changed the details to game, as an App is worthless, all reports i've made are under "Game" settings.
I choose DX12, compile, browse upload to xbox from browser, go to xbox, change from app to game, launch => crash with error driver crash and some other texts i don't remember now
but will compile and test again to see exact error

[fkrstevski]

Crashes if compiled with D312 RHI ...

Is your game deployed as a game or an app:

https://docs.microsoft.com/en-us/win...rce-allocation

If its deployed as an app, the performance will suffer.

Apps do not support DirectX 12 but games do. Also with Games you get full access to the GPU and 4 exclusive CPU cores. On your Xbox if you go the details view of your deployed game you should see the App Type.

[som3on3]

Crashes if compiled with D312 RHI ...

[motorsep]

UWP is not Epic's problem
and seems is an XB1 bug because i've installed the UWP on local windows and shows correct

Maybe DX12 bug ? Either way, renderer is in UE4, not in XBOX1, so it could very well be Epic's problem. When you run engine on XB1, it might use different rendering path (even though you run UWP, on Windows it might use one render path, on console it might use another render path).

Good example would be something working on Nvidia, but not on AMD.. Assuming there are no issues with drivers, you don't say "it's AMD's problem". You try solving it in the software.

[som3on3]

Perhaps it's a bug you should be reporting to Epic

UWP is not Epic's problem
and seems is an XB1 bug because i've installed the UWP on local windows and shows correct

[motorsep]

On windows works fine, but on XB1:


And no shadow at all

Perhaps it's a bug you should be reporting to Epic

[som3on3]

Odd, it seems to be working fine in VR (on Windows). https://docs.unrealengine.com/latest...nceandfeatures

On windows works fine, but on XB1:



And no shadow at all

[motorsep]

tried Forward Rendered instead but the Stationary Directional Light is not included somehow and get only Sky Light

Odd, it seems to be working fine in VR (on Windows). https://docs.unrealengine.com/latest...nceandfeatures

[som3on3]

Have you tried baked AO + FXAA and baked AO + MSAA x2 ?

Nope, but will try later on
tried Forward Rendered instead but the Stationary Directional Light is not included somehow and get only Sky Light