Unfortunately we were not able to reproduce the problem. Positions amount shows correctly for us
Best regards,
Panagiotis
Panagiotis,
Can you please check this under the same conditions (broker, symbol, etc) ?
This way you'll be (obviously) more likely to be able to reproduce the issue.
Remark: It has been already noticed in the past that many issues that applied to indices were not applicable to forex.
Thanks.
We did but with no luck unfortunately. We will keep it in mind though in case we stumble upon it in any other occasion
Panagiotis,
I really don't understand how you're not able to reproduce this issue.
Try the following backtest settings and let me know. Using the exact same cBot code and backtest settings I can't expect anything else than the same outcome.
thanks for your reply and I'm quite sure you will be right ;-)
But I still wonder why the chart history is different to backtesting history data.
So for clarifying 3 questions and I hope I don't bother you, if that is explained in doumentation you could provide me the link to it:
Chart-data/TimeFrame.M1 => what is the source format the broker provides? Tick-data or directly TimeFrame.M1-data?
Backtesting-data/Source: M1 from Server => what is the source format the broker provides? Tick-data or directly TimeFrame.M1-data?
Backtesting-data/Source: Ticks from Server => The source could be only the Tick-data, right?
If your answer to point 1. and point 2. is the same, the problem ist probably not at the broker side, but between 1 and 2 is a difference.
So considerd that your answer above “talk to IC Markets” is right, I guess cTrader gets all broker data (for Charts and Live-Bots) only by ticks and makes/generate all longer timeframes as M1, H1 etc. by it's own - only that would explain that “Backtesting-data/Source: Ticks from Server” and “Chart-data/TimeFrame.M1” gets the same result. Based on that and if that would be true, “Backtesting-data/Source: M1 from Server” have to be a different source by the broker, am I correct with that?
Thank you and best regards,
Bernhard
Hi Bernhard,
If your chart data is different to your backtesting data, try cleaning your backtesting cache in C:\Users\[USER][\AppData\Roaming\[BROKER]\BacktestingCache. If the issue persists, please talk to your broker. It is a bit pointless to try pinpoint the source of the problem yourself. The price feed is a responsibility of the broker. Even if this is a cTrader issue, we cannot intervene unless the broker asks for it.
I managed to eliminate the requirement of AccessRights.FullAccess. I create not the url i want to use and then i use Http.Get(myurl) to send the message.
This works still when i run the cBot on my computer, but does not work when i run it in the cTrader cloud.
Does this mean, Network Access is not working when a bot is started in the new cloud?
Hi, I also have the same problem. Did you fix the problem or not? Thank you.
Hi there,
Network access is not permitted for cBots executing on the cloud.
When the price of US30 is 40,000, I buy US30 using ExecuteMarketRangeOrderAsync(TradeType.Buy, US30, lot, 10, Symbol.Ask + 100, MyLabel, stopLoss, stopLoss * 10, comment); my base price should be 40,100, and the range pips are 10 points. In theory, the transaction should only be executed when the ask price reaches 40,099 or 40,101, but in practice, it is executed immediately. Why is this RANGE restriction ineffective?
Hi there,
No, this is not how it works. Market orders are executed immediately. This is way they are called market orders. If you need a pending order use a Stop Limit order.
Best regards,
Panagiotis
thank you for replying!
The issue I'm encountering is: when placing an market order, marketrangepips can limit negative slippage , but it doesn't limit positive slippage. For example, when I'm buying, the price at the time of order placement is 40,000, and the marketrangepips is set to 10. However, if the price suddenly drops to 4, which is very favorable to me, so it filled at 4, I don't want the order to be executed. It should only be executed within the range allowed by marketrangepips. Does the marketrangepips parameter only limit negative slippage, or does it limit both positive and negative slippage? What I want is that the positive slippage can also be limited though the price is favorable to me, this function can prevent potential reversal after sending an maket order at exceptionally active market conditions
Market range only limits negative slippage.
Is it possible to implement a function to limit positive slippage?thank you.
Hi there,
You can suggest it in Suggestions. Nevertheless I don't think it would be a popular suggestion as I personally do not see the reason of limiting positive slippage. I can't think why you would not want a better price for your order. It's like rejecting a discount for a product and insisting to pay the actual price.
We do not have any plans to upgrade to .Net 8.0 at the moment.
Best regards,
Panagiotis
BUMP!
Hi Panagiotis,
cTrader has become my preferred algo. trading platform.
Knowing that support for .Net 8.0 will not be provided leaves little choice in progressing with c# coding of cBots for every cAlgo programmer. Sad!
Perhaps cTrader staff would reconsider this decision with enough support for the concept from the cTrader community?
Hi there,
I don't think so. Upgrading frameworks requires substantial resources that need to be redirected from other useful features. Resources are not unlimited hence if we do this, we won't do something else. Therefore we will not do this if there is no substantial value to be added to the platform. For example, at the moment we prefer to develop the R/R tool than upgrading to .Net 8.0. When we see that it's time to upgrade e.g. require some feature from the newer version, we will do it.
In the Telegram channel, cTrader team told me that this value updates instantly and report any issues here.
I am seeing 52% short for XAUUSD nearly more than 3 days now.
It is not updating on IOS or Windows desktop. I am using icmarkets real money account.
Is there a problem? Is there anything i need to do?
All the Best
Hi there,
The fact that the sentiment does not move for some time is not a sufficient indication of an issue. It could just be that the sentiment is stable. I will monitor this over the next week.
Execution issues should be addressed by your broker/prop firm. Please reach out to them.
Best regards,
Panagiotis
Hi Panagiotis,
Thank you for your response. I reached out to the prop firm, and they mentioned that there's nothing they can do about it, even though my TP was hit a few seconds before the SL.
Best regards,
Hi there,
Unfortunately we cannot help you with this.
Best regards,
Panagiotis
Hello Panagiotis,
Thank you for your response. I understand that my request may be outside of the usual scope, but could you please confirm whether my understanding of the trade execution is correct? Specifically, I would like confirmation on whether my Take Profit (TP) was hit before my Stop Loss (SL) in this case, and if so, whether it should have been prioritized in closing the trade.
I would like to have this confirmation from cTrader, as it will help me address the situation with my prop firm, Funding Pips. I appreciate your support in clarifying this matter.
Thank you for your time and assistance.
Best regards,
No I cannot confirm this. A Sell TP is triggered by Ask prices while the candles are drawn using Bid prices. So the candles themselves is not a sufficient evidence of an issue and a wide spread could be the most probable reason of what happened. But this needs to be confirmed by Funding Pips who controls the execution.
Execution issues should be addressed by your broker/prop firm. Please reach out to them.
Best regards,
Panagiotis
Hi Panagiotis,
Thank you for your response. I reached out to the prop firm, and they mentioned that there's nothing they can do about it, even though my TP was hit a few seconds before the SL.
PanagiotisCharalampous
15 Oct 2024, 10:00
Hi there,
I do not understand your problem. What is Capiix? What is exactly that you are trying to do? Can you provide more information e.g. screenshots?
Best regards,
Panagiotis
@PanagiotisCharalampous