[imported_tickstoryParticipant September 11, 2015 at 1:47 pm Post count: 1479]

in reply to: Modelling quality problems with v1.7 #21104

Great news, Romanzif!

[imported_tickstoryParticipant September 11, 2015 at 12:37 am Post count: 1479]

in reply to: Add Button Save as Default #21002

Hi Rever27,

Thanks for your suggestion – it has been noted.

Regards.

[imported_tickstoryParticipant September 11, 2015 at 12:32 am Post count: 1479]

in reply to: Which is faster: Download or export? #21114

Hi Cullo,

If you are exporting, it is best to just use the “Export” function as it downloads and exports in a single step. The “download” function is primarily used when back-filling or verifying existing data. You can obviously use the “Download” function if you want to merely pre-download the data to your PC for subsequent use at a later time.

And yes, you can copy the FXT files to the Data Folder of another MT4 instance.

Hope this helps.

[imported_tickstoryParticipant September 11, 2015 at 12:29 am Post count: 1479]

in reply to: Error when saving MT4 Default settings #21111

Hi Danchik,

Thanks for mentioning the issue with the “save as defaults”. It looks like this might be related to not having sufficient permissions to write to the file. Are you able to confirm this by running Tickstory as ‘Administrator’ and see if the problem is resolved? If so, we will raise a tracking item to resolve it.

Regarding your question about the data going missing (?). Some questions:

1) Are you referring to the FXT or HST files? Presumably FXT if they are that large. Can you please confirm they were marked as “read-only”?
2) Are you connected to your broker?

Thanks.

[imported_tickstoryParticipant September 11, 2015 at 12:24 am Post count: 1479]

in reply to: Suggestion for creating a general reference procedure #21105

Hi Danny,

Many thanks for the feedback. Can you explain what you mean by “reference routine”? Are you suggesting that the data be checked for data gaps or something else?
Re: The MT4 fields, we are working on a grid which should give more information and hopefully simplify the process of setting the correct information (commission, for example, will be translated to more recognisable options such as “Charge Per trade” rather than zeros and ones). Bear in mind that MT4 doesn’t officially document any of this so we need to be wary that things might change without notice.

Regards.

[imported_tickstoryParticipant September 11, 2015 at 12:13 am Post count: 1479]

in reply to: Symbol Setting Error #21090

Hi Worker – FXT files are binary not editable in a normal text editor. Tickstory provides the FXT editor tool. Just go to Tools->MT4 Data Editor in the Tickstory menu. Further information can be found in the manual under the section “Exporting to Metatrader: MT4 Data Editor”.

Regards.

[imported_tickstoryParticipant September 11, 2015 at 12:09 am Post count: 1479]

in reply to: Modelling quality problems with v1.7 #21102

Hi Romanzif,

The last screenshot link you sent doesn’t work it seems. As for the “mt4config” error you are getting – are you using MT4 in “portable” mode? That is, is your “MT4 Data Folder” residing in the “Program Files” directory? If so, you need administrator permissions to write to this directory. The other thing to made sure is that the mt4config has a valid filename. From your screenshot, it looks valid, however just to make sure, you can specify a filename such as “broker.mt4config” in the EA parameters.

Hope this helps.

[imported_tickstoryParticipant September 11, 2015 at 12:02 am Post count: 1479]

in reply to: Help USA500 #21109

Hi Pandion,

That’s always a big question when testing an EA, which is why we can’t assist trouble-shoot specific EAs. The best advice we can give is to firstly test with the standard ‘MACD Sample’ EA and ensure you are getting modelling 99.9% quality. After that, it is likely that your EA is sensitive to one of the parameters such as spread, causing it not to trade. Other problems may include parameters such as lot-size, tick value (etc) being incorrect in the exported data. In this cause, you should be able to nail down the exact parameter that is causing the issue by logging the error code you get when trying to place an order. If you don’t have the EA’s source code, you will need to consult the vendor to see if they can assist.

Hope this helps.

[imported_tickstoryParticipant September 10, 2015 at 12:30 am Post count: 1479]

in reply to: Inconsistent results #21078

Hi Artisticmagic,

That’s a bit odd. Please let us know if you identify the issue as it may assist others!

Thanks!

[imported_tickstoryParticipant September 10, 2015 at 12:25 am Post count: 1479]

in reply to: lost FXT files #19176

Hi all,

The read-only issue mentioned above has now been resolved as of v1.7.2. You can refer to this post for further details:

http://tickstory.com/forum/viewtopic.php?f=2&t=766&p=3562&

Regards.

[imported_tickstoryParticipant September 10, 2015 at 12:13 am Post count: 1479]

in reply to: v1.7 Released! #21042

Hi all,

v1.7.2 has just been released! In this version, the following changes are included:

Fixes
• [artf288240] MT4 Export: FXT files not being marked as read-only when created for the first time.

Improvements
• [artf288241] Improved Japanese translation.

As before, registered users can download the latest from the link they were emailed during registration.

Happy trading! 😉

[imported_tickstoryParticipant September 9, 2015 at 11:07 pm Post count: 1479]

in reply to: Importing non Dukascopy data #21107

Hi AlgoNaute,

Thanks for your suggestion. We’re planning this feature in the next major upgrade to Tickstory which should allow text-based files to be imported/exported.
In the mean-time, if you’re wanting to import only bar data into MT4, you can do this via the “Import” function within Metatrader’s History Center.

Hope this helps.

[imported_tickstoryParticipant September 9, 2015 at 10:49 pm Post count: 1479]

in reply to: Symbol Setting Error #21088

Hi Worker,

Thanks for further information. It seems that your error (including a zero divide error) is coming from your EA. You will need to check why this is the case. All the other details seem to indicate that you have exported data correctly.
The problem is most likely in one of the parameters you are using in your EA. You can cross-check the actual value that’s being embedded in your FXT file by using the MT4 FXT Editor. You can then edit these values manually in order to trouble-shoot your issue.

Hope this helps.

[imported_tickstoryParticipant September 9, 2015 at 10:12 pm Post count: 1479]

in reply to: DAX data #21106

Hi Adeller,

We source Dukascopy data as-is without any modification. If they correct the data or back-fill any gaps then you can get these updates by downloading the data range again.

Regards.

[imported_tickstoryParticipant September 9, 2015 at 8:35 am Post count: 1479]

in reply to: Modelling quality problems with v1.7 #21099

Hi – can you please go to your message box and send us a personal message (PM) with your order details or email address you used to register? We will firstly check there is no issue with your license.
Also, are you able to confirm that Tickstory is successfully launching MT4? That is, you should see no error messages when launching.
If there is no issue with the launcher, it is most likely that you are getting a poor modelling quality due to either

1) You have not mapped the symbol you are testing correctly. (eg. if your symbol name is say ‘EURUSDm’, then you will need to map EURUSD to EURUSDm) or;
2) You are not testing in with a “tick” modelling quality.

Please let us know.

Thanks.

[Author]

Posts