Defold 1.13.0 BETA

[ekt]

In defold 1.12.4 3D models were shaded, in 1.13.0 they are no longer shaded. Is this expected?

is this beacsue they are .dae models and the format is now obsolete?

[Mathias_Westerdahl]

@ekt

is this beacsue they are .dae models and the format is now obsolete?

That would likely be the first issue, then yes. The models are simply not loaded.

[Andrew_Fowler]

that worked. thank you

[henriquesousa]

Hi, all! I’m running into an issue where my Samsung Galaxy A13 (ARMv8-L, i.e. 32-bit Android running on a 64-bit Exynos 850 SoC with a Mali-G52) crashes when loading a 2048x2048 3-page paged atlas when the Android graphics API is set to OpenGL+Vulkan or Vulkan and texture compression is enabled.

INFO:GRAPHICS: Transcoding: /hub/art/atlases/game_headers.texturec from 16 to 10 (TEXTURE_FORMAT_RGBA_ASTC_4X4 -> cTFASTC_4x4_RGBA)
ERROR:GRAPHICS: Vulkan Error (../src/vulkan/graphics_vulkan.cpp:4649) VK_ERROR_DEVICE_LOST
A  ../src/vulkan/graphics_vulkan.cpp:4649: void dmGraphics::CopyToTexture(dmGraphics::VulkanContext *, const dmGraphics::TextureParams &, bool, uint32_t, void *, dmGraphics::VulkanTexture *): assertion "0" failed
INFO:CRASH: Successfully wrote Crashdump to file: /data/user/0/<pkg>/files/_crash
ERROR:CRASH: CALL STACK:
#00 pc 0x0000396bfc ...libClassicGames.so
#01 pc 0x000005db38 ...libc.so
#02 pc 0x0000063126 ...libc.so abort+137
#03 pc 0x00000633c6 ...libc.so __assert2+25
#04 pc 0x000024263c ...libClassicGames.so
#05 pc 0x000024743c ...libClassicGames.so
#06 pc 0x00002018dc ...libClassicGames.so
#07 pc 0x00001a986c ...libClassicGames.so
#08 pc 0x00001c41f4 ...libClassicGames.so
#09 pc 0x00001c3eec ...libClassicGames.so
#10 pc 0x00001d2770 ...libClassicGames.so
#11 pc 0x00001d2290 ...libClassicGames.so
#12 pc 0x00001d187c ...libClassicGames.so
#13 pc 0x00001d1760 ...libClassicGames.so
#14 pc 0x00001d1760 ...libClassicGames.so

Right now, the only workaround is forcing OpenGL only or disabling texture compression.

I’ve created an issue already.

[totebo]

@Mathias_Westerdahl

b2d.shape constants

• SHAPE_TYPE_CIRCLE
• SHAPE_TYPE_EDGE
• SHAPE_TYPE_POLYGON
• SHAPE_TYPE_BOX
• SHAPE_TYPE_CHAIN
• SHAPE_TYPE_GRID

Curious, why is SHAPE_TYPE_CHAIN only available for Box2D v2? It’s also part of the Box2D v3, but maybe it was more difficult to hook up?

[Mathias_Westerdahl]

Because there is no “chain” or “edge” type in Box2d v3.
It’s technically called “SEGMENT”.
We do provide EDGE as an alias for the SEGMENT type.

[jhonny.goransson]

Thanks for testing! I’ll check it out next week

[totebo]

Thanks! I mention it because I noticed edge shapes snag moving objects, but chain shapes don’t:

Box2D v2 with chain shapes:

Box2D v3 with edge shapes:

I suppose the solution is to use v2 instead of v3 to avoid snagging.

[Mathias_Westerdahl]

I also have to correct myself a bit, as there seem to exist a b2CreateChain which doesn’t seem to be neither a shape or joint
It’ll have to arrive at a later date I suppose… (we’ll happily accept PR’s ofc)

[CrazyAmphibian]

removed collada support

why?

[britzl]

Collada is an old legacy format. glTF is a modern format which supports many features not present in Collada, such as material settings and embedded textures. glTF is JSON, Collada is XML. We only want to support one format in our tools, and that format is glTF.

[ekt]

@britzl

We only want to support one format in our tools

useless note: I have to re-import a bunch of models but I fully agree with the choice

[One_Red_Eye_Dev]

I found a “bug”?

upon opening a GUI component via Ctrl + P, You cannot zoom in and out without clicking within or panning the view within the Scene editor first.

It cannot be reproduced in 1.12.4 and earlier. Should I open a github issue?

[britzl]

@One_Red_Eye_Dev

Should I open a github issue?

Yes, please!

[One_Red_Eye_Dev]

Done!

Cannot Zoom in or out after opening a GUI component before clicking or panning the Scene editor first

[JosephFerano]

Thanks for catching this! It’s fixed. Should be merged soon.

[Mathias_Westerdahl]

We’ve now updated the BETA with chain functionality and other functions. (see notes above).
See the example project for usage: GitHub - JCash/example-box2d: An example how to use Lua scripting with Box2d in Defold · GitHub (V2 and V3)

[Pawel]

A first example for playing animations with morph targets is live now (credits to @jhonny.goransson for preparing it):

Morph Target Animation | Defold

[illo]

I was trying out 1.13 with the BRDF Deferred Rendering demo (GitHub - martianovdev/Defold-BRDF-Deferred-Rendering-V2 · GitHub) and I ran into this issue: some of the assets seem to be dispalced, shifted either upwards or downwards.

But when I open the same scene in 1.12.4, everything is lined up correctly. I didn’t modify the scene at all, just opened the scene.

After making some code substitutions necessary in 1.13, the scene runs, but the collisions and some objects have been displaced.

Could this be some type of bug?

[britzl]

@illo

but the collisions and some objects have been displaced.

Could this be some type of bug?

It’s this:

@Mathias_Westerdahl

Model transform fixes

We previously had a “helpful” functionality, where we recentered a model to where the gameobject/component was in the scene. It turned out to be the wrong approach, as the model file may be much more complex than that. In fact, it produced errors for some scenes, and we decided to remove that hidden function completely

MIGRATION:. For the most part, we don’t anticipate users being affected by this. If you are affected, the fix is to move the model appropriately within the gameobject/component.