[render86Participant January 3, 2014 at 1:57 am Post count: 51]

in reply to: History issue #19551

@tickstory wrote:

I can imagine that you may well get this response. Metatrader 4 is not designed for the sort of high-end tick-level back-testing that Tickstory tries to facilitate and as a result, some compromises are necessary if you want to obtain tick-accurate back-tests. If you were to source your back-test data from the “official” data sources you will note that the most granular you will get is 1-minute data points – a comparitively small amount of data to the volume of tick data that Tickstory can export.

Given that MT4 is built on handling at-best 1-minute data, MT4 developers have assumed a maximum size for how large the historical data file can be – initially this was 2GB but may have been extended recently to 4GB. Of course, when you’re dealing with 1-minute quotes, it is a very reasonable assumption that your FXT file will be well within the limit – 7 years of 1-minute data, for example, would produce approximately a 200MB FXT file. This is obviously not the case for tick data which is much more voluminous.

Here are some further discussions on the topic that I believe have already been raised with Metaquotes:

http://www.mql5.com/en/forum/6687
http://forum.mql4.com/54343

Regards.

I’ll be honest with you: your standpoint about the FXT file size limit being exceeded just doesn’t make any sense to me. First, I can successfully run EURUSD backtests starting as early as 01.01.2008 until 07.06.2013. That would sure mean the FXT file size limit is not exceeded, wouldn’t it? But then all I do is simply change the backtest’s starting date from 01.01.2008 to 01.02.2009 in the MT4 strategy tester. I don’t download the history again or do anything else. Just change the starting date in the MT4 strategy tester. That’s it. Yet the backtest would not run since that date (01.02.2009). It instead runs since 23.07.2012. How could the FXT file size increase as a result of me merely changing the backtest’s starting date in the MT4 strategy tester?

[render86Participant January 3, 2014 at 12:03 am Post count: 51]

in reply to: History issue #19540

@tickstory wrote:

As mentioned, we are not privy to the inner workings of MT4 nor can we help if there is an issue/limitation in MT4 itself. We could obviously assist further if there was a bug in the Tickstory software but this does not appear to be the case. Our best recommendation is to ensure you work within the MT4 limitations. The FXT file size limit is a well-documented problem which is discussed regularly on MT4 forums and if you need further information, other MT4 users may be able to shed more light on the problem you are having.

Hope this helps.

What is this specific MT4 limitation? I can contact MetaQuotes like I did on multiple occasions in the past and ask them to fix it. But I need a detailed description/justification that the problem is indeed on their end. Else, their underpaid customer service representative will take a similar convenience of putting all blame on Tickstory.

[render86Participant January 2, 2014 at 11:27 pm Post count: 51]

in reply to: History issue #19548

@tickstory wrote:

I doubt it as this makes no difference to the size of the FXT file. You can reduce the size of the FXT file somewhat by checking the “Filter duplicate ticks” option in the MT4 Export window. Of course, you should only use this option if you know your EA wont be affected by the filtering of this data (eg. some scalper EAs could have their back-test results affected if they are dependent on price action/activity).

Regards.

I always have the “Filter duplicate ticks” checked. Have you tried to reproduce the issue I am experiencing?

[render86Participant January 2, 2014 at 11:12 pm Post count: 51]

in reply to: History issue #19546

@tickstory wrote:

The Metatrader FXT file size remains the same once you have finished exporting the data from Tickstory. It could be that the behaviour you’re seeing is a result of MT4 trying to find the date you specify by locating an offset within the file and this number is sometimes too large to handle.

Hope this helps.

Should re-downloading the history with GMT offset 0 help?

[render86Participant January 2, 2014 at 11:04 am Post count: 51]

in reply to: History issue #19544

@tickstory wrote:

Hi Render86,

Is your FXT file larger than the maximum size? If so, please try reducing the size of it and see if it eliminates the issue for you. Given that we are not privy to the internals of MT4, we can only suggest workarounds to any issues you are experiencing.

Thanks.

Could the FXT file size somehow change after I set a later (not earlier) starting date for the backtest without downloading the historical data again?

[render86Participant January 2, 2014 at 3:57 am Post count: 51]

in reply to: History issue #19541

@tickstory wrote:

Hi Render86,

It is more than likely you are coming across the FXT size limitation that MT4 has. See this post for details:

viewtopic.php?f=4&t=202

Regards.

How was it then possible for me first to be able to run the backtests since 01.01.2008 until 07.06.2013 just fine yet be unable to run backtests since 01.02.2009 until 07.06.2013?

[render86Participant November 6, 2013 at 12:25 am Post count: 51]

in reply to: ‘Access to the path is denied’ #19439

For a record, I am using Windows 8.

[render86Participant October 4, 2013 at 11:09 pm Post count: 51]

in reply to: Issue with leverage #19314

@tickstory wrote:

Hi Render,

Are you able to manually edit this value? We will add an item to automatically calculate this in the future, however for the moment it is user-specified.

Thanks.

No, I am not, as the EUR price constantly changes throughout the backtest period.

[render86Participant October 2, 2013 at 9:09 pm Post count: 51]

in reply to: Issue with leverage #19312

@tickstory wrote:

Hi Render86,

Could you provide the parameters/code that demonstrates which exported values do not match up with what you expect? The only control the export has is the specific values embedded in the FXT file as shown int he ‘MT4 Info’ tab – after that, you will need to consult the MQL manual for how to perform your lot calculation.

Thanks.

The MT4 tester, following the hack by your program, issues a wrong number in response to the query MarketInfo(EURUSD, MODE_MARGINREQUIRED)). For EURUSD, the lot price (100000 EUR) should depend on the Euro’s current price (136000 as of now) while with Tickstory, MT4 issues 100000.

[render86Participant September 20, 2013 at 10:25 am Post count: 51]

in reply to: Issue with leverage #19310

@tickstory wrote:

Hi render86,

We were unable to reproduce any issue with leverage using the following steps:

1) Select ‘Export to MT4’ on EURUSD.
2) In the Mt4 Export window, select Metatrader Info tab and specify the Account Leverage to be 200.
3) Press OK and wait for it to complete.
4) Launch Metatrader by pressing F8 in Tickstory.
5) Run MACD Sample with the following line of code inserted into the start() function:

Print(“Acc lev: ” + DoubleToStr(AccountLeverage(), 5));

6) Account leverage correctly reports that leverage is 200.

Hope this helps.

Kindly refer to the clarification in my second post. I don’t mean the Leverage but MarginRequired which is given incorrectly in USD as base currency.

[render86Participant September 19, 2013 at 11:56 am Post count: 51]

in reply to: Issue with leverage #19308

Here’s more info on the problem: with Tickstory, MetaTrader4 gives incorrect margin. E.g. instead of 128000 in April 2013 for EURUSD (when the EURUSD price was around 1.28), the margin is 100000. This distorts the lot size of the EAs tested.

[render86Participant July 5, 2013 at 7:27 pm Post count: 51]

in reply to: v0.9 Released! #18882

@tickstory wrote:

Hi render,

Do you happen to have any popup blockers installed? Is Javascript enabled on your web-browser settings?
Another user has reported that having Chrome as their default browser caused some issues.

Can you please follow-up in this topic as it will possibly assist other users:

viewtopic.php?f=4&t=204

Thanks.

Yes, I do too have Chrome as my default browser. Will switch to Internet Explorer and let you know if this helps.

[render86Participant July 4, 2013 at 7:38 pm Post count: 51]

in reply to: v0.9 Released! #18880

@radu wrote:

@render86 wrote:

Tried it but the problem persists. After I hit the Like button, the Tickstory window simply freezes for a moment, then unfreezes, yet no like is credited and no MT4 build 500+ is accessible (same old unsupported error window pops up upon hitting F8).

Do you have Internet Explorer enabled on your Windows? You don’t have to use it for browsing, but TickStory Lite uses IE engine. After the click a popup window should appear, with the Facebook login screen.

Yes, I have Internet Explorer enabled yet no pop-up window opens.

[render86Participant July 4, 2013 at 3:46 pm Post count: 51]

in reply to: v0.9 Released! #18878

@radu wrote:

@render86 wrote:

I still cannot run the latest version of Tickstory with MT4 build 509 despite claims of it supporting build 500+.

Please read the previous post carefully! You have to “Like” TickStory, and the 500+ launcher will be available then. Click here

Tried it but the problem persists. After I hit the Like button, the Tickstory window simply freezes for a moment, then unfreezes, yet no like is credited and no MT4 build 500+ is accessible (same old unsupported error window pops up upon hitting F8).

[render86Participant July 4, 2013 at 6:31 am Post count: 51]

in reply to: v0.9 Released! #18876

I still cannot run the latest version of Tickstory with MT4 build 509 despite claims of it supporting build 500+. I keep getting the same error message as with the previous version. Attached are my screenshots illustrating my experience.

[Author]

Posts