Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 24 Apr 2024 17:10:47 +0000
Post From: Notice: Transact Websocket Connectivity Issue
| [2019-11-10 01:30:32] |
| |
|
Yes it is a Transact issue. The following message was sent to Transact earlier today: we continue to hear users who are having lagging problems and it looks poorly for us because they are not seeing the problem with your software and that would be because I think your software is still using the binary feed and using UDP from what I understand.
I think that providing market depth data in the JSON messages should be optional. And then we can give the user an option to turn off the depth. ,the SC chart will not display the entire move after catching up to match the Transact DOM displayed price, This is because after the send buffer on the Transact side, reaches a certain amount (We think 1 MB from memory), they just discard it. They did tell that to us. We told them instead they should close the connection and then when Sierra Chart reconnects, the missing data will be downloaded.so I have to delete the .scid file for that symbol and reload the chart to represent what had actually occurred.
You only need to follow the procedure here in this case:Historical Intraday Data (Missing Data / Download Errors / Viewing More Data): Retrying the Download When There is Data in the Chart 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-11-10 01:33:35
|