The external library (d3dx9d_43.dll) is included at build time.
In order to be included, it must be placed in the following path
"C:\Program Files (x86)\Clickteam Fusion Developer 2.5\Data\Runtime\Unicode\d3dx9d_43.dll"
If it is working correctly, you only need to place it.
No special operations are required.
I think it has something to do with the previous problem of poor loading at startup.
On startup, I get.
"C:\Program Files (x86)\Clickteam Fusion Developer 2.5\d3dx9d_43.dll"
Basically, this should work, but this is the story of the failure to load it.
As in this case, I think the file in Runtime is not being read.
For example, maybe you don't have permission to access the file.
Maybe you could try running CF2.5 with administrator privileges or check the permissions to access the file (DLL) in question?
We have confirmed that it works in both versions, so I don't think it is a version difference.
(We did not make it to target a version).
From the fact that the DLL at startup was placed in the windows system folder and worked
It seems to me that the working directory at runtime has something to do with it.
I'll get back to you when I figure something out.
For example, if you build with UnPackEXE, you will find d3dx9d_43.dll in Modules.
This is because CF2.5 loads the DLL in "Runtime" at build time.
If there is no DLL in "Runtime", an error popup appears at build time.
(And I found a bug where the executable file output by UnPackEXE could not be started, but that's another story)
I have already encountered the lack of DLL in Runtime.I installed it forcibly, and this solved the problem. But the game eventually turns to external sources anyway. Placement in the catalog on (C:\Program Files (x86)\Clickteam Fusion 2.5\Data\Runtime) also did not bring a solution. Placing the DLL in C\Windows allows the project to work as well. But later it accesses the external directory anyway. It looks like there are no communication options left.
I checked UnPack builds the DLL into modules. But the game continues to search for an external resource the same way. It's desperation.
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)
