dave.anderson.consulting
07 Nov 2024, 14:25 ( Updated at: 08 Nov 2024, 06:13 )

RE: RE: Two years testing cTrader, and now the troubles of 5.0.40

PattyTradeTeam said: 

PanagiotisCharalampous said: 

Hi all,

This problem should have been resolved by now. Please restart your cTrader and in case you still experience problems, please send us some troubleshooting information quoting this thread.

Best regards,

Panagiotis

Thank you for your efforts.

Please consider some of our feedback for future developments

Keep moving in the right direction cTrader deserves to become a leader of the trading platforms

Patty

“Keep moving in the right direction cTrader deserves to become a leader of the trading platforms”

Why exactly? Based on your supposed findings? You contradict yourself. It's like the comments under the youtube videos that superficially thank the author for what he uploaded. Regardless of what nonsense the author says.
Regarding software quality, reliability and speed, cTrader is years behind almost every other platform I know.
Besides, every mediocre developer knows what software testing and software quality is. I'm sure the cTrader team knows it too. The only question is why they don't do anything about it.

dave.anderson.consulting
04 Nov 2024, 19:48

I have yet to come across a latest version of cTrader that doesn't have ridiculously big bugs.

For the future consider installing a version of your broker instead of the latest version of cTrader. The lateste versie seems to be a kind of test version.

dave.anderson.consulting
04 Nov 2024, 19:43

Probably a cTrader 5.0.40 issue. Many seem to have this kind of weird issues since upgrading to 5.0.40.

For the future consider installing a version of your broker instead of the latest version of cTrader. The lateste versie seems to be a kind of test version.

dave.anderson.consulting
04 Nov 2024, 16:44

I once accepted 2 clients with cTrader projects and since then I have experienced so much misery that I have sworn to not accept any new cTrader clients.
I know a few trading platforms and must honestly say that cTrader is by far the most unstable platform you can have.
I will keep it short.....
I learned a long time ago that I should not use the latest version of cTrader but the broker version of cTrader. These are often a few versions behind. And of course there is a good reason for that.
In my opinion, the latest cTrader version should always be seen as an alpha or at most a beta version. The intention is that the bugs are found and reported by the users.

dave.anderson.consulting
07 Jun 2024, 20:11

In fact, I think your list of defects is much shorter than reality. I should have looked at the forum earlier. I've been dealing with strange behavior from cBots that have sometimes been in the live account for more than 1 year now for almost a day. Backtesting and Optimization are of course the two regulars that almost never work properly after a release.
I think the UI has deteriorated this time compared to previous releases. I guess they have a new UI designer ;-)

Immediately back to previous version 4.9. I won't be using the latest release from now on either. I will stay at least 1 version behind so as not to make my life unnecessarily miserable!

dave.anderson.consulting
29 Aug 2023, 15:54

RE: Random error #FDDE36C4 . Please help !

rob.p.marshall said: 

I also have the same problem. The errors in the log are:

11/02/2023 01:39:17.037 | CBot instance [FuryB 0.21.2, AUDUSD, Re8] crashed with error #FDDE36C4.

 

 

This has been resolved in 4.8.23. I no longer experience this.

dave.anderson.consulting
29 Aug 2023, 15:53

RE: Decimal OverflowException on cBot optimization when using multi timeframe

Spotware said: 

Dear traders,

The new update (v4.8.23) was released on Cross Broker cTrader and some brokers. Please let us know if you still experience this problem with this version.

Best regards,

cTrader Team

I no longer experience this. Thanks for quick update and hopefully a better testing process in the future.

dave.anderson.consulting
29 Aug 2023, 15:52

I no longer experience this. Thanks for quick update and hopefully a better testing process in the future.

dave.anderson.consulting
25 Aug 2023, 14:09 ( Updated at: 26 Aug 2023, 14:48 )

No there isn't any workaround for this bug  :-(

No there isn't any fix for this bug even on cTrader version 4.8.23 in 2023 :-(

Even after 4 years!

See originally reported bug in 2019: https://ctrader.com/forum/cbot-support/15410

dave.anderson.consulting
25 Aug 2023, 14:06 ( Updated at: 26 Aug 2023, 14:49 )

This is an old bug which was reported in 2019.

This issue has never been resolved since it was reported. We are now 4 years later and still no fix on cTrader version 4.8.23.
I needed to optimize a client's cBot and ran into this bug today.
To make sure it's not my fault I grabbed the originally reported cBot (see originally reported issue) and tested it and saw that there is still a difference between Optimization and Backtest results. Exactly as it was reported in 2019.

Reply to standard reply of support “Share the cBot with us so that we can reproduce”:

Originally reported issue : The same issue with cBot code in here: https://ctrader.com/forum/cbot-support/15410

dave.anderson.consulting
25 Aug 2023, 13:58 ( Updated at: 26 Aug 2023, 14:46 )

This issue has never been resolved since it was reported. We are now 4 years later and still no fix on cTrader version 4.8.23.
I needed to optimize a client's cBot and ran into this bug today.
To make sure it's not my fault I grabbed the above passed cBot and tested it and saw that there is still a difference between Optimization and Backtest results. Exactly as it was reported here in 2019.

Reply to standard reply of support “Share the cBot with us so that we can reproduce”:

See the same issue with cBot code in here: https://ctrader.com/forum/cbot-support/15410

dave.anderson.consulting
25 Aug 2023, 13:52

This issue has never been resolved since it was reported. We are now 4 years later and still no fix on cTrader version 4.8.23.
I needed to optimize a client's cBot and ran into this bug today.
To make sure it's not my fault I grabbed the above passed cBot and tested it and saw that there is still a difference between Optimization and Backtest results. Exactly as it was reported here in 2019.

dave.anderson.consulting
23 Aug 2023, 14:38 ( Updated at: 24 Aug 2023, 05:07 )

RE: RE: BACKTESTING AND OPTIMIZATION FAILURE IN VERSION 4.8.21

thebeinvest said: 

Spotware said: 

Dear traders,

Can you please provide us with exact steps on how to reproduce this problem?

Best regards,

cTrader Team

                           double TrailingStopPips = (result * AjstSLM2);                                                                                  var newStopLoss = pos.TradeType == TradeType.Buy ? Symbol.Bid - Symbol.PipSize * TrailingStopPips : Symbol.Ask + Symbol.PipSize * TrailingStopPips;                                                                                  var StopLoss = ModifyPosition(pos, newStopLoss, pos.TakeProfit, true);                                                      if (StopLoss.Error == ErrorCode.InvalidStopLossTakeProfit && (Account.Equity >= (Account.Balance * 1.01)) )                            ClosePosition(pos);

if I simply put "FALSE", deactivating the modify position, it doesn't give the error anymore, the error is in the position modification.

If I do a ModifyPosition and change StopLoss only once, the cbot doesn't crash, however, if I activate HasTrailingStop (true), then yes, it's crashing.

Again, in other versions this did not happen.

I've done the test by changing all trailingStop methods and all give the same error.

In summary, if I deactivate HasTrailing Stop (false) it works, if I activate it, it gives an error. And again... in the other versions, this didn't happen.

in backtesting, I activated the visual mode, and believe me, in visual mode I have no problem with backtesting, but without visual mode and also in optimization it has a problem, that is, I cannot perform optimization, nor backtesting without visual mode.

I have just tested it on ctrader version 4.7.13 and confirmed that backtesting works normally even without visual mode activated.

Thus confirming that version 4.8.21 brought this error bug.

Please... help me take this message to the developers, it will help a lot of people.

the algorithm is correct, however, with the new update it is giving this error.

Even without Trailing Stop it crashes on optimization. In one of my cBots I have no trailing stop and no ModifyPosition. Even that cBot crashes the same way.

dave.anderson.consulting
23 Aug 2023, 11:17 ( Updated at: 24 Aug 2023, 05:03 )

This is the same issue as this https://ctrader.com/forum/calgo-support/41646

A fresh bug in the cTrader.

dave.anderson.consulting
23 Aug 2023, 11:13

RE: Decimal OverflowException on cBot optimization when using multi timeframe

Spotware said: 

Dear Marisco,

Thank you for reporting this issue. We were able to reproduce it and and we will fix it in an upcoming update.

Best regards,

cTrader Team

Any workaround for this until your next update?
I can't tell my customer to wait for Spotware to come out with an update someday.

dave.anderson.consulting
22 Aug 2023, 21:35 ( Updated at: 22 Aug 2023, 21:36 )

RE: Decimal OverflowException on cBot optimization when using multi timeframe

Spotware said: 

Dear Marisco,

Thank you for reporting this issue. We were able to reproduce it and and we will fix it in an upcoming update.

Best regards,

cTrader Team

Actually the optimization feature is broken. I hope this gets some priority.

By the way, this issue also occurs on single timeframe cBots.

dave.anderson.consulting
22 Aug 2023, 21:24

I have exactly the same problem.

dave.anderson.consulting
10 Feb 2023, 18:13

RE:

PanagiotisChar said:

Hi Dave,

They are posting release notes in Announcements

Aieden Technologies

Need help? Join us on Telegram

Need premium support? Trade with us

 

Obviously I had already read that before I started writing a message here.
The problem is that the cTrader team may use a different wording than I've done here.

I hope they fix this issue in the next update.

dave.anderson.consulting
10 Feb 2023, 13:47

Dear cTrader Team,

I checked with latest update and saw that the issue is not resolved in 4.6.3 version.

How will you announce when this is fixed? Are you going to reply on this message or is there another way of letting know this is resolved?

Regards,

Dave

dave.anderson.consulting
25 Jan 2023, 11:34

Awesome!
Big, useful and necessary features that I and probably many algo developers have been waiting for. These additions alone were enough to bring me back to cTrader. Can't wait to rewrite my algos back to cTrader.
Especially Renko-Range backtest and optimization possibilities are a very big improvement. But Local Storage and Rate Conversion are also great enrichments.

I don't know what or who put this on the agenda and made it possible, but I am very grateful. Very much appreciated.