We are going to update the instructions on the bottom-left of the screen in ARPlatformInitializer.
We are going to grab each of the instructions and update it with new text once we know that the project is running on an AR platform.
Paste the code snippet below into ARPlatformInitializer.cs:
Updating ARPlatformInitializer
In MainScene drag the GameUI GameObject from Hierarchy into the Game UI Document field within the AR Platform Initializer component in Inspector when AR Session is selected in Hierarchy
Moving GameUI into ARPlatformInitializer compoinent
Go to the BuildSettings folder, select iOS-Build, then click "Build and Run" in Inspector
Then launch the app
Hitting "Build and run" for the iOS-Build
Updating instructions dynamically for AR players
We now have dynamic Game UI based on platform type
We updated ARPlatformInitializer
Updating the styling
We are going to update the styling to update the padding in the footer and header. Currently, the curve and notch in newer iPhones cover up quite a bit at the top and bottom of the screen. Although adjusting the styling to account for newer iPhones is not required (well, none of this is), we are explaining this just to make your project a little easier to navigate. We will also update our logo to use an SVG.
With your SVG selected go to the Inspector and select
"UI Toolkit Vector Image" in the drop-down list for Generated Asset Type
Target Resolution 2160p
Click "Apply"
Adding Moetsi Logo SVG to UI/ as a UI Toolkit Vector Image
Paste the code snippet below into TitleScreenUI USS:
Updating TitleScreenUI USS
If you want to use a different SVG (not the Moetsi logo SVG), you will need to update the name of the SVG in the .logo class.
Paste the code snippet below into GameUI USS:
Updating GameUI USS
Let's also update our PanelSettings (in the UI folder) to better handle mobile and desktop.
In Inspector, make the following updates to PanelSettings:
Scale Mode = Scale With Screen Size
Screen Match Mode = Match Width Or Height
Reference Resolution
X = 1000
Y = 1200
Screen Match Mode Parameters
Height = 1
Our UI dynamically updates when we change our Scale Mode to "scale with screen size." We choose "height" as the main driver because we have a more vertical UI in our app. If it is wider, it should not affect the scale of our UI, but if it is taller or shorter we would want our UI to scale.
Updating PanelSettings
Now build for iOS (clicking "Build and Run" in Inspector when iOS-Build is selected from the BuildSettings folder) and take a look at our new UI updates
Shooting down AR player
Getting shot down by the desktop player
We now have a more desktop/mobile-friendly UI
We imported an SVG
We updated TitleScreen USS
And updated the logo class to use the imported SVG name if necessary
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.XR.ARFoundation;
using Unity.Entities;
using Unity.NetCode;
using UnityEngine.UIElements;
public class ARPlatformInitializer : MonoBehaviour
{
[SerializeField] GameObject m_Session;
[SerializeField] GameObject m_SessionOrigin;
//This is how we will grab access to the UI elements we need to update
public UIDocument m_GameUIDocument;
private VisualElement m_GameManagerUIVE;
private VisualElement m_BottomLeft;
private Label m_1stInstruction;
private Label m_2ndInstruction;
private Label m_3rdInstruction;
private Label m_4thInstruction;
void OnEnable()
{
//We set the labels that we will need to update
m_GameManagerUIVE = m_GameUIDocument.rootVisualElement;
m_BottomLeft = m_GameManagerUIVE.Q<VisualElement>("bottom-left");
m_4thInstruction = m_GameManagerUIVE.Q<Label>("instructions-4");
m_3rdInstruction = m_GameManagerUIVE.Q<Label>("instructions-3");
m_2ndInstruction = m_GameManagerUIVE.Q<Label>("instructions-2");
m_1stInstruction = m_GameManagerUIVE.Q<Label>("instructions-1");
}
IEnumerator Start() {
if ((ARSession.state == ARSessionState.None) ||
(ARSession.state == ARSessionState.CheckingAvailability))
{
yield return ARSession.CheckAvailability();
}
if (ARSession.state == ARSessionState.Unsupported)
{
//If we AR is unsupported we disable both GameObjects
m_SessionOrigin.SetActive(false);
m_Session.SetActive(false);
}
else
{
//If AR is supported we create our IsARPlayerComponent singleton in ClientWorld
foreach (var world in World.All)
{
if (world.GetExistingSystem<ClientSimulationSystemGroup>() != null)
{
world.EntityManager.CreateEntity(typeof(IsARPlayerComponent));
}
}
//Due to a UI Toolkit bug we cannot currently update existing labels without getting wacky behavior
// https://forum.unity.com/threads/updating-labels-causes-a-gap-on-first-ui-view.1049081/
//So we will remove all labels and attach new ones to our bottom left container
m_BottomLeft.Remove(m_4thInstruction);
m_BottomLeft.Remove(m_3rdInstruction);
m_BottomLeft.Remove(m_2ndInstruction);
m_BottomLeft.Remove(m_1stInstruction);
//Now that our container is empty we make 3 new labels for our 3 new instructions
Label instruction1 = new Label();
Label instruction2 = new Label();
Label instruction3 = new Label();
//Now we add our instruction-text class to our labels so they have the same styling as before
instruction1.AddToClassList("instruction-text");
instruction2.AddToClassList("instruction-text");
instruction3.AddToClassList("instruction-text");
//Now we update the instruction text in the labels
instruction3.text = "Tap with 1 finger to spawn and shoot";
instruction2.text = "Move device to move player";
instruction1.text = "Tap with 3 fingers to self-destruct";
//Because we flex grow upwards we start with the bottom instruction (instruction 1) and then add the rest
m_BottomLeft.Add(instruction1);
m_BottomLeft.Add(instruction2);
m_BottomLeft.Add(instruction3);
}
}
}
