What will be the Azure Infrastructure for Unreal graphical project

Question

We got an unreal project which is a pure graphical project where we need to deploy the services on Azure Landing Zone Subscription. That services will use the PixelStreaming Unreal engine servers.

What type of app service configurations like storage, processors, ram can be better for deploying to Azure Landing Zone Subscription where we will have public access disabled in management group level and completed enabled with virtual network and private endpoints connectivity.

Could you please give me an idea on how to deal with this scenario and also the better configuration.

Answer 1

Hello, @Rajoli Hari Krishna !

I'm happy to help with any specific questions you have about Azure Virtual Machines. Architectural and Epic Games Pixel Streaming in Unreal Engine specific questions will be out of scope for these forums but I'll try my best to get you started.

What do I need to deploy Unreal Pixel Streaming in Azure?

Microsoft gaming has a comprehensive guide for deploying Unreal Pixel Streaming in Azure that can be found here:

https://learn.microsoft.com/en-us/gaming/azure/reference-architectures/unreal-pixel-streaming-deploying

It involves deploying either a single GPU VM or multiple GPU VMs if you want to use the Matchmaker service to load balance across many streams.

• Single VM: Unreal Engine 3D App and the Signaling Web Server (SS) on the same VM, allowing users to stream to a single stream which will be shared.
• Multiple VMs with Matchmaker: Provides each user their own 3D stream with the Matchmaker (MM) service on a separate VM to load balance incoming users across multiple GPU VMs running the Signaling Servers.

Using the Single VM scenario as an example, you would deploy a virtual machine as usual with the following settings:

https://learn.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-portal

Note: Some guidance has been changed for added security. See Quick Start Deployment for a Single VM in Azure for full instructions.

• Region: Closest to the users that will be running the Pixel Streaming application
• No infrastructure redundancy required
• Image: Windows 10 Pro Version 1809 or later (or Windows Server 2016 or 2019 if desired)
• Azure Spot instance may allow you to save money if available
• Size: Standard_NV6 (NV12v3's are a new/faster option that is similar in price to NV6, though might require a support ticket to increase your quota before it shows up as an option)
  Note: Most NC* series GPU VMs are setup for ML (TCC) workloads and require an NVIDIA GRID license to use for WDDM, with an exception of NCas T4 v3 which supports Ray Tracing. See Azure GPU VM pricing here for comparisons of price/capabilities.
• Inbound ports: Consider using Azure Bastion or a jump box setup with NSGs for your network for more security for RDP logins.
• Disks: Defaults should be fine for testing, but you'll want to select disks that are appropriate for the type of project you'll be running.
• On the Networking tab, create a new Virtual network and select any existing network resources.
• On the Advanced tab, choose the Select an extension to install link under the Extensions section, and choose the NVIDIA GPU Driver Extension. This is required to install the correct NVIDIA GRID drivers for WDDM support to run 3D applications (make sure you are using NV* series VMs, not NC* series).

There's a lot more involved on the Epic Games Pixel Streaming in Unreal Engine side of things so I would recommend checking out the following documentation:

Epic Games/Unreal:

• Getting Started with Pixel Streaming in Unreal Engine
• Pixel Streaming

Microsoft Games/Azure:

• Unreal Pixel Streaming in Azure
• Deploying Unreal Pixel Streaming in Azure
• Unreal Pixel Streaming at Scale in Azure

General Microsoft Games/Azure:

• Microsoft Game Dev (YouTube)
• Azure for game development

Azure Architecture:

• What is an Azure landing zone?

I hope this helps!