TickStory v0.8 RC1 GBPUSD M1 bug

[virtual001]

Hi..
I download all data 2007-2013 from dukacopy and generate fxt using TickStory v0.8 RC1.

I notice only GPUSD M1 is corrupted, and only able to be backtested from 2007-2008 (backtest stop here). I try M5 and its able to backtested 2007-20013
EURUSD work perfectly on M1. Please fix this.

[tickstory]

Hi virtual001,

Couple of questions for you to see if it's possible to reproduce the issue:

- What version of MT4 are you using?
- Are you using the Tickstory launcher to start MT4?
- If so, what is the size of your FXT file? I assume you're aware of the 2Gb limitation?
- Does v0.7 work correctly for you when you try the same export?
- Could you provide the exact dates you are exporting for and any additional settings (such as whether you are filtering for duplicate ticks).
- Does your backtest stop with an error and on which date does it stop?

Thanks for your assistance.

[jupp76]

I have the same problem. I though it is general with tickstory but it is only GBPUSD, I cant backtest it on every Time Frame.

- What version of MT4 are you using? 419
- Are you using the Tickstory launcher to start MT4? No, Birts Solution
- If so, what is the size of your FXT file? I assume you're aware of the 2Gb limitation? Yes, but using birts
- Does v0.7 work correctly for you when you try the same export? no
- Could you provide the exact dates you are exporting for and any additional settings (such as whether you are filtering for duplicate ticks). no filter, downloaded 2008-2013, all standard
- Does your backtest stop with an error and on which date does it stop? "invalid file" and "no data for testing"

thanks for a solution

[tickstory]

Hi jupp76,

Thanks for your further detail. Appreciate if you can update to a MT4 build that is supported by the Tickstory launcher such as 432. This will limit the number of variables in trying to identify the issue. A test of a smaller period on GPBUSD has unfortunately been able to yield the same problem so will need to work with you further to see if we can resolve it.

At this stage it is unlikely that this issue is specific to v0.8 so I have responded to your other post that seems to relate more closely to your issue.

http://www.tickstory.com/forum/viewtopi ... ef6c8#p324

Thanks!