vipin.bhatia
12 Jun 2023, 09:44 ( Updated at: 21 Dec 2023, 09:23 )

RE: RE:

vipin.bhatia said:

firemyst said:

To make sure Spotware gets and receives this, please also report it through cTrader:

 

In the text box, put the link to this thread.

If you can, also put in the technical details from the event-viewer you captured as well.

A windows update after the clean install of .Net Framework, runtime and cTrader fixed the issue.

But now there is a different error, after 4 to 6 hours cTrader crashes, the screen goes blank. To access the computer I now need to RDP into the machine (VNC based solution will continue to show the blank screen) and there I can see the error WeFault.exe (0xc000012d).

Attached is the image, can anyone guide me on how this can be fixed.

Thanks.

vipin.bhatia
11 Jun 2023, 10:56 ( Updated at: 21 Dec 2023, 09:23 )

RE:

firemyst said:

To make sure Spotware gets and receives this, please also report it through cTrader:

 

In the text box, put the link to this thread.

If you can, also put in the technical details from the event-viewer you captured as well.

A windows update after the clean install of .Net Framework, runtime and cTrader fixed the issue.

vipin.bhatia
09 Jun 2023, 00:09

RE:

Hi,

Can someone from cTrader support confirm this bug.

Thanks,

Vipin

driftingprogrammer said:

Hi,

After the new updates to cTrader it has completely stopped rendering unless the windows desktop on which it is running is directly connected to a monitor. I have multiple desktops and only one monitor for emergency to check. I access my multiple desktop computers using VNC solutions like Teamviewer or Google Desktop Sharing. Lately after some update cTrader just shows a black screen unless that particular desktop computer is connected to the monitor making it impossible to use it remotely. Once I go physically to the desktop machine and connect it to the monitor the remote session starts rendering cTrader normally.

 

This needs to be logged as a bug, unless this is solved I will be forced to buy a monitor for each and every desktop computer I have in order to access the computer remotely to use cTrader.

 

Please let me know how I can log this as a bug.

 

Thanks,

Warm Regards.

vipin.bhatia
12 Mar 2020, 20:16

Is it possible to increase it

Is it possible to increase it to like 70% rather then the default 50%. I would feel so much safer having to risk only 30% rather then 50%.

Thanks.

vipin.bhatia
10 Mar 2020, 15:56

No Problem

PanagiotisCharalampous said:

Hi driftingprogrammer,

This happens because

Bars tempBars = MarketData.GetBars(TimeFrame.Minute15);

does not return any values in OnStart(). Unfortunately getting past bars from other timeframes is not supported at the moment in Optimization. You can only get bars from other timeframes that are constructed during the time the cBot is running. If your cBot logic allows it, here is a workaround to consider.

using System;
using System.Linq;
using cAlgo.API;
using cAlgo.API.Indicators;
using cAlgo.API.Internals;
using cAlgo.Indicators;

namespace cAlgo.Robots
{
    [Robot(TimeZone = TimeZones.UTC, AccessRights = AccessRights.None)]
    public class NewcBot : Robot
    {
        [Parameter(DefaultValue = 0.0)]
        public double Parameter { get; set; }

        protected override void OnStart()
        {

        }

        protected override void OnBar()
        {
            Bars tempBars = MarketData.GetBars(TimeFrame.Minute15);
            if (tempBars.Count > 0)
            {
                Print("Printing tick volume " + tempBars.Count);
            }
        }

        protected override void OnStop()
        {
            // Put your deinitialization logic here
        }
    }
}

Best Regards,

Panagiotis 

Join us on Telegram

 

Hi Panagiotis ,This code works and can be backtested, so I would assume 

MarketData.GetBars(TimeFrame.Minute15);

is working fine in OnStart.

Like you mentioned MarketData.GetBars(TimeFrame.Minute15); will anyways not work during optimization, well that is not a problem at all, I can just form my own candles, I prefer them anyways since they are more accurate because I can form timeframe datasets from my present position and not depend on the predefined timeframes of 6, 6:15,6:30,6:45 etc...

Thanks for letting me know, I can go ahead and modify my code but it would have been awesome if there was a warning being printed in the log similar to the one that shows up if you query for the Depth of Market in backtesting.

If I cant use the code inside the optimizer then I would not use that code at all but I would like to point out that MarketData.GetBars(TimeFrame.Minute15); fails intermittently during backtesting, usually for much older dates. It being an intermittent issue lead me to assume it had something to do with the historical data. After removing it I am assuming I will not be facing those intermmitent crashes. 

Cheers.