Merge pull request #111360 from ChristopherManthei/master

Platform limitations update

Author: shawnmariejones

articles/remote-rendering/how-tos/unity/objects-components.md

@@ -9,7 +9,7 @@ ms.topic: how-to
 
 # Interact with Unity game objects and components
 
-Azure Remote Rendering (ARR) is optimized for vast numbers of objects (see [Limits](../../reference/limits.md)). While it's possible to manage large and complex hierarchies on the host, replicating them all in Unity on low-powered devices is unfeasible.
+Azure Remote Rendering (ARR) is optimized for vast numbers of objects (see [Limitations](../../reference/limits.md)). While it's possible to manage large and complex hierarchies on the host, replicating them all in Unity on low-powered devices is unfeasible.
 
 Therefore, when a model is loaded on the host, Azure Remote Rendering mirrors the information about the model structure on the client device (which will incur network traffic), but does not replicate the objects and components in Unity. Instead, it expects you to request the needed Unity game objects and components manually, such that you can limit the overhead to what is actually needed. This way you have more control over the client-side performance.
 

articles/remote-rendering/overview/system-requirements.md

@@ -41,7 +41,7 @@ Even though the correct H265 codec might be installed, security properties on th
 
 ## Devices
 
-Azure Remote Rendering currently only supports **HoloLens 2** and Windows desktop UWP as a target device.
+Azure Remote Rendering currently only supports **HoloLens 2** and Windows desktop as a target device. See the [platform limitations](../reference/limits.md#platform-limitations) section.
 
 It's important to use the latest HEVC codec, as newer versions have significant improvements in latency. To check which version is installed on your device:
 

articles/remote-rendering/quickstarts/deploy-to-desktop.md

@@ -54,6 +54,9 @@ Only flat desktop apps are currently supported on desktop so VR support has to b
   ![Solution configuration](./media/unity-deploy-config-pc.png)
 1. Build the solution (F7).
 
+> [!WARNING]
+> Make sure to select **x86**. **x64** is currently not supported, see [platform limitations](../reference/limits.md#platform-limitations).
+
 ## Launch the sample project
 
 Start the Debugger in Visual Studio (F5). It will automatically deploy the app to the PC.

articles/remote-rendering/reference/limits.md

@@ -1,15 +1,15 @@
 ---
-title: Limits
+title: Limitations
 description: Code limitations for SDK features
 author: erscorms
 ms.author: erscor
 ms.date: 02/11/2020
 ms.topic: reference
 ---
 
-# Limits
+# Limitations
 
-A number of features have size or count limitations due to internal details of the running system.
+A number of features have size, count, or other limitations.
 
 ## Azure Frontend
 
@@ -35,4 +35,13 @@ The allowable number of polygons for all loaded models depends on the size of th
 |premium| no limit |
 
 
+## Platform limitations
 
+**Windows 10 desktop**
+
+* "PC Standalone" deployment from Unity is not supported. Use UWP instead.
+* UWP/x86 is the only supported UWP platform. UWP/x64 is not supported.
+
+**Hololens 2**
+
+* The [render from PV camera](https://docs.microsoft.com/windows/mixed-reality/mixed-reality-capture-for-developers#render-from-the-pv-camera-opt-in) feature is not supported.

articles/remote-rendering/reference/toc.yml

@@ -4,7 +4,7 @@
   href: regions.md
 - name: Network requirements
   href: network-requirements.md
-- name: Limits
+- name: Limitations
   href: limits.md
 - name: Remote Rendering samples repository (GitHub)
   href: https://github.com/Azure/azure-remote-rendering