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.

New Info Map

Updated Scene

UI Design

First make a few changes to the Project Settings

• Set the Default Game Map In the Maps and Modes section. This needs to be the main (persistent) level of your scene.
• Add the levels that need to be cooked in the Packaging - Advanced - List of Maps to include... array. You don't need to add any sub levels that are loaded from your main levels to the list. But you need to add any other levels if the user can travel to them.
• Add your movie directory there as well. I put them in both arrays Additional Non-Asset Directories ... . It's probably not necessary that way.

NOTE: Leaving the list of maps empty can increase your package size significantly. In that case everything in the project will be packaged.

Sometimes Unreal didn't install some additional software needed. Check that you have the software when the packaging fails early on:

• Windows SDK
• Visual Studio (free community version)
• Net framework (if everything else doesn't help)

Check the output log if the packaging fails later on. Scroll down to the very end and then look for any red messages above, like a missing structure here:

[2023.06.08...]LogProperty: Error: FStructProperty::Serialize.../UI/Widgets/UI3_CustomButton.UI3_CustomBu tton_C: Color Set Used'. Unknown structure.

Scroll down for a few more solutions for failed packaging.

Unreal Documentation

Look for the 2 widgets below if packaging fails with an error about those assets:

• UI3_IconButton.uasset (NOT IconButton02)
• UI3_ListButton.uasset

They are referencing an old structure. I added dummy widgets with the same name to overwrite them in case of an update. You can delete them as they are not used anymore since May 2023.

The update also fixes the same error for the widgets

• UI3_CustomButton
• UI3_PreviewButton

They had a reference to the variable called Color Set Used. The variable itself used the deleted structure ArchVizUI_V3/UI/Etc/Structures. You can put this variable back into the folder to solve both problems without updating. Download the file from the link below:

STR_UI3_UIColourStructure

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 update fixes the interface not responding
• Set the default aperture to 32 or it will be blurry because the tablet is out of focus. (Settings - Cinematic Camera)
• use colour scheme id 3 as a start
• increase icon and text sizes

Cinematic Camera Settings

Too Bright

This is a side effect of using the dynamic sky blueprint. You need to turn down the brightness of all text and image elements. Follow the link at the end of this section.

Too Dark

There was a bug where lowering the brightness is applied twice for some image. Change the widget UI3_Image to look like the image. This has been fixed in an update.

Using Game Modes

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.

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.