For the first error:

Check the syntax on the coding you were doing with the frames. Could a simple little grammar error.

The second error indicates that the game cannot read your walk file. Most likely would be the result of the grammar error.

Originally posted by 『Ariene』 目隠しダ:

Originally posted by ScorpiovaEden:

It's hard to tell - and usually results in trial and error. But if you are referring to your own pieces that you have created, you should be able to see how big each piece is. I am not sure how though. I have not done that type of re-skin using spine.

The only re-skins I have done are re-colors or modifications of the existing assets.

In terms of my own art assets that I use in spine - I have not re-skinned those.

I guess I just have to try and see.

Again Huge Thanks for the Help!

No problem - feel free to ask if anything else comes up. I have made some 60+ of these class mods so I have encountered a lot of the errors that can pop up lol.

It's hard to tell - and usually results in trial and error. But if you are referring to your own pieces that you have created, you should be able to see how big each piece is. I am not sure how though. I have not done that type of re-skin using spine.

The only re-skins I have done are re-colors or modifications of the existing assets.

In terms of my own art assets that I use in spine - I have not re-skinned those.

Smaller is fine. Every piece has a set "size" anything beyond that size - results in white mess.

If you work beyond the skel - it will not work as a skin. If you work within the skel then it can be a skin.

Anything beyond the parameters of the pieces skel's will result in white pixels/boxes.

Whenever I have done skins - I have just worked with them in photoshop and gimp. I do the edits in photoshop - save file as .psd. Then open it in GIMP and export it as a png. Then place the files in the correct folder. Just look at a default class to see how the folders work for the alternate skins they use.

The head animation - yes. The lower animation listing near the bottom of the tree, find that, open it, and the name needs to go there.

For skills you only put the string of the title - for exmple, attack_magic, not the full hero.sprite.attack_magic that is listed as the overall name.

No worries at all. It is a lot to learn, I know I made many mistakes.

I am really not sure at this point. The only other thing I can think of is a pathing/naming issue maybe (the game can't find the files).

Make sure you have debugging turned on in DD in the options - sometimes an error will display on the right hand side of the screen when debugging is on, this can give a hint to the issue.

FX are separate - you can use any hero fx and most enemy fx for your character. Must be renamed properly. I have never made my own fx.

Also make sure the naming is correct in the atlas files.

Most likely your naming your files wrong in spine.

You are naming the animation right? Doesn't matter if it's a walk anim or just an attack anim. All need to be named correctly at the top of your tree in spine as well as in the "animation" section in spine.

So if you have your anim called soldier.sprite.attack_melee ... then in the animation section of spine (just scroll down the tree to where it says animation) and make sure the name is right in there. Which in this case would be attack_melee. In the case of walk, combat, and idle .... the animation section should have it listed as walk or combat, or idle, whcihever one you are making.

Ok - a few things there.

Power of Two must be checked "on".

If you edit your file after exporting you can load up the class again in spine and re-export again, or use GIMP. If you are using gimp then you have to export as a png file and check all boxes that pop up except Adam 7.

The image would be correct then. But again - you can do this through spine by re-opening your file to update the image and re-exporting.

This can be two different things depending on the effect.

A white box blocking your image is the result of using .png code that is sub-standard. Ironically photoshops .png is of the older ilk. I am using the term "older" as I do not know the proper terminology for it. Bascially the code for their png files is garbage. And sadly a lot of programs have that issue. Now - if the image is directly out of spine then that should not be the issue - as spine has good .png.

But if you have altered the image after exporting it from spine in say photoshop and then saved it, the white box will happen. Running the image back through spine would correct it. You can also use GIMP - it is considered one of the best for this issue.

__________________

If you weren't using spine and just re-working the images in a photo-editor/art program then I would say you went outside of the borders for the parts and that results in white particles. But you are using spine so exporting it should get rid of the size constraint.

__________________

If you explain to me the order in which you put together your images, I might be able to understand better that the issue is.

Also - maybe you are exporting it wrong - in which way are you exporting your images?

I am assuming you know you have to set specific margins and us ethe "power of two"? Considering it's may 4th, that is a star wars reference LOL.

But I digress - there are specific settings you need your images set to when exporting them.