Scaling down - Mesh question

jimbobjim

Hi,
I've had to scale down some Spine files from a larger size to in-game true size. I did this by exporting and setting the atlas files to be a smaller scale (from 1 to 0.3), then reimporting the json and setting the skeleton to the same scale (0.3). File is working fine in Spine and when viewing in the skeleton viewer.

After showing to our developers they have pointed out a potential issue - They are saying that even though the files have been scaled down that "the meshes and canvas remain at the original larger size, which could create problems with performance in-game". This is the first I've come across this and they are suggesting starting the files completely from scratch (!). Would anyone have any additional information on this or be able to provide a potential solution?

Also, if it helps provide any additional info, we have to use Spine 3.6.53.

Thank you in advance for any help provided.

James

Misaki

jimbobjim Hmm, I'm not sure I fully understand your problem, but it seems that your developer's opinion might not be correct.

By the way, it's generally more efficient to use the latest version of the runtime. Why did your project choose such an old version like 3.6? It might be better if the developers themselves asked about the performance issues they're facing, rather than having you ask on their behalf.

Nate

jimbobjim the meshes and canvas remain at the original larger size, which could create problems with performance in-game

Meshes are a collection of vertices. How far apart the vertices are does not affect performance. When you imported with a scale < 1, the meshes vertices go closer together.

Spine doesn't have the concept of a "canvas", so I don't know what they mean there.