Support Board
Date/Time: Sat, 18 Jan 2025 19:21:47 +0000
64-bit custom study automated file distribution
View Count: 1261
| [2018-02-26 07:29:56] |
| binaryduke - Posts: 375 |
|
@Sierra Chart Engineering Before 64-bit goes on full release, as there are 95% of users on 64-bit OS, would it make sense to change the naming convention so that a 32-bit DLL results in the name _32.dll and the 64-bit DLL carries no suffix. For users that transition to 64-bit without even being aware, this will mean that they have no need to edit their chartbooks to point to new 64 bit DLLs. |
| [2018-02-26 07:42:19] |
| |
|
This is not necessary because _64 is automatically added to the file name when loading the DLL. This is fully automatic. If this is not working properly do let us know though. The way this is intended to work is that users can move between the 32-bit and 64-bit version at will. And both 32-bit and 64-bit DLLs can and will be present. And the appropriate one will be loaded. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-02-26 07:43:18
|
| [2018-02-26 08:04:36] |
| binaryduke - Posts: 375 |
|
It's good to hear this is the design. I don't think the _64 file name appending is functional in the v1706 pre-release. Pleas prefer to the attached screenshots: test 1. showing a saved chartbook with 'missing' studies test 2. drilling down showing the DLL name (highlighted in red) that does not have _64 appended. |
 SC64bit_test1.png / V - Attached On 2018-02-26 08:04:07 UTC - Size: 209.69 KB - 319 views SC64bit_test2.png / V - Attached On 2018-02-26 08:04:14 UTC - Size: 284.71 KB - 318 views |
| [2018-02-26 08:13:27] |
| |
|
test 2. drilling down showing the DLL name (highlighted in red) that does not have _64 appended. Based upon what we see in the Message Log there is a problem with the filename. It looks like the filename is using 16-bit characters and that is the source of why the file cannot be loaded. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-02-26 09:56:43] |
| binaryduke - Posts: 375 |
|
OK. Both DLLs including the 32 bit referenced by the chartbook were built using your Remote Build and the dll filenames haven’t been edited so I’m at a bit of a loss as to how to resolve. All guidance appreciated.
|
| [2018-02-26 10:13:07] |
| |
|
Can you attach the 64-bit DLL here.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-02-26 10:46:59] |
| binaryduke - Posts: 375 |
|
It was uploaded this weekend via an account support ticket. Please could you reference it from that ticket.
|
| [2018-02-26 11:40:35] |
| binaryduke - Posts: 375 |
|
Now attached for speed.
|
Private File |
| [2018-02-26 15:09:08] |
| Zosimus - Posts: 345 |
|
binaryduke, I see the same problem on my side (see attached image). I may be mistaken but my understanding is that you will have to build the studies on a 64-bit Sierra in order to get a working 64-bit verison of the studies. When you build them on a 64-bit Sierra you will see the _64 added to the dll name. Unfortunately this means that your users will have to remove the 32-bit version of your custom studies from the chartbook and replace them with the 64-bit. Also my experience so far is that only the Remote Build creates the _64 dlls. The MS Visual C++ compiler that comes wirh Sierra doesn't seem to create them. I definitely hope I'm mistaken. |
| 64_bit_CustomStudies.png / V - Attached On 2018-02-26 15:08:09 UTC - Size: 83.41 KB - 307 views |
| [2018-02-26 15:20:42] |
| binaryduke - Posts: 375 |
|
Thanks Yon. My understanding from SC’s responses on this thread is that you’re mistaken. Everything should just drop through. I only use remote build.
|
| [2018-02-26 18:54:54] |
| |
|
When we tested this DLL you provided and we could not reproduce the problem but we did make some changes before the test. So not sure if that had anything to do with it. Possibly but it would seem like not. We will have a new release out later today and we want you to test again The MS Visual C++ compiler that comes wirh Sierra doesn't seem to create them. 64-bit compiling support will be added for the Visual C++ compiler in the next release.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-02-26 22:04:56] |
| |
|
It looks like the filename is using 16-bit characters and that is the source of why the file cannot be loaded. For the record this cannot be the case at all. We should not have even considered it.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-02-27 13:15:53] |
| Zosimus - Posts: 345 |
|
I'm on 1707 now. The Visual c++ compiler works fine and created a _64 version of the dlls BUT still the 64-bit Sierra doesn't automatically replace the 32-bit dlls that were applied to a chartbook with their new _64 versions (As you can see in the attached image). Is Sierra supposed to replace them automatically or do we have to manually replace all custom studies with their _64 version manually (after buiding them on 64-bit of course). |
| studies on 64-bit.PNG / V - Attached On 2018-02-27 13:14:53 UTC - Size: 48.74 KB - 328 views |
| [2018-02-27 18:58:39] |
| |
|
BUT still the 64-bit Sierra doesn't automatically replace the 32-bit dlls that were applied to a chartbook with their new _64 versions
We will do more testing on this and see why this is the case. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-02-27 19:08:23
|
| [2018-02-27 20:06:09] |
| binaryduke - Posts: 375 |
|
I have just updated to v1707 and recompiled the 64 bit DLL using Remote Build. Loading a chartbook from pre-64 bit gives the error message: Error loading Custom Studies DLL: (path and DLL name) Windows error code 194: %1 is not a valid Win32 application I can however successfully add studies from the newly compiled DLL (_64.dll filename) to a chartbook). Date Time Of Last Edit: 2018-02-27 20:06:59
|
| [2018-02-28 02:49:38] |
| |
|
This is now resolved and we will have a new release out in a few hours. It was a programming error on our part that we did not catch in our testing.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-02-28 04:52:30] |
| |
|
1708 is now released.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-02-28 08:06:23] |
| binaryduke - Posts: 375 |
|
Working well now in 1708.
|
| [2018-02-28 09:58:17] |
| Zosimus - Posts: 345 |
|
Yes working well on my side too.
|
To post a message in this thread, you need to log in with your Sierra Chart account: