[imported_tickstoryParticipant January 20, 2014 at 10:32 pm Post count: 1479]

in reply to: variable spread in backtesting…. #19631

Hi 4EverMaAT,

The export and launcher only support fixed spreads at the moment.

Regards.

[imported_tickstoryParticipant January 20, 2014 at 3:42 am Post count: 1479]

in reply to: Export of MT4 Symbol Properties #18978

Hi Ejcmartins,

Could you please do a comparison between your “MT4 Symbol” info between XAUUSD and GBPUSD. It is possible that the instrument information for XAUUSD is not configured fully which could be causing the issue (for eg. the Lot Step setting could be zero causing an issue).

Regards.

[imported_tickstoryParticipant January 20, 2014 at 3:38 am Post count: 1479]

in reply to: Zero divide error #19583

Hi Fepra,

This issue typically occurs when there’s an error in the EA, the executable is corrupt or compiled for a different MT4 version. Can you please recompiling the MACD Sample and see if this helps? Otherwise I would suggest you download a new version of MT4 and firstly test the MACD Sample before exporting data from Tickstory to ensure everything works fine.

Hope this helps.

[imported_tickstoryParticipant January 20, 2014 at 3:21 am Post count: 1479]

in reply to: How does the Metatrader Info MT4Config impact MT4 backtest #19609

Hi Shawky,

I’m guessing that you have an EA that’s particularly sensitive to spread. What you could do is work with a fixed spread and break back-test down into yearly time-periods. This would at least give you some indication of spread level and year(s) that your EA starts to degrade and perform further analysis from there.

Hope this helps.

[imported_tickstoryParticipant January 16, 2014 at 11:08 pm Post count: 1479]

in reply to: Possible Error FXT m30 for all pairs? #19601

Hi Lukemp3 – Thanks for letting us know you fixed the problem!

Regards.

[imported_tickstoryParticipant January 16, 2014 at 11:07 pm Post count: 1479]

in reply to: How does the Metatrader Info MT4Config impact MT4 backtest #19607

Hi Shawky,

Sorry for the delay getting back to you. Supporting variable spreads is still on the cards, however our first priority is to revamp Tickstory so it can support this and many more features and platforms that our users are asking for.
Appreciate your patience and support.

Kind regards.

[imported_tickstoryParticipant January 16, 2014 at 10:13 am Post count: 1479]

in reply to: Server 2008 Installation #19629

Hi pbageps,

Unfortunately .NET 4.5.1 and .NET v3.5 SP1 are two different products. You will need to explicitly install the 3.5 version to make things work.

Hope this helps.

[imported_tickstoryParticipant January 16, 2014 at 10:12 am Post count: 1479]

in reply to: Zero divide error #19581

Hi Fepra,

Does the problem occur with a standard EA such as “MACD Sample”?

Thanks.

[imported_tickstoryParticipant January 14, 2014 at 8:43 pm Post count: 1479]

in reply to: Application error #19597

Hi Norbertbti,

Thanks for getting back – great to hear it works now.
The issue seems to be pointing to a corrupt .NET installation. We initially thought the problem may be due to some odd setup with where your configuration was stored, however this does not appear to be the case.

Hopefully this post will be able to assist others.

Regards.

[imported_tickstoryParticipant January 13, 2014 at 12:32 pm Post count: 1479]

in reply to: Application error #19594

Hi Norbertbti,

Did you see the config file was re-created in the location you mentioned when you started Tickstory again?
Also, is it possible to confirm that the application is working correctly on another (non VPS) system that you have available?

Thanks.

[imported_tickstoryParticipant January 12, 2014 at 9:21 pm Post count: 1479]

in reply to: FXT is being used by another process #19611

Hi Marcel,

Are you able to run the IObit Unlocker once you get the “file locked” error message in Tickstory? This will hopefully confirm what application/process has the file locked. Would you have the exact steps you are using to get this error message so we can try reproduce it?

Thanks.

[imported_tickstoryParticipant January 11, 2014 at 10:14 pm Post count: 1479]

in reply to: FXT is being used by another process #19612

Hi Marcel,

The most likely reason for this error is that you are running Metatrader at the same time you are trying to edit the FXT files. This will not work since MT4 locks the files from being written to by other processes. The simple solution should be to quit your Metatrader, edit the FXT file in Tickstory and then start Metatrader again.

If you are still having problems, you can download a program like ‘WhoLockMe’ (http://www.dr-hoiby.com/WhoLockMe/) which will tell you what application is locking the file.

Hope this helps.

[imported_tickstoryParticipant January 9, 2014 at 11:07 am Post count: 1479]

in reply to: Application error #19592

Hi Norbertbti,

Thanks for the further detail. The contents of the config file appears correct.

Can you please rename or delete any config files you see in any directories including the one you mentioned:

C:UsersusernameAppDataLocalTickstoryTickstory Lite
C:UsersusernameAppDataRoamingTickstoryTickstory Lite
C:Documents and SettingsAdministratorApplication DataTickstoryTickstory Lite

And then try to restart your application?

It could have something to do with a bad config file somewhere so doing a fresh start of Tickstory might pin-point where Tickstory is loading/storing your configuration.

Regards.

[imported_tickstoryParticipant January 8, 2014 at 11:22 pm Post count: 1479]

in reply to: how to create normal (not-tickdata) mt4-history? #19569

The FXT files will not be created and you should also not need to launch MT4 via Tickstory as you are not using the FXT/tick data.

Regards.

[imported_tickstoryParticipant January 8, 2014 at 11:19 pm Post count: 1479]

in reply to: Possible Error FXT m30 for all pairs? #19598

Hi Lukemp3,

Unfortunately we have not used this software so can’t comment on what the problem may be. Maybe some other member who is familiar with this program can assist, although suffice to say that if there is a stack overflow error, this usually indicates there is a bug in the EA.

Regards.

[Author]

Posts