Hi,
Yes, I am aware of the issue with Build 950, but I reverted and am currently using Build 910. Any thoughts on why it would be happening on Build 910?
Search found 5 matches
- Fri Feb 12, 2016 2:39 pm
- Forum: Issue/Bug tracking
- Topic: Spread not calculated -- using version 1.7.4 & Build 910
- Replies: 3
- Views: 10927
- Fri Feb 12, 2016 5:55 am
- Forum: Issue/Bug tracking
- Topic: Spread not calculated -- using version 1.7.4 & Build 910
- Replies: 3
- Views: 10927
Spread not calculated -- using version 1.7.4 & Build 910
Hi there, I am currently using Tickstory Version 1.7.4 and reverted MT4 back to Build 910 using the recommended steps discussed in the forum. I downloaded MT4 directly from the Metatrader website, and it is not connected to any broker. I deleted all existing historical data, so the only data that it...
- Tue Feb 09, 2016 5:29 pm
- Forum: General Discussion
- Topic: v1.7 Released!
- Replies: 146
- Views: 3180440
Re: v1.7 Released!
Hi,
I realized that the spread was "points" and not "pips", and I was entering a value of "2" when it should have been "20". So everything seems to be fine now.
Thanks!
I realized that the spread was "points" and not "pips", and I was entering a value of "2" when it should have been "20". So everything seems to be fine now.
Thanks!
- Sun Feb 07, 2016 6:16 am
- Forum: Issue/Bug tracking
- Topic: Extra historical data at tailend of backtest result
- Replies: 1
- Views: 6882
Extra historical data at tailend of backtest result
Hi, I recently purchased the Tickstory software. The version I have is 1.7.4. I am using MT4 build 910. I was running a 1-year backtest (2/2015 - 2/2016), and I noticed that at the tailend of the backtest result, there is some data that shouldn't belong there, namely some data from 2011 (4/14/2011 t...
- Sat Feb 06, 2016 11:18 pm
- Forum: General Discussion
- Topic: v1.7 Released!
- Replies: 146
- Views: 3180440
Re: v1.7 Released!
Hi, I recently purchased Tickstory and downloaded the most recent version (1.7.4). I am using Build 950, and everything works perfectly fine except for the workaround mentioned above. I see that the spread is applied on the Control Points method, but when I switch to the Every Tick method and check ...