It uses your cBot's timezone. If there isn't one set, it's UTC+0
Well, that's annoying. According to the way it's implemented, if I wanted any cBot to log in local time for the time zones I go through because I travel often, I would have to update, recompile, and redeploy the bot every single time I cross a timezone to update the bot instances with the timezone I'm in?
Who decided that?! O.M.G. face palm
cTrader can certainly determine if the cBot is running locally (and not in the cloud), and can also determine if there's a timezone set or not.
If I start a cBot on a VPS that's set for my local time zone running an instance of cTrader bot locally (not in the cloud) set to the current timezone I want to use, then why doesn't the bot, by default if no time zone is specified and it's running locally, use the local time zone?!
It makes more sense to use the timezone the user has selected in cTrader in than a default UTC+0.
Speaking of issues, look how much more memory this new version requires. I used to be able to run 2 copies of version 4.18 on a VPS with 4GB of ram and still have plenty of memory space left over.
Now when I start 2 copies of cTrader 5.0.xx on a VPS with 4GB of ram, there's only like 740k of memory left. The VPS hasn't changed, so it can't be blamed on Windows.
If you had a total of 10 lots, how do you expect to have two take profits of 9 lots each? That in itself is 18, which is more than the 10 you have.
If you want any help, then maybe you should try specifying what your order actually was and what the original lot amount was when you entered your position.
We had no luck reproducing this issue therefore we cannot fix it at the moment.
Best regards,
Panagiotis
It's still doing this as of today, April 17th with version 4.8.30.
Doesn't the @Spotware team want to remote desktop and/or something else to get to the bottom of it? It's OBVIOUSLY an issue since I can reproduce it and have provided several videos showing it happening and can still reproduce the issue at will.
It happens when I switch between saved templates on an indicie (like the NAS 100) with a broker that has a pip size set at 0.1 points instead of 1 point on that indicie.
//Now the time data is stored in the haTimeFrame variable. Put this in your “OnStart” or “Initialize” methods depending on whether you're writing a bot or indicator so it only gets the data once. If you put it in OnTick or Calculate, it's going to waste valuable CPU and network bandwith trying to reload the data on each tick.
Because that appears to be a custom indicator you are using… if you know how, you need to import them into your project or add them as a reference in Visual Studio.
Hi firemyst,
Thanks for your reply.
I am new to this, how would I import tem into my project?
Many thanks
Gary
Why do you need to use the custom indicator and not use the built in heikin ashi candles instead?
Maybe because they want to see the HA candles on a regular candle chart? I sometimes do the same thing.
There's also numerous indicators that do this as well as are quite popular.
firemyst
28 May 2024, 06:49
RE: Log window not showing the correct time
PanagiotisCharalampous said:
Well, that's annoying. According to the way it's implemented, if I wanted any cBot to log in local time for the time zones I go through because I travel often, I would have to update, recompile, and redeploy the bot every single time I cross a timezone to update the bot instances with the timezone I'm in?
Who decided that?! O.M.G. face palm
cTrader can certainly determine if the cBot is running locally (and not in the cloud), and can also determine if there's a timezone set or not.
If I start a cBot on a VPS that's set for my local time zone running an instance of cTrader bot locally (not in the cloud) set to the current timezone I want to use, then why doesn't the bot, by default if no time zone is specified and it's running locally, use the local time zone?!
It makes more sense to use the timezone the user has selected in cTrader in than a default UTC+0.
@firemyst