Topics
Replies
firemyst
02 Jul 2024, 02:17
( Updated at: 02 Jul 2024, 05:27 )
Manually, you change the amount you have:

Programmatically, you can follow the example on this page:
https://clickalgo.com/ctrader-market-orders
@firemyst
firemyst
28 Jun 2024, 07:07
( Updated at: 28 Jun 2024, 07:16 )
Have you reviewed and tried the example Spotware provided?
https://help.ctrader.com/ctrader-algo/guides/network-access/#how-to-use-network-access
If so, what happened?
@firemyst
firemyst
26 Jun 2024, 08:53
( Updated at: 26 Jun 2024, 09:10 )
RE: RE: RE: RenkoAshi cBot trouble
PanagiotisCharalampous said:
firemyst said:
PanagiotisCharalampous said:
Hi there,
The freeze issue is under investigation. Regarding the SL issue, this usually happens when you are trying to set invalid stop losses i.e. inside the spread or with an invalid price. If you can provide steps to reproduce the problem with valid stop loss prices we are happy to have a look.
Best regards,
Panagiotis
Has Spotware been able to reproduce the freeze issue?
Hi firemyst,
Please stop spamming the entire forum with this issue and keep the conversation in one place. The OP does not mention your issue.
Best regards,
Panagiotis
Sorry. My issue is the “Freeze” issue, which the OP in this thread clearly mentioned in their original post (bold italiacs are mine) :
"cBots that run on "Ontick" or "Renko Chart" frequently freeze because the number of bars exceeds the memory."
Also, I didn't see an answer to the question if Spotware has been able to reproduce the freezing yet that's been reported?
Thank you.
@firemyst
firemyst
26 Jun 2024, 07:46
( Updated at: 26 Jun 2024, 08:27 )
RE: RenkoAshi cBot trouble
PanagiotisCharalampous said:
Hi there,
The freeze issue is under investigation. Regarding the SL issue, this usually happens when you are trying to set invalid stop losses i.e. inside the spread or with an invalid price. If you can provide steps to reproduce the problem with valid stop loss prices we are happy to have a look.
Best regards,
Panagiotis
Has Spotware been able to reproduce the freeze issue?
@firemyst
firemyst
26 Jun 2024, 07:44
( Updated at: 26 Jun 2024, 11:44 )
If you actually post this request in the correct forum, they may actually look at it and decide to implement it.
If you want something, post it in Suggestions:
https://ctrader.com/forum/suggestions
Otherwise, it'll probably be ignored here because this forum is for help/technical support.
@firemyst
firemyst
26 Jun 2024, 07:42
( Updated at: 26 Jun 2024, 07:52 )
Please post this in the Suggestions forum:
https://ctrader.com/forum/suggestions
Your post here probably won't be acted upon by Spotware as this forum is for help and/or support, not suggestions.
@firemyst
firemyst
26 Jun 2024, 07:41
( Updated at: 26 Jun 2024, 07:51 )
You need to post these requests in the suggestion forum:
https://ctrader.com/forum/suggestions
Your suggestions will not be acted upon here by Spotware.
@firemyst
firemyst
26 Jun 2024, 07:39
( Updated at: 26 Jun 2024, 08:05 )
This issue with freezing while back testing has been reported by others.
There's also separate threads of the new cTrader ‘freezing’ just running cBots.
It was raised the end of May (nearly a month ago as of this post), and Spotware has yet to resolve the problem.
Other threads:
https://ctrader.com/forum/ctrader-algo/44014
https://ctrader.com/forum/ctrader-algo/44016
https://ctrader.com/forum/ctrader-support/43974
https://ctrader.com/forum/ctrader-algo/44215
@firemyst
firemyst
26 Jun 2024, 07:35
( Updated at: 26 Jun 2024, 08:53 )
Would be great if you'd post this in the forum where suggestions actually belong:
https://ctrader.com/forum/suggestions
I would also include a screen capture showing the text you would like ‘bigger’
@firemyst
firemyst
24 Jun 2024, 10:17
( Updated at: 26 Jun 2024, 05:47 )
If not, please provide the version-up products after confirming that they are completely safe to use. Users are in a lot of trouble.
The quality and reliability of the cTrader platform product is important. If bugs occur frequently, the cTrader platform will lose the trust of its users and become less competitive with other companies.
This is so true. There have been many issues and bugs that should have never seen the light of day. It's like Spotware's Developers don't even use the product or have any dedicated quality control / test engineers.
If Spotware had their own cbots running in a test environment, this bug should have been picked up by their team loooooooooong before being released.
What's worse is how much longer it's taking critical issues to get resolved. This freezing issue was first reported end of May. It's nearly 30 days later and it's still not resolved. Totally unacceptable! Not only can we not run bots safely now, a lot of users reported the issue using the backtest functionality. These are what sets cTrader apart from the rest and when these key aspects can't even be trusted…
If Spotware ever gets around to cleaning up this mess, they need to look internally and either start removing people who aren't doing what they're supposed to be, or actually creating a team to do this and ensure a quality product gets released.
There's now at least 3 threads on this issue, plus it has been brought up in the Facebook cTrader group as well:
https://ctrader.com/forum/ctrader-support/43974
https://ctrader.com/forum/ctrader-algo/44016
https://ctrader.com/forum/ctrader-algo/44014
@firemyst
firemyst
24 Jun 2024, 09:24
RE: RE: RE: RE: My ctrader freeze when i'm using my cbot
PanagiotisCharalampous said:
Your broker should have an older version of cTrader
Is the latest release supposed to fix the issue? My cTrader was just updated to this version today:

