Forum Replies Created
-
AuthorPosts
-
in reply to: zarjpy wrong decimal #20851
Hi Bmigette,
We’re just looking into this one and will get back to you.
Thanks.
in reply to: MT4 Launcher issue on Windows 7 #20858Hi Primito,
Can you please try starting MT4 manually first and then subsequently launch via Tickstory to see if this resolves the issue?
Sometimes the launcher may have issues if there is a delay in the MT4 application startup.Thanks.
in reply to: v1.6 Released! #20774Hi Jared,
Couple of questions:
1) Have you applied your license in Help->About before launching?
2) What is happening when you try launch Metatrader by itself?
3) If Metatrader is starting fine by itself, what happens if you simply select ‘Launch’ from Tickstory after it has started?
4) How are you confirming that the launcher is not working? Are you attempting to back-test after you launch?Thanks.
in reply to: v1.6 Released! #20768Hi Eduardculka – thanks for your support. It’s likely that in your Metatrader folder you have a “tds.exe” file remaining which Tickstory is trying to use. Remove this file and this should hopefully resolve the issue.
Regards.
Hi – You will note that the symbol name in Dukascopy is “JPNIDXJPY” whereas your MT4 symbol name is “[JP225]” (note the braces). You will need to use the “Maps To” field to map the Dukascopy symbol to your MT4 symbol name. This process is described in the manual and also if you search the forum for “Maps to”.
Regards.
in reply to: Back-testing questions #20850Hi Forexman,
Regarding your questions:
1) Just double-check that all the data you exported is appearing correctly in the Metatrader charts and also in the History Center. This will rule out any possible export issues. After this, you’ll need to hone in with why you believe the EA is “skipping” some months. Use “MACD Sample” EA first – if all is well, then it’s likely that your EA is giving you issues or there is some criteria preventing it from trading.
2) Again, you will need to trouble-shoot the EA to see why it’s stopping. Check the error logs to see why this might be occurring. The only known limitation that could be causing a problem outside of this is if your FXT data files are greater than 4GB. If this is the case, you will need to reduce your back-testing range until the file size is under 4GB.
3) The executables for Build 765 can be found here:
[hide:exwtyter]http://www.tickstory.com/files/Metatrader.765.zip[/hide:exwtyter]Hope this helps.
Check the FAQ, please for “I am not getting 99.9% modelling quality on my back-tests”:
Thanks.
in reply to: Error message! I cannot run Tickstory #20746Hi fx4sam,
This is not a Tickstory error message. This is an error generated by Metatrader that your EA has invalid stop prices. You can search “mt4 error code 130” for further information and how to correct your EA.
Regards.
in reply to: 7,39% Modelling Quality after revert to Build 765 #20834Hi – We just re-tested with Build 765 and all is working fine. Best bet is to revisit the FAQ and some of the other threads which help trouble-shoot this issue.
Regards.
in reply to: 7,39% Modelling Quality after revert to Build 765 #20832Hi Hylocharis – Given that there’s been a flurry of recent MT4 updates, it’s possible that MT4 introduced the breaking change on or before this build. I suggest you try an even earlier build such as ~725 and see if this works.
Regards.
in reply to: v1.6 Released! #20767Hi Dreamr,
Please ensure you apply the license you were issued by email by going to Help->License in the menu and pasting the code. After this, please try launching again.
Regarding “read-only” files – make sure “Make FXT Read-only” is checked during the export (this is the default).Thanks.
Thanks for the suggestion, Duker. We did note it in the email you received, but understand that it can be missed. Most importantly, glad to hear you’ve resolved the issue!
Regards.
in reply to: Question On Buying #20841Hi Vitali,
Your payment of US$23.95 gives you early access to Tickstory along with any updates until August 31st. Other terms of the software license do not change. We unfortunately cannot guarantee updates indefinitely for the fee we are charging which is why this limitation is specified. If there is sufficient uptake of licenses, then this would mean we could provide on-going updates for a longer period. The structure is designed to benefit all – if users participate, then we can continue to provide updates for you. If not, we will revisit the fee while ensuring that licensed users somehow benefit from their early adoption (aside from the obvious advantage of getting to use the latest software right now).
On a similar topic, you may want to also read this thread which might also be helpful:
Hope this helps.
-
AuthorPosts