May I ask a technical question – due to the changes and the new function coming with b600+. I have to point out though that I am deeply impressed with the tickstory product and am looking forward to future releases and updates. Hope this post a) helps to clarify things and b) causes tickstory amend the exporting to MT4
The main problem I see is that the way the current exporting from tickstory to MT4 works breaks the backtesting results of an EA that wants to trade only at the first tick of a new bar (earliest possible point after completion of the previous bar) with the EA detecting such first tick of a bar via the condition: “Volume = 1” Ideally, an EA that counts each tick internally (counting up a global variable each time the start function gets called in MTD) and also displays the result of the MQL4 function Volume should show that they are in line while first Bar is being formed.
changing if someone filters duplicate ticks) in a Bar? Question: Can the generation of the HST files be adjusted so that Volume represents the number of ticks (consistent to the FXT file, i.e. This can be seen in MT4 History Center after launching MT4 out of tickstory: if the “Suppress Volume Info” option is selected when exporting to MT4, all HST files show a volume of 1 per Bar and if the “Suppress Volume Info” option is deselected the HST files show some non-interger number (sum of Bid and Ask Size from Dukas in Mio) which does not match the way MT4 works. The volume as number of ticks per bar does not seem to be supported by tickstory (v 1.0) at this point when generating and exporting HST files. It seems that gooly was referring to the second definition. I believe there is a confusion about the term ‘Volume’ here.Īs I understand it, the volume coming from Dukascopy represents the size of the Bid or Ask in millions of the quoted currency while the function VOLUME in MT4 counts the number of ticks in a bar.