[imported_tickstoryParticipant May 15, 2014 at 1:41 am Post count: 1479]

in reply to: Birts CSV2FXT format #20166

Hi Vinisius,

Most applications expect data in a specific format – for example, some require commas in-between field data and some expect tabs. Timestamps can also be formatted differently.

In the case of Generic format vs Birt’s CSV2FXT, the timestamp format actually differs since CSV2FXT expects it the date in yyyy.MM.dd format rather than yyyyMMdd. As such, you should use whatever format is appropriate for the application you are exporting to otherwise you will encounter errors.

Regards.

[imported_tickstoryParticipant May 14, 2014 at 4:30 am Post count: 1479]

in reply to: Backtests run only since 01.01.2013 #20152

You will need to experiment with ranges for each instrument, bearing in mind that each will have it’s own level of tick activity and therefore resultant file size. Keep reducing the date range for EURUSD by say 6 months until you find the working limit.

[imported_tickstoryParticipant May 14, 2014 at 1:47 am Post count: 1479]

in reply to: Backtests run only since 01.01.2013 #20150

Hi Render86,

The only known issues that we know of that causes the “n/a” issue is when the MT4 has not been launched via Tickstory or that the exported data is not being used by MT4 correctly. As such, you can check the following:

– That you have launched MT4 via the Tickstory ‘Launch’ function.
– That the exported data is in the correct data folder.
– If your MT4 symbol is different to that of the Tickstory named symbol (eg. EURUSDm in MT4 but EURUSD in Tickstory), that you have correctly used the ‘Maps To’ field.

If you have already checked these things, then the only other suggestion is to make a small 1-month export and see if that works. It could be that there are still unexpected issues when MT4 internally tries to process large files. If this is the case, you’ll need to reduce your exported range further until it gives the correct modelling quality (or keep working as-is with the potential of other issues occurring).

Regards.

[imported_tickstoryParticipant May 13, 2014 at 1:16 pm Post count: 1479]

in reply to: Error: tester cannot calculate prices #20075

Hi Adeller,

Thanks for your feedback. We’ve also confirmed that the Profit Calculation Mode=1 (CFD) should address this problem. Attached is a screenshot denoting the settings to change when setting up the DAX index for export. You will need to make similar parameter changes when dealing with other indices and commodities.

Regards.

[attachment=0:1c2a5tfl]exportscreen.jpg[/attachment:1c2a5tfl]

[imported_tickstoryParticipant May 13, 2014 at 1:04 pm Post count: 1479]

in reply to: TickInfoExpert #18532

Hi Mmsk,

It appears that the name of the file that Tickstory has chosen (which is based on your broker name) is too long and/or invalid. You can manually override the filename by going to the Tickstory EA parameters and set the “Config filename” parameter to “CapitalMarkets.mt4config” or the like.

Hope this helps.

[imported_tickstoryParticipant May 13, 2014 at 12:55 pm Post count: 1479]

in reply to: Error while saving settings #20165

Hi Digi88,

This error is unfortunately due to Windows restrictions. We will need to address the issue in a future version, however for now you can either:

1) Install Tickstory in a directory other than C:Program Files (x86) (eg. C:Programs) or
2) Run Tickstory as Administrator

We will let you know when this is resolved.

Thanks.

[imported_tickstoryParticipant May 13, 2014 at 12:51 pm Post count: 1479]

in reply to: "Cannot open [13, Permission denied]" error on backtest #20143

FYI, we have seen this error occur when Tickstory is still in the process of exporting to MT4. In such an event, waiting for the export to complete should resolve the issue. If you still get the error, the best course of action is to close any applications that may have the reported file open – including Tickstory – and then trying to commence the back-test again.

[imported_tickstoryParticipant May 13, 2014 at 1:33 am Post count: 1479]

in reply to: Prefix Suffix #20106

Hi Moralproxy,

In some cases the server is returning zero values whenever the broker connection is unavailable. In these cases, the Tickstory EA attempts to assume some values. In the case of Initial Margin, however, you are right that it should really be zero. We will update the EA accordingly.

Thanks.

[imported_tickstoryParticipant May 12, 2014 at 11:14 am Post count: 1479]

in reply to: Searching to Import INDICES and Commodities #19985

Hi Adeller,

As you’re aware, the “cannot calculate prices” issue is being discussed here:

viewtopic.php?f=4&t=450

Thanks.

[imported_tickstoryParticipant May 12, 2014 at 11:09 am Post count: 1479]

in reply to: Prefix Suffix #20104

Hi Moralproxy,

From the MT4 manual:

MODE_MARGININIT => Initial margin requirements for 1 lot
MODE_MARGINREQUIRED => Free margin required to open 1 lot for buying

These values are taken directly from the MarketInfo command.

The free-margin you highlighted in the screenshot is for the live/demo account – not for the back-tester.

Regards.

[imported_tickstoryParticipant May 12, 2014 at 12:31 am Post count: 1479]

in reply to: Error: tester cannot calculate prices #20073

Hi Adeller,

Profit calculation mode is set in the “MT4 Info” tab when the “Export to MT4” option is selected. We’re still not exactly sure what causes this error in MT4 so if you do find a solution, please let us know.

Thanks.

[imported_tickstoryParticipant May 10, 2014 at 11:20 pm Post count: 1479]

in reply to: [BUG] Gaps when export on Tickstory v1.5! #20118

Hi Rodrigo,

Could you kindly provide us with the exact steps and parameters you are using for the export to see if we can firstly reproduce your issue?

With regard to remote support, we don’t typically provide this – what did you have in mind?

Thanks.

[imported_tickstoryParticipant May 10, 2014 at 11:07 pm Post count: 1479]

in reply to: Bad Export ?? #20133

Hi Breunig,

On your File export, make sure you set your ‘Timeframe’ to ‘Tick’ if you want the bid/ask values to come out. Bid and ask fields are only valid in this time-frame. If you are exporting Bars (such as 15 minute candles) then Bid/Ask will not work – only Open, High, Low and Close prices.

Hope this helps.

[imported_tickstoryParticipant May 10, 2014 at 10:34 pm Post count: 1479]

in reply to: TickStory VS Forward Test #20111

Hi Tradexfol,

If you have some more details of the differences you are seeing then appreciate if you could describe them. Obviously if there is some way which we can improve the back-testing experience via Tickstory we would look at it. The main known issue at the moment is with spread-sensitive EAs. If your EA is highly dependent on spread – that is, it is a scalper or it only opens a trade under certain spread conditions – then back-testing with a fixed spread will invariably affect results. The best way to determine if your EA is highly spread sensitive is by back-testing with a few different fixed spread values and seeing how dramatic the differences are.

The other issue may be the broker data feed. Tickstory is using Dukascopy tick data, whereas your broker may differ in some way – timing/latency, frequency, price, etc. This will also impact your back-test vs live results if your EA is sensitive to these variables.

Other than that, maybe some other users can share their experiences with the EAs they have tested with.

Regards.

[imported_tickstoryParticipant May 10, 2014 at 10:02 pm Post count: 1479]

in reply to: Backtests run only since 01.01.2013 #20148

We have tested the Tickstory launcher on Build 646 and it appears to be working correctly. We have no other known cause of the issue you have described aside from the FXT file being over 4gb. If you have selected the correct Data Folder in Tickstory and MT4 (and set your Launcher settings to have the ‘/portable” parameter if appropriate), then this shouldnt be the cause of any issues between versions.

[Author]

Posts