Post-update issues 1.3.1 -> 1.4.1

Hey everyone!

Finally updated Defold to recent version. Current major problem:

image

image

Looks like atlas wasn’t found. Some syntax changes maybe?

Worked fine before the update. O_o

Please share code as text as it becomes searchable and also easier for us to mark and comment on.

-10 is PROPERTY_RESULT_RESOURCE_NOT_FOUND:

Does that resource really exist? Have you checked?

Can you reproduce this in a minimal project and share it?

2 Likes

Not so sure. 8( It’s prerelease and about 300Mb of graphics.

Exactly. I don’t want a 300MB project! :slight_smile: The question is if this happens in a new empty project with a single atlas resource property?

1 Like

Hah…
go.set("#", “atlas”, hash ("/atlases/mapobjects/" … tileN … “.a.texturesetc”)) works
go.set("#", “atlas”, hash ("/atlases/mapobjects/" … tileN … “.texturesetc”)) nay)

Ah. yes, this is a fix we made a while back so that a tilesource and an atlas with the same name doesn’t create the same texturesetc file and overwrite each other. An atlas will now build to foobar.a.texturesetc while a tilesource builds to foobar.t.texturesetc.

3 Likes

I didn’t expect manual resource path generation tbh

3 Likes

Fixed in May 2022: https://github.com/defold/defold/pull/6627. I actually don’t see it in the release notes of any version…

3 Likes

Yay! Everything works again. 3 lines of fixes and all is back from ruin.

3 Likes