Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(2 edits)

I send the archive. The unicode test_ext38 did not help.

I can confirm that it is indeed behaving in a way that is not expected.(Read embedded binaries)
I will look into it.

It seems to me that we need to find a requirement for spine files.

The binary is not extracted, maybe the mfa file of the project is corrupted.
The sample you gave me failed to read the binaries when I built it over here.

In the project where I copied the frames from the sample into a new project, the binaries also worked.
(There is no visible difference, so it is a very strange behavior.)
http://ugken.com/ext/Spine/sample2_mfa.zip

(5 edits)

I am able to assemble your project properly. But when I transfer from it to the new one, it stops working. It also doesn't work if I transfer my material to your project. It looks like my program or computer can't create a relevant project or material initially. Some of the system configurations allow the utility to work only partially. The situation repeats on different computers and engines. It looks like the reason is at a low level of the system.

I also found that when transferring a scene to another project, the file does not detect itself. We have to hand replace it in the event editor with another one, then back.

I can see a few areas where there are loading errors.
I will look into it to see if it can be corrected.

(It seems to be due to Unicode, character encoding, or other environment-dependent characters.)

This is a problem with loading embedded data, but I think I was able to fix it.
Please check it out.

Appreciate the report.

(2 edits)

the problem was solved by manually adding the engine to the binary space, followed by extraction into the level. It's probably worth pointing out as an alternative.

(1 edit)

Registration in the binary space is a necessary thing.

And although the binary data was to be extracted without an extraction instruction (the extraction instruction is executed inside the Extension)

The extraction function was not working well depending on the environment.
(I believe this has been fixed in the 20231116 version)

Thanks for the report.

I'm using this version. The changes did not affect my computer. Thank you for your response.