Tickstory

Hi thomas, The "no data for testing" error is usually caused by 2 things - either: 1) You have not launched your Metatrader terminal via Tickstory (by pressing F8) or; 2) You have not mapped your instrument symbol correctly to your Metatrader terminal. If this is the case, this post should help you:...

Hi colbygray, This issue is usually caused by not launching your Metatrader terminal with Tickstory (by pressing F8). Please re-generate your MT4 export and ensure you launch via Tickstory before commencing your back-test. A more detailed description of the back-testing steps is in the help manual (...

Hi coffeesnob, Thanks very much for your encouraging feedback. Regarding the download process, the idea behind utilising/downloading the latest Dukascopy format is to captialise on the significant disk space savings (in some cases the data is 75% smaller). Once you have performed the download once, ...

Hi Ilias, Thanks for your post and feedback. The xx_1.fxt and xx_2.fxt data files are created when back-testing with the "crude" and "open price" models. These modes are significantly inferior to tick-based back-testing and are not supported by Tickstory. If you wish to get a rudimentary idea of how...

When back-testing on a 4-digit Metatrader 4 terminal, users could encounter the following error: OrderSend error 4107 Error opening BUYSTOP order []: (4107) invalid price parameter for trade function invalid price 1.28236000 for OrderSend function You can resolve the issue by either: - Modifying you...

Hi Paul,

Thanks very much for your suggestion - this feature has been noted and is currently in development.

Regards.

Hi fxchess,

This is most likely due to your FXT file being greater than 2GB. At the moment does not support this, so you have 2 choices:

- Break your back-test down into say yearly exports.
- Use Tick Data Suite (a third-party product) which supports > 2GB FXT files.

Hope this helps.

Excellent news - thanks for letting us know how you solved it.
Have fun back-testing!

Hi m8se, Thanks for the further detail. Sorry, I forgot to mention that the specific version of .NET required is v3.5. Could you please install this and try again. The setup.exe installation should be checking for this version and prompt you. If it isn't, then can you please try install .NET v3.5 ma...

Hi m8se, Thanks for raising your issue. Tickstory has the ability to detect any unhandled errors and display it's own detailed error message to trouble-shoot the issue. When you get the MS crash window, it usually means something fundamental is missing and/or corrupted such as the .NET installation....