Home >> Support Board

Support Board

Date/Time: Sat, 27 Apr 2024 13:45:24 +0000

How to Post a Message for Support

32-bit Builds of Sierra Chart to be Discontinued with Newer Versions

View Count: 9794

[2019-05-31 15:28:02] #25 [Go To First Post]
opci - Posts: 90
I know this is my study that has been working for 5 years ... but why not work on the 1926 version of 32 bit? thank you

[2019-05-31 15:38:19] #26 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The reason for this is because it was compiled with version 1224 or earlier. Refer to: Notice: Studies Compiled With Version 1224 And Lower Will Need To Be Recompiled 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: 2019-05-31 15:53:24

[2019-06-13 22:04:09] #27 [Go To First Post]
User931283 - Posts: 55
Just please keep old Versions.. circa 1480 .. working and available. Some of us are Stuck there, and they are fast. Our concern is more ... market data feeds lagging .. even by seconds.. more than micro-second resolution. Market data feed (CQG-FIX) today seemed lagging seconds on Time-Sales. Such is crucial, .. even fatal to trading. Is there a lag alarm study that will work in old versions? Showing milliseconds lag (from system time), going from yellow (warning) to red (over 1 second) would be great.

[2019-06-13 23:00:06] #28 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
and they are fast. Actually the fact is the newer versions are faster. There is considerable performance improvements which have been made. Newer versions are faster in so many areas. Significantly faster. Especially on newer hardware. Older versions are slower. We know this definitively. The idea that an older version is faster is nonsense. And once we release the OpenGL support, and that becomes stable, if performance is important to you, there would be no reason to be using any other old version. Please consider using the Sierra Chart Exchange Data Feed if you have any lagging problems with other feeds: Sierra Chart Exchange Data Feed You also have the ability to control the number of levels of depth: https://www.sierrachart.com/index.php?page=doc/DataSourceSettings.php#MaxDepthLevels Also we do expect by 2020 1480 will be discontinued. 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

