Bug in Tickstory HST generation

Report any bugs with the Tickstory Lite software here. Please give as much detail as possible so the issue can be identified and resolved as soon as possible.
Post Reply
RV13
Posts: 11
Joined: Thu Nov 20, 2014 7:31 am

Bug in Tickstory HST generation

Post by RV13 »

Steps to reproduce:
1. Use on Duskascopy data.
2. Right-click pair, click export to MT4, set adjust timezone to "UTC+2 with European/London DST". Export HST only
3. Check the resulting outcome on the last set of 180 bars. Counting from right (=bar 0 or bar 1), bars 180 to 120 are data from the last day selected (seems okay, though I have not checked the actual shift)
Bars 120-0 are data from the next day - i.e. 22:00 to 00:00 is missing for the last day selected, and 00:00-02:00 are data from somewhere else (it looks messy)

Please fix asap :)

RV13
Posts: 11
Joined: Thu Nov 20, 2014 7:31 am

Re: Serious bug in Tickstory

Post by RV13 »

The 00:00-02:00 data are the original non-shifted data from the next day 00:00-02:00

RV13
Posts: 11
Joined: Thu Nov 20, 2014 7:31 am

Re: Serious bug in Tickstory

Post by RV13 »

Ok, the first exported day has the same problem (22:00-00:00 missing). All the days in between seem fine

RV13
Posts: 11
Joined: Thu Nov 20, 2014 7:31 am

Re: Serious bug in Tickstory

Post by RV13 »

No, it's worse. The 30th of the month (in a month with 30 days) has the same issue, somewhere in the midst of the data. Very serious bug.

tickstory
Posts: 4900
Joined: Sun Jan 06, 2013 12:27 am

Re: Serious bug in Tickstory

Post by tickstory »

Hi RV13,

Could you please clarify what the issue is with a screenshot, please? Also:

- What time-frame are you working on?
- What charts are you looking at?
- What dates are you exporting?
- Are you filtering weekend information?

And any other information that may be useful for us to understand what issue you are coming across.

Thanks.

tickstory
Posts: 4900
Joined: Sun Jan 06, 2013 12:27 am

Re: Bug in Tickstory HST generation

Post by tickstory »

Hi RV13,

We assume that you have now resolved the issue. If not, could you kindly get back to us with the above-mentioned details?

Thanks.

Post Reply