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

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.

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.

A couple of users messaged me that they get this error message. The tablet seems to miss its texture, or the texture isn't accessible. Make sure you use the SDot VR game mode for VR. I'm not sure what happened there. Please check the following:

• open the Blueprint SDotUI3_CharacterV3
• look for the tablet mesh in the character viewport
• see if it has its material applied

The material is in the folder Content/ArchVizUI3/UI/Mat and is called M_MobileDevices01_i01.

Please reassign the material, if the material isn't applied in the static mesh browser for the tablet or in the character.

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.

• 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.