com.jme3.asset.AssetLoadException

An exception has occured while loading asset: Scenes/MagoTribe/MagoTribeMetaData.xbuf

Solutions on the web3

  • via GitHub by Ali-RS
    , 10 months ago
    An exception has occured while loading asset: Scenes/MagoTribe/MagoTribeMetaData.xbuf
  • An exception has occured while loading asset: objects/creatures/goblin/textures/green/ogre.material
  • An exception has occured while loading asset: Common/MatDefs/Light/Lighting.j3md
  • Stack trace

    • com.jme3.asset.AssetLoadException: An exception has occured while loading asset: Scenes/MagoTribe/MagoTribeMetaData.xbuf at com.jme3.asset.DesktopAssetManager.loadLocatedAsset(DesktopAssetManager.java:261) at com.jme3.asset.DesktopAssetManager.loadAsset(DesktopAssetManager.java:373) at com.jme3.asset.DesktopAssetManager.loadModel(DesktopAssetManager.java:416) at com.jme3.gde.core.assets.SpatialAssetDataObject.loadAsset(SpatialAssetDataObject.java:94) at com.jme3.gde.core.assets.actions.ConvertModel$1.run(ConvertModel.java:59) at java.lang.Thread.run(Thread.java:745) Caused by: com.google.protobuf.InvalidProtocolBufferException: Message missing required fields: tobjects[0].transform.rotation.x, tobjects[0].transform.rotation.y, tobjects[0].transform.rotation.z, tobjects[1].transform.translation.y, tobjects[1].transform.rotation.x, tobjects[1].transform.rotation.y, tobjects[1].transform.rotation.z, tobjects[2].transform.translation.y, tobjects[2].transform.rotation.x, tobjects[2].transform.rotation.y, tobjects[2].transform.rotation.z, tobjects[3].transform.translation.y, tobjects[3].transform.rotation.x, tobjects[3].transform.rotation.y, tobjects[3].transform.rotation.z, tobjects[4].transform.translation.y, tobjects[4].transform.rotation.x, tobjects[4].transform.rotation.y, tobjects[4].transform.rotation.z, tobjects[5].transform.translation.y, tobjects[5].transform.rotation.x, tobjects[5].transform.rotation.y, tobjects[5].transform.rotation.z, tobjects[6].transform.translation.y, tobjects[6].transform.rotation.x, tobjects[6].transform.rotation.y, tobjects[6].transform.rotation.z, tobjects[7].transform.translation.y, tobjects[7].transform.rotation.x, tobjects[7].transform.rotation.y, tobjects[7].transform.rotation.z, tobjects[8].transform.translation.y, tobjects[8].transform.rotation.x, tobjects[8].transform.rotation.y, tobjects[8].transform.rotation.z, tobjects[9].transform.translation.y, tobjects[9].transform.rotation.x, tobjects[9].transform.rotation.y, tobjects[9].transform.rotation.z, tobjects[10].transform.translation.y, tobjects[10].transform.rotation.x, tobjects[10].transform.rotation.y, tobjects[10].transform.rotation.z, tobjects[11].transform.translation.y, tobjects[11].transform.rotation.x, tobjects[11].transform.rotation.y, tobjects[11].transform.rotation.z, tobjects[12].transform.translation.y, tobjects[12].transform.rotation.x, tobjects[12].transform.rotation.y, tobjects[12].transform.rotation.z, tobjects[13].transform.rotation.x, tobjects[13].transform.rotation.y, tobjects[13].transform.rotation.z, tobjects[14].transform.translation.y, tobjects[14].transform.rotation.x, tobjects[14].transform.rotation.y, tobjects[14].transform.rotation.z, tobjects[15].transform.translation.y, tobjects[15].transform.rotation.x, tobjects[15].transform.rotation.y, tobjects[15].transform.rotation.z, tobjects[16].transform.rotation.x, tobjects[16].transform.rotation.z, meshes[0].vertexArrays[1].attrib at com.google.protobuf.UninitializedMessageException.asInvalidProtocolBufferException(UninitializedMessageException.java:81) at com.google.protobuf.AbstractParser.checkMessageInitialized(AbstractParser.java:71) at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:209) at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:49) at xbuf.Datas$Data.parseFrom(Datas.java:1082) at jme3_ext_xbuf.XbufLoader.load(XbufLoader.java:35) at com.jme3.asset.DesktopAssetManager.loadLocatedAsset(DesktopAssetManager.java:259) ... 5 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago