Support Board
Date/Time: Tue, 21 Apr 2026 23:35:01 +0000
Custom ACSIL .cpp files not appearing in Remote Build file list
View Count: 44
| [2026-04-21 12:36:20] |
| User368639 - Posts: 55 |
|
I have .cpp files placed in C:\SierraChart\ACS_Source\ that do not appear in the Remote Build Standard file list, even after clicking Refresh. Facts: I have been using Claude ai to construct some special studies. Excellent results until we hit this brick wall. This and all other newly constructed tools work perfectly on my Local Desktop. This came about when we tried to transfer .cpp files from the Desktop to QuantVPS. The latest files in the Build List in the VPS are from 01-23-2023, which seems strange. Files are confirmed present in ACS_Source via Windows Explorer and PowerShell File extensions are correct (.cpp, single extension, no doubles) Line endings are Windows CRLF SC version 2891 Other stock SC example files in the same folder appear normally in the Remote Build list Our custom files have never appeared in the Remote Build list despite weeks of attempts The specific file is Arts_EBO_Detector_FINAL.cpp. What determines whether a .cpp file appears in the Remote Build file list? Is there a file attribute, header requirement, or registration step we are missing? Thank you. |
| [2026-04-21 19:22:53] |
| Sierra_Chart Engineering - Posts: 23588 |
|
What file list are you referring to? This is not clear to us how are you getting to this file list. What is the title of this list?
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-04-21 20:41:03] |
| User368639 - Posts: 55 |
|
Analysis > Build Advanced Custom Studies > Remote Build - Standard > Select Files, which when clicked shows a path of C:SierraChart\ACS_Source\. At the bottom of that screen there are two fields: File Name*.cpp and below that: File Type: Advanced Custom Studies Files (*.cpp: *.h). See screenshot below. The 38 studies/files in the existing list from two days: from 2026-01-23 and 2026-04-21 and include ADSIL CustomChartBars_Example.cpp, ACSILDepthBars.h, ADSILSpreadsheetInteraction.cpp, AutomatedTradeManagementBySubgraph.cpp, CandleStickPatternNames.cpp, CandlestickPatternNames.h, OrderEntryStudies.cpp, etc. Historically, the only files that show up are the .cpp files we have been working on, not "stuff" that has been created by SierraChart. The following methodology is how we have built several different tools/Special Studies: Claude ai constructs the code, provides me with a download button, I download the .cpp file, I copy it and place it in C:\SierraChart\ACS_Source\. I then go to what is written in the first paragraph of this message and the .cpp file is found and the Build is executed. When the build shows Complete with no errors, the new study then shows up in the Add Custom Study folder as a .dll file. We have the file, which was built on my local desktop machine and is listed in the Special Studies list as .dll files on that machine. The .cpp file is in the VPS Source folder, but we cannot get it to move into the Advanced Custom Studies files list, even though the path is C:\SierraChart\ACS_Source\. https://app.screencast.com/EIExlAhtfRsBm Thank you. |
| [2026-04-21 20:51:30] |
| John - SC Support - Posts: 45720 |
|
You have the sorting for the "Select Advanced Custom Study File" window set to "Modifed Date-Time" with the oldest on top. Therefore, you need to scroll down in the list to find your file named "Arts_EBO_Detector_FINAL.cpp". Did you scroll down to see if you could find your file further down in the list? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: