To be clear, it means no leverage with cryptocurrencies on the cTrader platform?
Edit : Regardless of the version of cTrader, regardless of the currency, whether on the demo account or my FTMO account, i cannot use leverage. And there is apparently nothing I can do about it.
The leverage is decided by the broker, not by the platform
Can you please provide more information about this issue e.g. steps to reproduce and some screenshots demonstrating what you are looking at?
Best regards,
Panagiotis
Hi
You can also test yourself in the backtest section; Add the Keltner Channels indicator and you will see that before starting each robot; The opening of the indicator is, for example, 50 pips away, but immediately after the start of the robot and the revelation of new candles; The opening of the indicator will quickly get closer to each other and it will show, for example, a distance of 5 pips. Photo 1 that I have attached is before the start of the robot and photo 2 shows shortly after the start of the robot. The same problem caused the robot that I wrote earlier based on this indicator and it worked correctly; It is now disabled after the recent update. I tried some similar indicators but they did not have this problem.
Thank you. We managed to reproduce this behavior and we will fix it in an upcoming update.
You need to check your symbol's leverage as well, through the active symbol panel, not only your account's leverage.
Best regards,
Panagiotis
Hello,
Thank you for your response!
Here's a screnshot of my symbol window. It seems all the crypto symbol are set on 1:1 leverage (forex has more than 1:1 leverage). (It's on Windows, but same problem on my Mac)
Edit : Same problem ("not enough money") with a demo cTrader account, despite the leverage in the window symbol :
It is done. I think I'll uninstall and reinstall it as soon as I have the time. That should fix the problem.
I have forwarded your video to the team. Please let me know if this fixes the problem.
Also could you pleasesend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
Can you provide more detailed information? Please share the cBot code and screenshots of the error message you receive so that we can reproduce this problem.
Are there any plans to allow traders to manage/access to their cloud space? This would be great
No plans at the moment
I see.
Cloud execution is not yet an alternative for cBots that need to access to files, I assume?
Any workaround?
No, for now cloud execution is designed with specific limitations to assure smooth execution of all cBots on the cloud. Risky operations like network are file access are limited at the moment. We will make further decisions after this first release is evaluated.
Thank you for reporting this issue. Unfortunately we were not able to reproduce this behavior. Could you pleasesend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
No you cannot. As firemyst suggested, you would need a different setup for such a scenario. In principle, dev environment should be different to your production environment.
Hi
I belive It used to be fine until now. I don't understand why was the change in last version. There's no sense of forcing a reload in the middle of a run. I suggest you change it back to the way it was.
Thanks
I want to emphasize this point. A part of the developing is actually running the bot while developing and modifing it at the same time so it's impossible to seperate running a bot and developing. Especially when running it on backtest. The auto-reload doesn't give any addded value, only cause complications
Hi there,
There are technical reasons that led the team to implement this and there are no plans to revert this change, therefore you should adopt the way you work.
PanagiotisCharalampous
11 Jul 2024, 06:34
Hi there,
This is by design. Calculate() method is executed once for each historical bar and then for each tick during real time operations.
Best regards,
Panagiotis
@PanagiotisCharalampous