UI3.2 Known Bugs And Solutions

Look here for answers if something does not go according to plan.

[fixed] or [lagacy] indicate that the issue has been solved in an update.

The Game Modes blueprints contain a node to enable or disable the VR headset. The node Enable HMD is not available in Unreal Engine 5.3 unless the OpenXR plugin is enabled. All other engines don't have that problem as far as I know.

To solve this you can

• Enable the OpenXR plugin.
• Or open the 4 game mode blueprints in the ArchVizUI3 / UI / Blueprints folder, switch to full blueprint editing mode, and remove the node Enable HMD. Compile and save the blueprints.

The older way will stay as an alternative. You would need to rename the DefaultInput.alt to DefaultInput.ini to get the old controls back.

You could also change the Axis Mappings in the Project Settings as seen in the image here. Remove the red marked Look Up mappings and add them to the Move Forward mappings instead.

I don't have access to a VR controller myself at the moment. If that unexpectedly doesn't solve the problem then please let me know.

stefan.doetschel@live.com.

Cheers.

Please open this blueprint in the blueprint editor

• Click on the variable Media Source
• Change it to CliffHouse_Low
• Save and Compile

Finally check if the actor in the level has the same media source set. And look into your directory if the actual movie (MP4 file) is there. Sometimes only the unreal actor is there but not the movie.

• Open BP_SDotControllerKeyboardMouse
• Search for Line Trace By Channel node
• Tick the box for Trace Complex
• Compile and Save

NOTE: The Variation Actor Blueprint needs to be in the same level as the static meshes you want to pick.

• Open the widget UI3_SubMenuPanel
• Go to the Event Graph
• Disconnect the variable Border Margin from Panel Shape Margin without disconnecting the rest of the nodes. Like seen in the image.
• Set the Panel Shape Margin value manually to 0.33
• Compile and Save the Widget.

• Open the Blueprint Controller SDotUI3_ControllerKeyMouse
• Go the the Event Graph
• Connect the variable is Valid Move Target to the Node called Check Move Target as seen in the image.
• Compile and save the blueprint

This will fix it for the keyboard mouse game mode. The gamepad mode can be fixed the same way. But it looks a bit different in the blueprint. - Touch controller seems to be fine.

Problem: You cannot select an object in edit mode. The name changes when you hover over the object, but nothing happens if you select it.

Solution: Open the project settings and search for Touch in the search bar on top of the window. Untick the tick box where it says: Use Mouse for Touch.

If this doesn't help then try to update the UI3 or check if a large collision is in front of the objects.

Part of translucency is Refraction. Turn it off to fix overly dark shadows behind glass. As seen in the image. You can also try to tweak refraction in the glass material. (There might be other places to look for it, like the light sources, or the project and world settings).

This topic has many aspects and it is constantly changing as well. I can only direct you to Google to find out what works best for you.

• making a change to the info maps settings
• moving the info map and then undo the move

I've been trying to find the cause for this. But despite many hours and some different approaches it just doesn't go away.

I'll keep trying and update the project as soon as this issue is solved or maybe it solves itself one day without an apparent reason. The same way it got introduced.

• Open the UI3_MainMenu widget
• Open the Function Hide All Sub Menus
• Change the nodes to look as shown in the image
• Compile and save the widget

This will be fixed in an update soon.