View Issue Details

IDProjectCategoryView StatusLast Update
0002789NoesisGUIUnrealpublic2023-11-15 11:56
ReporterPelo Studio Assigned Tohcpizzi  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.2.2 
Target Version3.2.3Fixed in Version3.2.2 
Summary0002789: Unreal Crash when exporting xaml files.
Descriptionhttps://www.youtube.com/watch?v=WuMHGPOINSo&authuser=0
I followed this tutorial here, and get stuck at the point where you need to import xaml file.
Steps To ReproduceJust import xaml file to unreal Project.
TagsNo tags attached.
PlatformAny

Activities

Pelo Studio

Pelo Studio

2023-10-28 11:28

reporter  

glitch.riv (18,940 bytes)
glitch.xaml (229 bytes)   
<Grid xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
  xmlns:noesis="clr-namespace:NoesisGUIExtensions;assembly=Noesis.GUI.Extensions">
  <noesis:RiveControl Source="glitch.riv"></noesis:RiveControl>
</Grid>
glitch.xaml (229 bytes)   
hcpizzi

hcpizzi

2023-11-03 09:24

developer   ~0008924

There are two issues at play here.

There was a miss handling of Rive files when they failed to import that I've fixed.

The other issue is that, due to Unreal's limitations, we don't support having two files in the same folder with the same name but different extensions. The reason is that they would have the same asset name in Unreal.

Simply renaming glitch.xaml to noglitch.xaml, while leaving glitch.riv the same, results in a correctly imported XAML and no crash, even without the fix I just implemented.

I'll look into warning about this problem during import to avoid confusion.

Thanks.

Issue History

Date Modified Username Field Change
2023-10-28 11:28 Pelo Studio New Issue
2023-10-28 11:28 Pelo Studio File Added: glitch.riv
2023-10-28 11:28 Pelo Studio File Added: glitch.xaml
2023-10-30 11:44 jsantos Assigned To => hcpizzi
2023-10-30 11:44 jsantos Status new => assigned
2023-10-30 11:44 jsantos Target Version => 3.2.3
2023-11-03 09:24 hcpizzi Note Added: 0008924
2023-11-03 09:24 hcpizzi Status assigned => feedback
2023-11-15 11:56 jsantos Status feedback => resolved
2023-11-15 11:56 jsantos Resolution open => fixed
2023-11-15 11:56 jsantos Fixed in Version => 3.2.2