[imported_tickstoryParticipant October 12, 2015 at 11:02 pm Post count: 1479]

in reply to: Closing/opening time inconsistency #21170

Hi Pete,

That matches the UTC data we have in our screenshot. It starts at 9pm UTC. What’s the issue with this?

Thanks.

[imported_tickstoryParticipant October 10, 2015 at 10:33 pm Post count: 1479]

in reply to: Closing/opening time inconsistency #21168

Yes we did. I think it would be more helpful to record the exact steps that are causing your problem and then post accompanying screenshots. That way it’s easier to understand and reproduce the issue if there is one.

Thanks.

[imported_tickstoryParticipant October 10, 2015 at 9:23 pm Post count: 1479]

in reply to: MT4 build 890 not working with Tickstory 1.7.2.0 #21226

Hi Samimasri,

As previously mentioned, the first popup is not an error. The second one, however is saying that the launcher didn’t work for some reason.
Once MT4 has started fully, could you please try pressing the ‘Launch’ button again and see if this helps? If MT4 takes a while to load, it can cause a problem.
Also, what version of Windows are you currently using?

Thanks.

[imported_tickstoryParticipant October 9, 2015 at 9:40 pm Post count: 1479]

in reply to: Closing/opening time inconsistency #21166

Hi,

Attached is a screenshot of the GBPUSD data for 14 March 2010 as shown in the Tickstory Data Viewer. It starts at 21:00 GMT.

Regards.

[imported_tickstoryParticipant October 9, 2015 at 1:11 pm Post count: 1479]

in reply to: Closing/opening time inconsistency #21164

Hi Pete,

Dukascopy data has some known “anomalies” but generally speaking is a reliable source. Perhaps this thread helps explains more: viewtopic.php?f=2&t=580. If this doesn’t answer your question, perhaps you can highlight what you believe is wrong with GBPUSD on 14/03/2010? We’ve viewed the data in the Tickstory data viewer in GMT and can’t see issue. If you’re saying there’s only a problem when the time-zone is shifted, are you able to show the problem in a screenshot? Also, have you ensured that you’ve got all the latest Windows updates applied – Tickstory utilises the time-zone information from your Windows installation.

Thanks.

[imported_tickstoryParticipant October 9, 2015 at 4:41 am Post count: 1479]

in reply to: error occurred during download #21187

Hi Vohanh,

All your screenshots look the same to me and don’t indicate any problem. Can we get back to basics and tell me what it is you are trying to do?

Tbanks.

[imported_tickstoryParticipant October 8, 2015 at 9:21 pm Post count: 1479]

in reply to: TimeStamp of tickdata in microseconds #21225

Hi Danny_pip,

If you are referring to doing this in Metatrader MQL, then this isn’t possible. The data is stored with at best ‘second’ resolution within the data file itself – microseconds are stripped off.

Regards.

[imported_tickstoryParticipant October 8, 2015 at 9:17 pm Post count: 1479]

in reply to: v1.7 Released! #21061

Hi

Please consult these threads that may assist more on resolving Error 131:

viewtopic.php?f=4&t=799
viewtopic.php?f=2&t=794

Thanks.

[imported_tickstoryParticipant October 8, 2015 at 4:19 am Post count: 1479]

in reply to: v1.7 Released! #21059

Hi Erzanza,

That is fine as long as you don’t have more than 2 instances running at the same time.

Regards.

[imported_tickstoryParticipant October 7, 2015 at 10:25 pm Post count: 1479]

in reply to: Commissions #21219

Hi Don,

Thanks for the run down.

As far as we are aware, the commission details should be entirely encapsulated within the FXT file. Bear in mind that other details such as swap are also incorporated into the P & L, but from what you’re saying all the FXT fields are exactly the same. If possible, I would highly suggest that you obtain a full copy of your brother’s MT4 installation along with its Data Folder. You can then try to isolate the problem by:

1) Installing a “test” copy of MT4 and configuring Tickstory to use it, then;
2) Copying the FXT data from your brother’s Data Folder into the new MT4 test installation. Does this resolve the issue? If so, this indicates that there was some exported data that was different causing different results.
3) If the differences are still there, copy the Data Folder’s “config” contents over the top of the test MT4 installation. Does this resolve the issue? If so, it appears there is some MT4 broker specific information that is causing the difference.
4) If the differences are still there, copy the Data Folder’s “MQL” contents over the top of the test MT4 installation. Does this resolve the issue? If so, it appears that your EA itself is most likely causing the difference.

Hope this helps.

[imported_tickstoryParticipant October 7, 2015 at 11:43 am Post count: 1479]

in reply to: error occurred during download #21183

Hi Vohanh,

Please see the attached annotated image of your screenshot. It highlights that you seem to have correctly installed TickstoryInfoExpert. The TickstoryInfoExpert.ex4 is highlighted in your screenshot of the folder and the TickstoryInfoExpert EA is highlighted in your MT4.

Thanks.

[imported_tickstoryParticipant October 7, 2015 at 11:34 am Post count: 1479]

in reply to: Error message #131 Invalid Volume #21152

Hi Seeker_a,

I believe you can use “/skipupdate” in the command-line argument when launching to suppress the updates. You can configure this in Tickstory vis File->Settings->MT4 Settings->Launch params..

Please let us know if this works for you.

Thanks.

[imported_tickstoryParticipant October 6, 2015 at 10:06 pm Post count: 1479]

in reply to: Timezone confusion! #21157

Hi Houmous,

The idea is to ensure that you match the time-zone with the broker that you will eventually be trading your EA live with. This means there will be less variables between your simulated and real EA trading environments.
If you’re going to trade your EA live with IC Markets, then export with New York time.

Regards.

[imported_tickstoryParticipant October 6, 2015 at 10:56 am Post count: 1479]

in reply to: Problem SP500 – Tester cannot calculate prices #21212

Hi Pandion,

I assume that you’re still getting the “Cannot calculate prices” error? Or has this been resolved after copying the above-mentioned settings?

We took the following steps to back-test S&P 500:

1) Download demo MT4 from XM.COM. Run it once and log in. A symbol called US500-DEC15 should exist in this platform.
2) In Tickstory File->Settings->MT4 Settings, set the path to your MT4 Installation folder.
3) In Tickstory, select the instrument USA500IDXUSD, right-click and Export to MT4.
4) In the “MT4 Settings”, copy all the details from the screenshot in this thread. Set the “Maps to” field to “US500-DEC15” which is the name of your MT4 symbol.
5) Select the dates for export – just start with the last month to keep things simple.
6) When done, Launch MT4 with Tickstory (press F8).
7) Select the US500-DEC15 instrument in the Strategy Tester. Select the “MACD Sample” EA for testing.
8) Start the test.

Hope this resolves the issue for you.

Regards.

[imported_tickstoryParticipant October 6, 2015 at 9:35 am Post count: 1479]

in reply to: Remote name could not be resolved #21224

Have you checked the MT4 History Center? Does it have the correct dates for the data you exported?

[Author]

Posts