Support Board
Date/Time: Wed, 11 Nov 2026 18:15:52 +0000
Post From: Setting study DLL module function objects to indicate DLL is not loaded
| [2026-09-25 04:13:32] |
| User153286 - Posts: 73 |
|
Possible solution: Another point of interest, my charts are complex. I use my custom studies and I also use a lot of the utility type studies you provide allowing me to build output on the chart based on other studies and bar data in the chart. I typically have 5 charts up across 4 monitors. This may or may not be part of the issue but in hindsight I thought the complexity may be involved in the problem. The real problem is I do not see the just successfully compiled study in the custom study UI, yet the DLL is in the appropriate folder with the magically applied _64 in the name. Here are the messages I see in the Message View when this issue occurs for a specific study: 2026-09-24 17:06:05.085 | Setting study DLL module function objects to indicate DLL is not loaded: C:\SierraChart\Data\TestDLL.dll 2026-09-24 17:06:05.085 | Study DLL module not found for: C:\SierraChart\Data\TestDLL.dll Previously I was doing my AI research on the 2nd message which was/is "Study DLL module not found for: C:\SierraChart\Data\TestDLL.dll" I find it very weird that SC somehow magically adds the _64 to the DLL name, yet it appears to attempt to load the non_64 version instead as listed as for example seen in the "Study DLL module not found for: C:\SierraChart\Data\TestDLL.dll" message. But, if I rename that DLL, manually removing the _64 from the name, everything works. So be it, overcoming or accepting weirdness is part of development. I then considered that perhaps the 2nd message is just an artifact of the real problem. So I changed the AI research to focus on the 1st message which is "Setting study DLL module function objects to indicate DLL is not loaded". The updated AI research came back with this: if one is creating, adding, updating basically mucking with custom studies, try these 3 steps if you encounter the "Setting study DLL module function objects to indicate DLL is not loaded" message. Step 1: Check File Locations Step 2: Click on Allow Load DLLs Step 3: Recalculate Chart Step 1 I have done and verified numerous times. The file locations are correct, source is where it should be and DLLs are uploaded to where they should be from the Remote Build process. Step 2 was new to me. I read up on Analysis-> Build Custom Studies DLL -> Build -> Allow Load DLLs I believe this is an internal magical SC process that runs when clicked on and is global in nature. I do not really see anything happen, it just seemingly does it's magic. Not certain if it only processes the selected file in the Build UI or not. It just quietly does what it does in the background. Step 3 raised other questions for me. I have been reloading charts to pickup UI changes in updated studies. AI research indicated to only use "Recalculate Chart" from the Chart Menu in the affected chart when this issue occurs. But being global in nature and in hindsight I do not think it really matters what chart "Recalculate Chart" is invoked from. Only doing "Recalculate Chart" seemed to be the required final step that resolved the issue. After doing these 3 steps with TestDLL, the TestDLL study magically appeared in Custom Studies UI. Why this issue occurs with some studies and not others is a completely different question, perhaps you have some ideas why? As I initially indicated, I provided TestDLL just to send in example study code. I have since applied the 3 steps to a real study I have been working on that initially ran into this issue. I had already run the 3 steps for TestDLL so I thought it might apply to my real study too, but after a recompile of the real study to re-create it's _64.dll file, the real study did not appear in the Custom Study UI and the 2 signature messages for this issue appeared in the message log. So I repeated Step 2 and then Step 3 and wala the real study appeared in the UI. This whole experience/process seems very weird to me but it thus far works for my environment. Even more strange is that this issue does not seem to happen for all custom studies, just the lucky ones I guess. |