[2019-06-14 01:08:44] #29 [Go To First Post]
User931283 - Posts: 55
Good idea. I may need to convert to Sierra Exchange Data feed. I don't use levels of depth- can't on this large system. (I use a lean instance (also on another PC) to confirm no lag in large instance below) As to "there would be no reason to be using any other old version", around V1490 you made a small change that affected overlayed spreadsheets into other spreadsheets resulting in shifted columns of 2 or 3 studies (3 Bar Break, VolbyPrice (etc). Big complex formulas are destroyed by any column shift. You suggested I convert it to express columns (standard fix). Not possible. This hierarchy of 55 charts, about 2600 studies and 19 spreadsheets can not be rewritten without many months of work. It runs fine in real time. A key feature of Sierra Chart to me and many was allowing staying on older versions a long time. I need to run V1488 at least 2 - 3 more years. Please keep us in mind to hold on through 2020. Date Time Of Last Edit: 2019-06-14 01:28:37

[2019-06-19 22:45:15] #30 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Regarding post #29, refer to: User Question \| Post: 172763 What we recommend you start to do at this time is install another copy of Sierra Chart which is a copy of your existing installation. You can find instructions here for this: Transferring Sierra Chart Settings and Data From Existing Installation to New Installation Begin to modify your formulas to the new format: Working with Spreadsheets: References to Study Subgraph Columns when using the Spreadsheet Study It does not seem like that should take months. Also take advantage of the new Inputs we have described in the link above. 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: 2019-07-22 09:57:55

[2019-09-25 11:32:55] #31 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Effective after October 1, newer versions of Sierra Chart will not be built as 32-bit. Only 64-bit. Older versions will still be available to use. 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

[2019-09-27 13:13:17] #32 [Go To First Post]
User931283 - Posts: 55
Using an older version that requires months to revise is working well so far-- by your work-around: A slim latest-release trade orders version acts also as Data Server to the older version in a separate folder. Hopefully that will keep feeding the old version (1488) when pre-Vers 1973 are obsoleted for CQG clients in October due to CQG protocols/ feed change requirements.

[2019-09-30 13:26:29] #33 [Go To First Post]
User316362 - Posts: 210
What is the "last" release number of the 32-bit Sierra Charts?

[2019-09-30 18:25:54] #34 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
There is no last release yet. We expect will be sometime in October. 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

[2019-10-10 17:10:47] #35 [Go To First Post]
Mattthespaniard - Posts: 41
I have just checked and seem to be part of the small minority using the 32 bit version. Can you guys confirm I can simply run the 64-bits executable and don't need to touch anything else and SC will work just like so far ? I don't want to mess anything up. I inform that I'm not using any custom studies or stuff like that.

[2019-10-10 18:51:36] #36 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Many users run the 32-bit version just because this is historically how Sierra Chart has been but you are running a 64-bit version of Windows . So yes you can easily use the 64-bit version. You are not going to have any problem. Just run the 64-bit version and everything remains the same. 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: 2019-10-10 18:51:43

[2019-10-11 16:07:04] #37 [Go To First Post]
User972768 - Posts: 166
The only caveat here for people running Custom Studies is to have 64-bit version of the DLL. If you run 32-bit version of Sierra with Custom Study(ies) in 32-bit DLL, make sure to acquire 64-bit version of the DLL before switching over.

[2019-10-11 19:15:28] #38 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Yes that is true. 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

[2019-12-04 18:04:26] #39 [Go To First Post]
User472520 - Posts: 7
Furthermore, the plan to discontinue the 32-bit version will also discontinue support for the "Use Excel" option in the Spreadsheet study. If you need to have a direct interface to Microsoft Excel, you will need to use a version of Sierra Chart prior to this. The built-in Sierra Chart spreadsheets will continue to be fully functional. Nothing will change in that regard. (We will hold off on removing Microsoft Excel support until 2020) Could you kindly recommend the last 32-bit/64-bit version that had the "Use Excel" option in the spreadsheet study so as to "rollback" to it? Date Time Of Last Edit: 2019-12-05 13:34:14

[2019-12-05 14:31:48] #40 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Regarding Excel support, use version 2012 or earlier. 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: 2019-12-05 14:34:22

[2019-12-09 18:43:01] #41 [Go To First Post]
User96296 - Posts: 28
It seems that 64-bit sound alert {sc.PlaySound(1) or PlaySound (from winmm.lib)} cause memory leaks and crashes. Crash happens after alert sound played many dozen times with 64-bit SC running and some usage of crome or firefox. Maybe issue is from Windows 10 (64-bit winmm.lib for PlaySound). I tried for two weeks and am back to 32-bit version which is fine.

[2019-12-10 14:02:52] #42 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
This is going to be an operating system level issue. This is something that would need to be resolved by Microsoft. 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

[2019-12-11 19:02:00] #43 [Go To First Post]
User96296 - Posts: 28
32-bit had the same issue (PlaySound) just with much much less frequency. I realized now that crashes were more of monitor screen crash (part or all 3 screens black out). I could still hear the sound out of SC from inside PC main case instead of usual build-in speaker inside monitor. As if the monitors died. I had to physically button off the PC. Instead of 32 vs. 64 bit issue, could monitor crash come from beta openGL? Build-in speaker in monitor uses my very limited video memory. I'll change my sound to PC speaker instead of monitor speaker.

[2019-12-11 22:30:51] #44 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Yes if you are using OpenGL disable that option to rule it out: Graphics Settings: Use OpenGL for Chart Graphics (Global Settings >> Graphics Settings >> Other) 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

[2019-12-22 03:59:27] #45 [Go To First Post]
FFTrader - Posts: 180
I have the custom study MAMA source code file (see attached). However, I am not sure if it is the one Sierra Chart has in under "Custom Studies" nor am I aware as to whether the one currently under Custom Studies will migrate flawlessly. Caveat is that I have been using the 64 bit version (currently version 2028) without any issue for the longest time. If nothing else, can you put the current MAMA from the Custom Studies section into the non-custom study section, please? Again, as it is in the custom studies section, there is no issue with the 64 bit version that I am aware of.


Private File Attachment Deleted.

[2019-12-22 07:28:18] #46 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We can do this. But what does MAMA stand for? 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: 2019-12-22 07:28:26

[2019-12-24 00:30:42] #47 [Go To First Post]
FFTrader - Posts: 180
But what does MAMA stand for? Better let the inventor explain it: https://www.mesasoftware.com/papers/MAMA.pdf

[2019-12-30 19:10:18] #48 [Go To First Post]
WarEagle - Posts: 70
I am not really sure how to ask this question as I am not completely certain what needs to be done. Hopefully this makes sense. I wrote a custom indicator set years ago and compiled it in Visual Studio 2013. It relies on some third party C code functions that I was able to compile into a 32 bit dll at the time. I can not get it to compile with the built in Sierra VC++ compiler (linker errors) so I continue to use VS whenever I make a code alteration. This has served me well but its 32 bit. I am not a formally trained programmer so I don't know how to convert it to 64 bit. It took me a year to get the first version working. I do not recall how to create a dll from scratch in VS to work with Sierra and the instructions I used for configuring VS for this are no longer in the Sierra documentation. Is this information still available? Hopefully if I start from scratch with a new 64 bit Visual Studio dll project I can get it to build without errors. Just like everyone else, this is crucial to my trading so I appreciate any help.

[2019-12-31 05:34:40] #49 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
You can certainly continue to use the 32-bit version of Sierra Chart. After January 15 there should not be any need to update anytime soon. Do you have the source code for this?: some third party C code functions 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: 2019-12-31 05:34:54

[2019-12-31 13:06:43] #50 [Go To First Post]
WarEagle - Posts: 70
Do you have the source code for this? Yes I have the code. I am attempting to rebuild it in VS 2019. I was able to build a generic 64 bit dll that runs in Sierra so I think I have the main settings correct now. When I #include the external functions they show up in the intellesense information but I get the same errors as the VC++ build through Sierra gives me (unresolved external symbols). All the code is there so its probably something I am doing wrong linking it all together. I will keep working on it but thanks for allowing a 32 bit version to be available for now. EDIT: I think I figured it out, just needed to place the correct source files in the right place. The problem of being a trader and not a programmer. Thanks for a great product that I can even do this with. Date Time Of Last Edit: 2019-12-31 13:29:34

To post a message in this thread, you need to log in with your Sierra Chart account: