[imported_tickstoryParticipant July 22, 2015 at 11:40 pm Post count: 1479]

in reply to: MT4 Build 830 and newer #20941

Hi Iconio,

The latest Tickstory v1.6 that supports Builds 830+ is available for purchase and you can find out more here: viewtopic.php?f=2&t=696. Once you have ordered you will be sent the download link and license information to get you going.

Hope this helps.

[imported_tickstoryParticipant July 22, 2015 at 11:27 pm Post count: 1479]

in reply to: Impossible to launch terminals and terminals not located #20944

Hi Carabama,

I believe we’ve assisted you resolve this error now with the following response:

To prevent TDS from being launched, please rename or delete the file tds.exe from the MT4 installation folder.  Once you have done this Tickstory should use its own launcher. 

There should be no problem selecting an installation folder other than C:.  You should be able to browse to that location using the “select” button. 

Regards.

[imported_tickstoryParticipant July 21, 2015 at 11:16 pm Post count: 1479]

in reply to: GBPNZD [M15] FXT fails #20932

Hi Jlao,

It sounds to me that you’re coming across the MT4 4GB FXT size limitation. You can find out more about this in our FAQ under the question “My back-test doesn’t complete fully and stops at a certain date. What’s happening?”:

viewtopic.php?f=4&t=613

Regards.

[imported_tickstoryParticipant July 21, 2015 at 10:53 pm Post count: 1479]

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

Hi FMIC, we have PM’d you with some details about running a test version for us.

Thanks.

[imported_tickstoryParticipant July 21, 2015 at 11:27 am Post count: 1479]

in reply to: Testing MT4 #20931

Hi Gianfrancotanzi,

The best advice we can give is to check your EA for the conditions that make the trailing stop to move. Check also the ‘Journal’ tab which may be giving you errors when the order details are being changed. In this case, it is often the specified price that could be causing the problem (i.e. it isn’t being “normalised” correctly). If you are getting errors, it will specify an error number which you can Google to find out more.

Hope this helps.

[imported_tickstoryParticipant July 21, 2015 at 5:58 am Post count: 1479]

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

It could be the case – some reports are suggesting the .NET framework is not releasing the file until an explicit garbage collection is done. Certainly appears to be symptomatic to what you describe – Tickstory does not have any in-built 5-10 minute delay to release any file locks. All our tests are done on the most up-to-date NET v3.5 SP1.

[imported_tickstoryParticipant July 21, 2015 at 1:10 am Post count: 1479]

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

Thanks for the last piece of information. It sounds like there’s something O/S-related that we’ll need to see if we can work around and let you know.

[imported_tickstoryParticipant July 20, 2015 at 10:03 pm Post count: 1479]

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

Hi FMIC,

Thanks for the clarifications. We just need to clarify as much as possible just in case we’ve missed something. We have never seen this issue occur unless some other applications are involved in the mix somehow. For example, if MT4 is running, it is still a potential candidate for fully reproducing the problem since it can be using the file and causing a knock-on effect somewhere in Tickstory. If you can confirm that no other applications that potentially use the FXT are running, then this would be appreciated. Tickstory does not open any FXT file on a fresh start, so it is a bit confusing how a single instance can be locking a file it reportedly cannot open for writing.

Re: “Data store”, apologies, what I was referring to was the MT4 data location and whether it was on the above-mentioned drives. Obviously if you are exporting MT4 data, there is a potential that the files are still locked for some reason. However, since you have confirmed you are only performing the 4 steps described from a clean start, then this shouldn’t be the cause.

We can only determine at this stage that the lock may be due to either 1) An error that occurred while writing the file, causing it to be left open (although this does not appear to be the case) or 2) The operating system not having flushed the file to the disk yet, causing the file to be locked.

At this stage, we still cannot reproduce the error with the mentioned steps. Thanks for the suggestion to review the issue further on your machine. We will need to review the code to see if we can trouble-shoot with the information you have given us first.

Thanks.

[imported_tickstoryParticipant July 20, 2015 at 9:48 pm Post count: 1479]

in reply to: Fixed Spread? #20930

Hi EasyX,

Yes, there seems to be an MT4 change that now uses the spread you set in the strategy tester. Please see this thread for more:

viewtopic.php?f=4&t=728

Thanks.

[imported_tickstoryParticipant July 20, 2015 at 1:21 pm Post count: 1479]

in reply to: Tickstory and commission #19871

Hi Bogola,

Perhaps it is the swap rate that is skewing the profit calculations? You can check what swap has been set in the FXT editor.

Regards.

[imported_tickstoryParticipant July 20, 2015 at 12:17 pm Post count: 1479]

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

HI FMIC,

Can you please confirm that the 4 steps I outlined above causes the problem? I’m not sure if this error will have anything to do with the installation directory, however if you have specified a “Data store location” that is on a removable drive (S: or D:?), perhaps there could be some issue where the file isn’t being released.

Thanks.

[imported_tickstoryParticipant July 20, 2015 at 12:03 pm Post count: 1479]

in reply to: Data error while downloading #20924

Hi Erick,

It appears that you are only occasionally getting corrupted files. Is it possible that your internet connection is disconnecting/overloaded? Do you have a different machine and/or connection so you can rule out these possibilities?
To test your internet connection, could you please click on the following link to see if it downloads successfully: http://www.dukascopy.com/datafeed/EURUSD/2015/04/01/00h_ticks.bi5 It should be 11.7kb in size.
Then, could you please check the file D:DataEURUSD2015410h_ticks.bi5 and ensure it is the same size?
After that, could you please delete D:DataEURUSD2015410h_ticks.bi5 and see if the problem occurs again? Perhaps Tickstory does not have sufficient permissions to delete this file to re-download it.

Thanks.

[imported_tickstoryParticipant July 19, 2015 at 10:56 pm Post count: 1479]

in reply to: Data error while downloading #20922

Ok, that solves the problem as to why the data directory keeps changing. The error you are getting doesn’t seem to be related to “access denied” which is what you get if you don’t have sufficient UAC permissions. Instead, it seems that the existing data is corrupted for some reason. Could you please do the following:

1) In Tickstory, right-click on the log window and “clear” all existing entries.
2) Download data from 1st May 2015 to 1st July 2015.
3) Note any errors that occur and save them on Notepad or another text editor.
4) Clear the log window again.
5) Re-download the same date range and see if the errors occur again.

After step 5, you should not see any errors as Tickstory should have re-downloaded the data. If the “Data error” still recurs, something more unusual is happening and will need to be investigated further.

Thanks.

[imported_tickstoryParticipant July 19, 2015 at 12:35 am Post count: 1479]

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

Hi FMIC,

We have tried the following (exact) steps to try reproduce the problem but cannot:

1) Start Tickstory
2) Start up the FXT editor and select any FXT file.
3) Edit a field in the FXT
4) Save the file.

The file save successfully with no locking error. Are there some other steps you are taking prior to step 4)?

Thanks.

[imported_tickstoryParticipant July 19, 2015 at 12:28 am Post count: 1479]

in reply to: Backtest without result (trades) #20918

Hi Nico,

Again, it is possible that the EA is not trading due to some settings that it is sensitive to. The other thing to check is that “lot size”, “min lot” settings, etc for the symbol you are back-testing are correct. Debugging information will definitely help isolate what is preventing the trade. You can also try compare the FXT settings of the “working” data to that of the “non-working” data to see what settings are different and make them the same via the FXT editor. After that, the only variable is the data itself which means that some pricing/indicator condition is preventing your EA from trading.

Hope this helps.

[Author]

Posts