firemyst
24 Jul 2024, 02:45

It's already there. You just have to look:

firemyst
24 Jul 2024, 02:43

It would help if you're able to get screen captures next time?

firemyst
23 Jul 2024, 05:34

RE: RE: Orders getting triggered without price reaching that point

samchaudhary said: 

firemyst said: 

First of all, price is the BID line; your SL might have been hit by the ASK line. Do you have both shown on the chart?

 

Second, if you want money back, you have to talk to your broker. 

What's the solution for it?

 

Solution for what? If you want the ASK line shown so you can see when it hits your stop loss, have it displayed on the chart.

If you want your money back, as I said earlier, you have to try and speak to your broker. But I doubt they'll give you your money back if your order was taken out legitimately (eg, either by BID or ASK line)

firemyst
21 Jul 2024, 13:19

The highest index should have the latest value. The indexes in the series also coincide with the bar numbers on the chart.

You can test this yourself by reading the first value, the last value, and comparing against values on the chart.

In layman's terms, if the latest value was kept at index 0, cTrader would have to constantly rewrite the DataSeries updating all the indexes, which is very inefficient. Whereas, just tacking on the last value to the DataSeries List object is the most efficient way - the entirety of the list doesn't have to be constantly updated with each new bar.

firemyst
20 Jul 2024, 13:56 ( Updated at: 21 Jul 2024, 05:24 )

Maybe they're not visible on your charts because you haven't added them?

Just because an indicator is installed doesn't mean you've selected it to be shown on your chart.

firemyst
20 Jul 2024, 13:55 ( Updated at: 21 Jul 2024, 05:24 )

First of all, price is the BID line; your SL might have been hit by the ASK line. Do you have both shown on the chart?

Second, if you want money back, you have to talk to your broker. 

firemyst
20 Jul 2024, 13:54 ( Updated at: 21 Jul 2024, 05:24 )

PLease post your request in the correct forum:

https://ctrader.com/forum/suggestions/

This is a technical support forum - Spotware doesn't come here looking for suggestions to improve their product.

firemyst
18 Jul 2024, 02:47 ( Updated at: 18 Jul 2024, 05:55 )

See this thread:

https://ctrader.com/forum/cbot-support/43666/

firemyst
18 Jul 2024, 02:45

You need to contact your broker and ask.

firemyst
18 Jul 2024, 02:43

A follow up question: if Spotware can send out these messages advising us maintenance is underway, how come they couldn't send users out a warning that maintenance was going to happen shortly, eg, in 30 minutes or something? 

This way users could adjust their positions take any necessary precautions they needed to like closing positions or adjusting stop losses. I find it totally unprofessional the way this ‘maintenance’ was handled yesterday.

firemyst
18 Jul 2024, 00:27

Maybe you need to take time to explore and learn the platform because it's already there:

firemyst
16 Jul 2024, 06:08

RE: RE: RE: M1 Backtest vs Tick

ATBIN-ROBOT said: 

firemyst said: 

ATBIN-ROBOT said: 

All my bots have this problem and I think the reason is tick data.

Can trades with m1 open/close profitable settings be profitable and reliable?

Depends on your strategy and how it's implemented.

Can you explain more please?

There's nothing to explain. It depends on your strategy. Either your trading strategy makes decision on each tick, when a bar is opened/closed, or a combination of both. 

Some strategies are profitable; others are not, hence why it depends on your strategy. And then, you may have a great strategy, but not code it well. 

So as I said, it depends on your strategy and how it's implemented.

firemyst
16 Jul 2024, 04:03

RE: M1 Backtest vs Tick

ATBIN-ROBOT said: 

All my bots have this problem and I think the reason is tick data.

Can trades with m1 open/close profitable settings be profitable and reliable?

Depends on your strategy and how it's implemented.

firemyst
15 Jul 2024, 14:44

The reason is you're probably running M1 based on candle closed/open as opposed to tick data?

firemyst
13 Jul 2024, 12:27 ( Updated at: 14 Jul 2024, 06:31 )

For the latest and follow up discussions, see this thread:

https://ctrader.com/forum/ctrader-algo/44215

firemyst
13 Jul 2024, 12:26 ( Updated at: 14 Jul 2024, 06:31 )

For the latest and follow up discussions, see this thread:

https://ctrader.com/forum/ctrader-algo/44215

firemyst
13 Jul 2024, 12:26 ( Updated at: 14 Jul 2024, 06:31 )

For the latest and follow up discussions, see this thread:

https://ctrader.com/forum/ctrader-algo/44215

firemyst
11 Jul 2024, 04:02 ( Updated at: 11 Jul 2024, 06:24 )

Duplicate.

Conversation is occurring in this thread:

https://ctrader.com/forum/ctrader-algo/44354

firemyst
11 Jul 2024, 04:01 ( Updated at: 11 Jul 2024, 06:24 )

RE: calgo TIME ZONE IN THE CLOUD

ncel01 said: 

Oi thebeinvest,

This seems to be another issue (not consistent with cBots running locally).

As far as I can see this works as follows:

• Local cBot: 
  • Journal: Same time as defined in the UI settings.
  • Log: Server time as defined in the cBot code TimeZone = TimeZones.CenAustraliaStandardTime
    (UCT+0 by default, if this is not defined).
• Cloud cBot information (contains both the Journal and the Log, I guess)  :
  • UTC+0 is shown, regardless of both the time selected in the UI settings and the TimeZone defined in the cBot code.

For me, it would make a lot more sense that all the info shown in the UI was based on the DateTime as defined in the app settings.
On the other hand, when writing to .txt files (both Journal and Log), the TimeZone as defined in the cBot code (UTC+0 if this is not defined) should be always considered. This because, unlike the info shown in the UI, the info already written into a .txt fill will remain static and will not change when modifying the current time in the app settings. The time reference should also remain static.

I'd also like to hear from Spotware some clarifications on this.

I agree with your sentiment. I recently posted about an issue where I was running cBots and noticed the logged times weren't matching up with either the specified time zone in the UI or my local computer, and was told bots only read from “cBot code TimeZone = TimeZones.CenAustraliaStandardTime”, which to me is ridiculous in itself in that every time I want/need to change time zone when traveling or running against a particular market, I have to recompile and redeploy code. 

For me, it would make a lot more sense that all the info shown in the UI was based on the DateTime as defined in the app settings.
 

Ditto! I'm glad you and more users are saying something about this. 

firemyst
10 Jul 2024, 11:52 ( Updated at: 11 Jul 2024, 06:24 )

RE: RenkoAshi cBot trouble

Mike-JP said: 

The freeze bug of the cTrader continues. Users of cTrader are at risk due to the bug.

‘On tick' and 'Renko chart' cBot frequently freezes. I think it is a memory overfllows of tick data. I also mentioned in another thread that this issue can be avoided by the user limiting the number of bars in the chart. MT4 also allows the user to choose the number of bars in the chart.

Spotware should fix the freeze bug ASAP.
Best regards,

It also happens on Range Charts and Heikin Ashi charts… I'm sure there's an appropriate Dilbert cartoon about this…