Creator 2.4.0 Native: UpdateMeshAttribute crashes, because of this._assebler is null

Cocos Creator
#1

Android native build crash after attempt to open new scene

Screenshot_2
Screenshot_21358×276 10.9 KB

#2

I think, your project codes have some issues?

I’ve tested 2.4.0’s example cases on native Android and everything worked fine.

#3

I updated my project from Creator 2.3.1 to 2.4.0. Ios project does not work too. In previous version all worked fine

#4

@zzf_Cocos @SantyWang @jare could you check this issue

#5

I think the scene’s json has been corrupted somehow. maybe you can find some places like "_components": null in the .fire file. you can change it to "_components" : []

#6

The problem is not in the scene.

CCMeshRenderer
CCMeshRenderer942×375 14 KB
CCMeshRendererAndroidStudio
CCMeshRendererAndroidStudio1837×557 25.1 KB

UpdateMeshAttribute does not work correctly, because of this._assebler is null. In our project we dynamically create node with MeshRenderer, game crashes when we set mesh in meshRenderer component. What should we do?

#7

@SantyWang could you check it

#8

Oh, Sorry, we’ll check it

#9

Maybe you should first add MeshRenderer node to scene (which will create the assembler) before set mesh.

#10

This is sample code that creates node wish mesh renderer

        this._highlightNode.is3DNode = true;
        this._highlightNode.active = false;
        this._highlightNode.eulerAngles = meshNode.eulerAngles;
        this._highlightNode.parent = this.bodyContainer; // adding node to scene
        this._highlightNode.scale = this.HIGHLIGHT_SCALE;
        const meshRenderer: cc.MeshRenderer = this._highlightNode.addComponent(cc.MeshRenderer);
        meshRenderer.mesh = meshNode.getComponent(cc.MeshRenderer).mesh;
        meshRenderer.setMaterial(0, CocosAssetsLoader.getAsset(AssetsNames.MATERIAL_TILE_HIGHLIGHT) as cc.Material);```
As you can see we set mesh after node has been added to scene.
#11

@jjyinkailejj have you checked this issue?

#12

@SantyWang @jjyinkailejj have you checked this issue?

#13

@slackmoehrle @SantyWang @jjyinkailejj could you take a look on this issue?

#14

I’ll ping the engineering team and ask how this is going.

#15

@TiniovyKit sorry for the late reply.

This is because your highlightNode active is false, the MeshRenderer will not create the internal assembler.

You can deactive the highlightNode after setting mesh to solve this problem. We may need to add protection check internally.

Thanks for your feedback.