@firemyst
firemyst
17 Jun 2024, 09:13
Best practices are generally not what you described, but more like how specific parts of indicators are implemented.
- For instance, there's been plenty of examples posted in these forums (that I've commented on) where people do the “GetBars” on every single tick. Bad!
- Or where people have an expression like “x * 3” a dozen times throughout the same method. Bad!
- Or where people draw a horizontalline, trendline, or other line, that only changes once per bar, on every tick. Bad!
Lots of things like the above (to name a few) will affect performance. Maybe not enough for users to notice it, but they unnecessarily use up cpu-cycles from the rest of cTrader.
@firemyst
firemyst
13 Jun 2024, 03:37
This has been like this since forever. It isn't a bug, just a use case that was never considered by the Spotware team (I'm guessing)
I've gotten around this by creating a static variable in my custom indicators they all reference when printing out messages. You'll have to manage thread-concurrency issues to make sure no two indicators are writing to it at the same time, but this can be easily overcome too by using a built in thread-safe structure like a ConcurrentDictionary or using global flags.
@firemyst
firemyst
06 Jun 2024, 12:46
( Updated at: 06 Jun 2024, 13:53 )
RE: RE: My ctrader freeze when i'm using my cbot
PanagiotisCharalampous said:
scottylace said:
@firemyst thank you for sharing all of that information, I'm encountering a similar issue, running multiple instances (~6) of the same CBot seems to cause the app to completely freeze after 6 or so hours. The CBot logic hasn't changed since the 5.x.x version launches and it ran fine on previous versions with no issues
Hi scottylace,
Could you please also send us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
Best regards,
He probably can't. He said the issue causes “the app to completely freeze”, which is the same issue everyone else is having.
cTrader completely freezes, meaning users cannot provide that trouble shooting information through the cTrader app because we can't click into the area to send it, or even get the cTrader app to respond – as per the link to the private video link I sent the Community@Spotware to see the issue first hand.
Have the team not been able to reproduce it with all the information and code I sent? I did another test today, and cTrader froze completely for me once again today. We're going to need a rollback soon if the issue isn't resolved because people are losing the ability to run their cBots.
@firemyst
firemyst
04 Jul 2024, 03:08 ( Updated at: 04 Jul 2024, 06:39 )
I also don't like now how all the “Start buttons” for bots are the same color, so you can no longer tell if you're starting a bot for demo or live account based on its color (previously demo accounts had blue buttons and live accounts had green buttons). To compound that, a user can no longer go by the account shown in the top right, but has to look at every account next to every instance they want to start.
Each bot instance listed now also takes up twice as much height as before, so as you say when you have a lot of bot instances there, it's double the amount of scrolling and such users have to go through now with little additional information.
I would be totally happy if they just rolled back to the latest 4.8 version – at least that would fix the bugs that have been introduced since version 5 and still affecting core functionality.
EDIT: I don't know if I add any weight since I have no relation to Spotware other than being a vocal user in these forums :-)
@firemyst