4043 - File Input with Crystilize crash Tiled Build

Bug Reports
1

@Stephen @WFab

For some reason those nodes (i did debug to figure out this) break Tiled Build and crash export

image
image640Ɨ443 32.1 KB

I did spend hour in tryes to debug issue, but have no success
So i publish world file here with input file, so maybe you could try:

World That Break Tiled Build.tmd (60.8 KB)

bitmap image to import:

image0
image01920Ɨ1746 759 KB

1 Like
2

if someone will find reason why that happen - please say me

i did make a project, and can not export it with Tiled Build - but i need to export it with TBšŸ˜­

update: i did fix it by replacing LocalSpace with WorldSpace

3

I just did quick test on my end with this TMD you provided. With the original file missing, it doesnā€™t crash. When I imported my own file within the file node, it does show the preview for a second, and then closes wm to desktop (no warning).

IMO localspace in general needs further testing with these corner cases. I donā€™t know which device is the problem here, Iā€™ll look deeper when Iā€™ve woken up fully lol!

1 Like
4

@Tomatiy My I ask WHY you are exporting ā€œLocal Spaceā€ data as ā€œTiledā€ export?

1 Like
5

Iā€™m not exporting LS with TB

My project is WS that uses LS objects

1 Like
6

I did spend one more hour on debuging

Issue is in Crystalize, Distrotion connected to it, and localspace object connected to crystalize

only if you will make those three conditions - you will receive crashes

1 Like
7

Edit: I originally thought this was applying a localspace distortion to a worldspace object. Will investigate further.

Edit 2: It is indeed the same problem as the localspace into a worldspace - the lack of validation also causes problems with local->local, as WM normalizes localspace inputs to have the same size/aspect as part of the device prologue. But it is not adjusting placement data, causing this crash.

1 Like