Forum Replies Created

Viewing 15 posts - 766 through 780 (of 1,458 total)
  • Author
    Posts
  • imported_tickstory
    Participant
    Post count: 1479

    Hi Render86,

    Are you referring to the MT4 setting for “Data folder”? We tried reproducing your issue by upgrading and this setting was correctly preserved.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Render86,

    According to the log information you posted, MT4 seems to be processing the tick data information. Have you tried to use a “standard” EA such as the “MACD Sample” to ensure that this isn’t specific to your particular EA? Alternatively, you can crete a new EA with one line of code like:

    Print("Bid: " + DoubleToStr(Bid));

    And verify if the Journal reports the Bid price during the back-test.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Adeller,

    Thanks for touching base. The feature is still undergoing development as part of the next major release. Unfortunately our development timelines for the new version have been pushed back a little due to priority enhancements for the current version. We will make sure we update you when we are closer to the release date.

    Kind regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Gooly,

    Thanks for providing info on this. Interestingly, we saw something similar to you during the development of Build 600+ which got us excited. It seemed that a couple of builds actually used FXT files rather than over-writing them if they were marked as ‘read-only’. At some stage however, it seems to have been reverted. We’ll obviously need to wait to see if this is a permanent change. The main draw-back of the feature was that (as you mentioned) the modelling quality was shown as N/A. This is obviously just an aesthetic issue but it was throwing some users off.
    If the change is permanent, it will at least mean that users can continue to back-test on newer versions of MT4 without having to wait for an updated launcher which is a great step forward.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: v1.4 Released! #19914

    Hi Nueo,

    Many thanks for getting back to us – great to hear to resolved the issue!
    Hopefully the up-coming version of Tickstory will address the item you mention – you will need to explicitly set up an MT4 folder and therefore provide all the folder locations on the initial set up.

    Kind regards.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: v1.4 Released! #19912

    Hi Gooly,

    Thanks for your feedback. The title bar can unfortunately get overridden by MT4 if it decides to change it. You can assume that the launch process has successfully worked if you do not get an error from Tickstory.

    Hope this helps.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: v1.4 Released! #19910

    Hi Nueo,

    We have tested the launcher on Build 625 and it works. Are you getting some sort of an error during the launch?

    Thanks.

    imported_tickstory
    Participant
    Post count: 1479

    Hi RL2013,

    Windows does not allow you to write data in the specified location (i.e. in your ‘Program Files’ directory). In your export file specification, specify a filename with a directory path such as “C:XAGUSD.txt” (or in your ‘Documents’ folder) and this should work.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi RL2013,

    The “Ninjatrader Tick Format” is intended to export tick data only. As such, make sure your export time-frame is set to “Tick” if you wish use this option. You can then import the file into Ninatrader as tick data.

    Alternatively, if you are looking to import bar data into Ninjatrader (such as 1-minute bars), according to the Ninjatrader manual (http://www.ninjatrader.com/support/helpGuides/nt7/index.html?importing.htm), NT bar data supports the following format:

    yyyyMMdd HHmmss;open price;high price;low price;close price;volume

    To achieve this in Tickstory, you can export with the following settings:

    Timeframe: 1-Minute
    Include headers: No
    Custom Format: {BarBeginTime:yyyyMMdd} {BarBeginTime:HHmmss};{Open};{High};{Low};{Close};{Volume}

    Please let us know how you go – we can add this as a pre-defined option to make things easier in the future.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Trader2384,

    Yes, you are correct – it appears that Dukascopy has extended the available data to 2006 which is positive news. If you have any updates to the date ranges, appreciate if you could share them on Tom’s post as I’m sure other users will find this of great use!

    Thanks.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Trader2384,

    As mentioned, we don’t support this configuration so hopefully some other users may be able to share a workaround with you.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Trader2384,

    The size of the data files are obviously going to be correlated with trading activity. If you have downloaded the data range and no errors appear in the log window then you can assume everything was downloaded correctly.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: Which Build? #19943

    It is best to put in a spread value otherwise your results will be skewed.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Trader2384,

    Unfortunately not with the current way things are set up. Tickstory currently utilises a single configuration file that resides in the user application directory. If you can virtualise or change this folder then you may be able to switch between several configurations, however we do not recommend this nor support it.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: 2012-2013 Data #19934

    Hi Trader2384,

    We tested the date range you mentioned – the reason why you are not seeing a bar for 28th of July 2012 is because no trading occurred on that day (i.e. a Saturday).

    The “include weekends” option simply disables a filter that would otherwise ignore all tick data between Friday 22hrs (GMT) to just before Sunday 21 hours (GMT) when “normal” trading resumes. Dukascopy does not trade on Saturdays so you should never see data for these days.

    Hope this helps.

Viewing 15 posts - 766 through 780 (of 1,458 total)