Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

If it is built into UnPack, then there doesn't seem to be a build problem.

I am wondering why the DLL is not called.

Would a minimal build, such as the sample file, do the same?

(I can also think of possible effects due to interference from other extensions, perhaps.)

(2 edits)

I tried to build your project specifically. The result was sad identically. That is, the complexity of the project does not solve. The program or add-on does not work specifically in this function, but it works in the rest.

(2 edits)

We have prepared a "test_ext38.zip" file.
Overwrite this with the extension for building "Data\Runtime\Unicode"

Please experiment to see if the DLL is called by the built executable.

This is a slightly modified version of the program regarding DLL calls.
(Since this is for experimental use, only the stand-alone data for building for spine 3.8)


(2 edits)

I'll check later. My foreign assistant can't download it yet. (I'm in Russia)

The only other thing I can think of is that anti-virus software is blocking the call.

I have collected my own and your animations at the same time inside your example project. I found that after the build, your json, atlas, png works, but at the same time it tries to detect my json, atlas, png from the outside. Maybe I need to know the exact json settings when exiting spine.

(2 edits)

If the data inside the binary is not called even though it is registered inside the binary, it is thought that there is a mismatch between the information required for the call and the information recorded inside the binary.

If you can provide us with an mfa and resource file that can confirm what is happening, we can conduct a deeper investigation.

Of course, we only need to be able to confirm the event, so the resources you use can be copyright-cleared.
(e.g. filled images, etc.)

(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.