uvwxyz
11 Aug 2018, 08:32

RE:

procumulative@gmail.com said:

anybody else has same problem? dont hesitate to tell us here...

Thank you guys, glad to know i am not only one having issues with performance in the new version of cTrader.

Seems like my new computer arriving in few days, with i7 (6 cores), 16GB RAM, 256GB SSD will not do any difference!!! Will keep you posted. I always thought it was the new version's implementation of new Graphical API was the problem. We dont need fancy tools but fast efficient tools. Or is it that some kind of brake goes on after certain nubmber of open charts???  I hope Spotware solves this issue very soon and continue their great pioneering work. Cheers.

uvwxyz
28 Jul 2018, 15:02

RE:

Panagiotis Charalampous said:

Hi uvwxyz,

Could you please post more information about your set up? What indicators do you use? How many charts do you have open? Can you share a screenshot?

Best Regards,

Panagiotis

Hi  Panagiotis,  I appreciate your early reply, thanks Panagiotis.

I am only using my custom indicators. 

 I also observd that when i had no instance open, the CPU was still very busy, 0% to 25%. All my indicators had been previously been succesfully compiled with no errors. This suggests to me the new update is trying to recompile the indcators; There is no way i can go back and change all the indicators to not use the obsolete API. That would take just too long.

After the new version download & the problem i encounted with slow scrolling of chart, I removed all the indicators except few, out of the cAlgo/Sources/Indicators folder. I closed all instances except one,   & i  had 8  indicators open below this chart (I opened the same indicator again and again, 8 times).  There was no improvement. Scrolling along the charts was not possible.

It appears that some of the problem may be with the slow implementation of your new API , in particular the new "Chart.DrawVerticalLine", & the obsolete "ChartObjects.DrawVerticalLine", ie as below:

      //Chart.DrawVerticalLine("endSell" + ind, ind, Color.Yellow, 3, LineStyle.Solid);
      //ChartObjects.DrawVerticalLine("endSell" + ind, ind, Colors.Yellow, 3, LineStyle.Solid);

When i disabled these as shown, the problem disappeared, and i could scroll smoothly along the chart with 8 open indicators.  The newer Chart.DrawVerticalLine would crash my indicator when i had 8 indicators open; the obsolete ChartObjects.DrawVerticalLine wont crash it, but strangely,  was far slower than how it performed before the Ctrader update of last week. These vertical lines are the essence of my indicators, aiding me to analyse and experiment in building my final strategy, which i was very close to before this problem stopped everything for me.

I am using : Processor: Intel(R) Core(TM) i5 - 3320M   2.60 GHz    2.60 GHz.        RAM of 8.GB.   Display adapter are: Intel(R) HD Graphics 400 (updated drivers) & RealTek WiFi Display VGA adapter (  updated driver).

If the problem in faster implementatiion of the newer API can't be solved,  or whatever the problem is cant be solved, can i possibly please, use the previous version for building and experimenting.  Then when i am ready to  build my final indicators that wont use these graphiccal visual tools, i will use the newer version of CTrader, Calgo. The last version was working just fine for me. This is totally not.

Thanking you for you assistence very much, i advance.

uvwxyz
10 May 2017, 13:07

hi,

try: 

    [Output("willPlotTheSeries_R ", Color = Colors.Yellow, LineStyle = LineStyle.Solid)]
     public IndicatorDataSeries willPlotTheSeries { get; set; }

        private IndicatorDataSeries willNotPlotTheSeries;       
     
        protected override void Initialize()
        {
            willNotPlotTheSeries= CreateDataSeries();

        }

//this will create 2 indicatorDataSeries, one will plot and and one will not.

Hope this helps. Cheers.
           

uvwxyz
07 May 2017, 12:13

Hi ROBO, 

Perhaps try:

recreating those indicators in ver 2.01. Hopefully you know the parameters values and type them in (or they  are as in the indicator code). Then delete the old indicator attachement. 

Ver 2.01 corrected this bug.

Cheers.

uvwxyz
05 Mar 2017, 03:15

RE:

tmfd said:

Hi,

 

What are the new features?

 

Thanks

Hi,

My comment wan't about the new features, but about making some of the old features work again. In particular, for me to continue using my custom indicators i needed  to be able to change the indicator parameters manually @ runtime. This is now possibe again. It's a simple feature but without it, custom indis can be crippled. ( There may well be new features in the the update, i havent gone thru it thoroughly.)

cheers.