phtcloud We apologize for the inconvenience. I think you may be encountering a problem similar to the one reported in the following thread:
https://esotericsoftware.com/forum/d/28829-update-project-with-cli-/5

As described there, this is not a bug in versions 4.2 or 4.3, but rather a bug in older versions that was fixed when opening them in newer versions.
We understand that this may be troublesome when upgrading older versions of Spine projects, but unfortunately, the fix described in the thread linked above is necessary.

By the way, there is a translation button on this forum, so you don't need to prepare your own English translation. Feel free to post in your native language.

phtcloud

所以说这个问题将在未来4.3版本修复？不用手动去修？还是说还是要手动去修复

In version 4.3.38-beta and later, triangle issues in meshes should be automatically corrected when importing data and exporting in JSON or binary format.

因为我使用4.3.38-beta还是无法查看贴图仍然丢失（

Since I haven’t actually seen your Spine project, this is only a guess. However, it’s likely that the mesh vertices are simply misaligned, and the image references themselves remain unchanged.
Try selecting the relevant mesh attachment, clicking the Edit Mesh button, unchecking Deformed, and then reviewing the vertex coordinates. I think there may be a discrepancy between the vertices and image coordinates, similar to the following:

You should be able to make a complete fix by aligning the positions of the vertices.

If that doesn't work, please send us a Spine project via email so that we can investigate the issue in more detail. : contact@esotericsoftware.com
Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.

phtcloud Thank you for sending us your actual Spine project! In your case, it appears that the top left vertex is actually overlapping two vertices, and one of them is positioned outside the hull. Uncheck the Deformed checkbox in Edit Mesh mode and delete the top left vertex. This should display the image correctly. (I have verified that this operation works correctly in 4.2.)

phtcloud

我发送了另一个服务器上的一个例子

I'm not sure what you mean; the machine translation doesn't seem to be working properly. I thought you meant that you sent another email, but I haven't received any other emails.

如果直接在4.2对顶点删除会丢失动作

I don't understand why the animation is lost by deleting only the vertices instead of resetting the mesh. You can delete or modify mesh vertices even after setting weights. Could you explain in detail why this situation has arisen?

phtcloud Thank you for the additional explanation. I see, that is indeed troublesome.
At least we can say that 4.2 unfortunately will not be updated, so we will have no choice but to address this issue in 4.3.

We have successfully received your new email, and it appears that deleting the vertex causing the problem in this skeleton, as in the previous case, will resolve the issue:

We will examine whether it is possible to automatically resolve the issue in future versions using the Spine project files you provided.

You're right, there are multiple problems with how Spine handles invalid meshes.

We should not reset the mesh weights except if the mesh has no bones at all. We've fixed this in 4.3.39-beta! This fixes the problem where you open a project, it says it reset a mesh, and your work is gone without giving you a chance to fix the mesh.

In 4.3.39-beta we now detect duplicate vertices and automatically remove one. This allows you to open your m.zip project and the mesh is fixed automatically. A warning is shown to let you know it changed the mesh, which may help if you need to fix the mesh for older versions.

Your other project is harder to fix automatically:


This selected internal vertex has 2 orange edges and it's slightly on the outside of the hull. This makes the orange edges invalid, as edges cannot cross the hull or any other edges. To fix it we could move the vertex, but it's very difficult to determine how to move the vertex in a way that fixes any similar problem AND doesn't cause any new problems.

We could delete the orange edges. That would all triangles to be computed, but the vertex would still be outside the hull. When that happens, the vertex does not affect the mesh image, so the behavior of your mesh would not be the same. You'd have a useless vertex hanging around.

Since there isn't a great way to fix it, probably it's best if we only warn about it. You'll see Mesh cannot be triangulated and can fix it manually.

We added --debug-triangulation which logs when triangulation fails. This can happen normally, for example as you drag a vertex to an invalid position. However, it doesn't normally happen when a project loads. This debug logging is probably not useful most of the time, but there may be some case where it helps identify meshes with bad vertices. Until the next launcher update, you'll need --ignore-unknown-args so the launcher doesn't complain about --debug-triangulation being invalid.

We have also had for some time --mesh-debug. You can use it 1, 2, or 3 times for more info.

For example with --ignore-unknown-args --debug-triangulation --mesh-debug you might see:

WARNING: Triangulation failed: Internal edge is outside of hull: 16, 62
WARNING: Mesh cannot be triangulated: [mesh: palm(L)_lv1, skeleton: skeleton, slot: palm(L)_lv1]

You would always see Mesh cannot be triangulated but now you also see the triangulation warning. The numbers correspond to the 2 vertices that make up the edge that is invalid. Since you have --mesh-debug you can see those vertex numbers:

16 and 62 are at the bottom, so you know where you need to move the vertices to fix it. If there are multiple problems, check the log again to see the next problem.

Fixing up vertices manually is not fun. Sorry for the trouble! I wish we could fix them all automatically, but it's a tricky problem. On the bright side, once your projects are fixed and moved to 4.3, you should never have triangulation problems again.

Thanks for sending your 3rd project. It has a problem that is a little different: an internal vertex is pushed up against the mesh hull. This can actually be considered valid, though it makes for a degenerate (zero area) triangle, which isn't very useful.

We have now revised how we process meshes and the rules involved for vertices and edges. It is no longer valid to have a vertex outside the mesh hull. This was never useful, as the vertex could not be included in the triangulation, so it could could not affect the mesh image. Vertices outside the mesh hull are now deleted on project load.

We are now able to (in 4.3.39-beta) automatically fix your 3 projects when the projects are loaded. Hopefully this makes your life easier! Exporting from the command line works the same as loading the project in the editor UI and exporting.

You can export 4.2 JSON from 4.3 and use Import Data to bring it into 4.2, but this is not recommended as you may lose data in some ways. It is much better to move to 4.3 when you can. While still beta, the 4.3 runtimes should be functional now. If you find problems with them, please let us know.

You can use the CLI to export 4.2 JSON from 4.3 by saving an export setting JSON file. You should see "version": 4.2 in that export settings JSON. The exported skeleton JSON will show at the top eg "spine": "4.2-from-4.3.39-beta",. You can import this into 4.2, but check thoroughly to see the if process lost any important data. You should not try to use this JSON directly in a runtime, instead import into 4.2 and export it from 4.2 properly to ensure runtime compatibility.