Have two different machines where you run your bots. Keep one running the “old” code, and use the other machine as your development machine where you can compile, run, rerun, and do whatever with newer versions of the code.
Or if you're using the cloud option, make sure to turn off the syncing.
TWiLiGHT_FX said: Doesn't work, if I delete the cBot or Indicator off my system & Synchronize, it retails all cBots & Indicators previously Sync'd on their server..
Of course it does. Because when you turn sync back on, it syncs everything. I don't think you get to pick and choose which ones sync and which ones don't.
However, if you have it on a separate computer (another laptop? VPS?) it will only sync what's on that computer. What I do is on VPS I only have the bot I want synced in the cloud; on my local laptop, I run bots I don't want synced in the cloud, and have disabled syncing on my local laptop; syncing is enabled on my VPS.
@PanagiotisCharalampous can you add any clarifications around this?
This does not delete cBots/Indicators synchronized by mistake. Can someone at Spotware please let me know how we can remove unwanted cBots & Indicators stored in the cloud please.??
Sorry I meant delete the cBot, from cTrader itself, wait for everything to sync, then disable the synchronization.
This means you'll have to reinstall the bot on cTrader after you disable the synchronization when you've deleted everything.
I believe you just disable them after deleting them from cTrader. Make sure you have a backup copy. Delete from cTrader like normal when synchronization is ON. When bots are synced and deleted, then disable synchronization:
You can start with either Google or going to the menu at the top of the forums, clicking on “Algorithms”, selecting Indicators, and doing a search. Same with bots.
If you can't find one, then you'll have to code one. However, cTrader doesn't give you the ability to have multiple SLs on the same position. Instead, in your code you'll have to draw lines on the chart where the SL is (to see it visually) and in your code have it reduce the volume of the position (or close it all together) when price reaches/passes your SL line.
The other thing you should do is look through the Suggestions forum:
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 :-)
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?
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
08 Jul 2024, 00:29
Have two different machines where you run your bots. Keep one running the “old” code, and use the other machine as your development machine where you can compile, run, rerun, and do whatever with newer versions of the code.
Or if you're using the cloud option, make sure to turn off the syncing.
@firemyst