cTrader 3.0 Bugs

Created at 24 Mar 2018, 02:06
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
SY

cTrader 3.0 Bugs
24 Mar 2018, 02:06


I am happy to test this, got some serious issues

 

First the backtesting data in TICK mode seam to be crap, compared to cBot (I was using fx pro for testing), now for example GBPJPY 01/01/2016 to 01/02/2016 have serious fail, more then 2 weeks missing, also alot a spot everywhere is missing, I cannot get anything to work with this data

 

Now from the API,

* The HasTrailingStop does not work, alsays like HasTrailingStop = false...

* ModifyPosition(Position, Volume)

ModifyOrder fail, I for example Sell a 5k Volume, want to split the order over time while the price going down.

Here a shot of one order split into 5, so I sell 1k (start at 16 pips profit) et for every 4 pips (around) going down. 

They seam to have a lot of issues, first the price should go up on each sell since the price go down (sell). It's doing the opposite. Also when the last order is close, only the last price is used in the trade statistics et graph, since the total net profit is 27.01 (but since the value on the history are not good its probably more like 5-6...) not 2.39, so the excepted result in the stats and graphs go like hell because it is not the good value. Without the split its 5.78 net profit I get...

 

 

 

 

 

 

I know it's beta, but I log this here to make sure someone correct the issue :)

Thank you!


@sylvain.rochette@gmail.com
Replies

sylvain.rochette@gmail.com
24 Mar 2018, 02:32

Also a suggestion, I mostly use Tick for my stuffs, That would be great to have in the Timeframe enum T1 to TX, I would like to test few stuffs using for example T20 with some indicators.


@sylvain.rochette@gmail.com

PanagiotisCharalampous
26 Mar 2018, 12:06

Hi Sylvain,

Thanks for reporting your issue. Could we have a cBot and backtesting parameters that will allow us to reproduce is and understand if this is a bug or not? Regarding your suggestion, I will pass it to the product team.

Best Regards,

Panagiotis


@PanagiotisCharalampous

sylvain.rochette@gmail.com
27 Mar 2018, 00:05

Ok i will do what I can since my project is big, i need to create a small example for that.

Basically I was doing a ClosePosition using ModifyPosition :) since the ClosePosition with a volume is not working in backtesting. I was decreasing the volume instead of increasing the volume.

 

from 5000 to 4000

from 4000 to 3000

from 3000 to 2000

from 2000 to 1000

then ClosePosition


@sylvain.rochette@gmail.com

PanagiotisCharalampous
27 Mar 2018, 09:19

Hi Sylvain,

If this is a similar issue to this one, then please note that we have managed to reproduce it and will be solved with the next update.

Best Regards,

Panagiotis


@PanagiotisCharalampous

sylvain.rochette@gmail.com
27 Mar 2018, 12:35

Yes it's exactly that great!


@sylvain.rochette@gmail.com