Home >> Support Board

Support Board

Date/Time: Fri, 03 May 2024 17:46:58 +0000

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

[2020-12-21 02:32:43] Link To Thread - Link To Post [Go To First Post]
User791263 - Posts: 151
I run Win 7 Pro 64 bit on O/C'd 2500K, 16 Gig; There's no 64-bit fear or memory limits here. I'm not "incorrectly faulting 64-bit architecture", as you accuse. Many of us just don't want or need 64bit SC." I cited only a V2012 problem that will be in later versions. (You usually say your changes "could not cause problems"). No change you make should cause what worked perfectly before to quit[/u]! You are missing my factor of many delicate timing dependencies. me: V2012 32 bit "did not work at all for me: It went into constant recalculation, mostly locking SC." you: "There must be another cause for the issue. It could not have been this: [ <----- ] 'When studies in charts make references to other charts, Chartbook loading can be faster because recalculation due to tagging with changes in source charts, only occurs once all chart data is loaded among all charts. ...' " That change will behave the same in 64bit. You say "There must be some circular reference going on". There are critical tuned update intervals/timing issues as overlays funnel down through 30+ charts. You've not encountered many dependencies like this as a user, so how can you say that is not involved?. After long tuning of update intervals, I can't spend weeks debugging that for no good reason, since no reference affects my results, V1991. V2012 was not giving a "circular reference" message. The change just screwed up delicate timing. I don't need risk and extreme work. I've been through that before. You repeatedly told users during late 2019 and most of 2020 we could "keep using 32 bit". A new datafeed may not be exploited by old versions, but if V1981 - V2002 run with our broker feed, we don't care. Changes must #1) run better, 2) improve profitability. No later features do that better, for me. Able to run "at all" is absolute #1.. so I need V1991-2002. Not all users tell you problems and work that some changes caused. Please do what you told us. Maybe offer an optional datafeed module patch, or A rare new 32b study you say requires no different source code. Maybe charge V1981-V2026 users $10/mo. to support datafeed patches. I'd gladly pay $10 per month to not be forced, again, to upgrade for a couple of years.