Problem with remote desktop

Created at 27 Sep 2023, 12:41
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
FX

fx.pro

Joined 08.03.2016

Problem with remote desktop
27 Sep 2023, 12:41


I have problem with access to my remote pc via remote desktop (Microsoft or Google). CTrader makes some refreshing and:

  • change cpu cores to about ⅓ of all,
  • backing any sorting of optimization passes to default
  • and remove any custom button created by my cbot, the only way to restore is restarting cbot

Can anybody have same problem and found a way to fix it ?

Thanks,

P.


@fx.pro
Replies

PanagiotisChar
28 Sep 2023, 05:23

Hi there,

How can somebody reproduce your problem?


@PanagiotisChar

fx.pro
28 Sep 2023, 06:45

RE: Problem with remote desktop

PanagiotisChar said: 

Hi there,

How can somebody reproduce your problem?

Hi,

it's quite easy.

a) run any optimalization via remote desktop, change cpu core usage to 100% and/or sort results by any cryteria,

logout from rdp session and login, you should see problem

b) or run cbot in real mode, draw buttons in “onstart”, logout and login,

In my case this object (border→stackpanel→button) was reduced to “0” dimension (i see small dot with colour of my border).

This problem starts about year ago after some update of cTrader. Before works without problems.

I checked 3 pc with 3 different os (W10,W11, Windows Server 2016).

Best Regards,


@fx.pro

fx.pro
28 Sep 2023, 11:52 ( Updated at: 21 Dec 2023, 09:23 )

RE: Problem with remote desktop

PanagiotisChar said: 

Hi there,

How can somebody reproduce your problem?

Simple Trading Panel :

before

after


@fx.pro

fx.pro
28 Sep 2023, 15:51

RE: Problem with remote desktop

PanagiotisChar said: 

Hi there,

How can somebody reproduce your problem?

Problem solved,

cTrader only works properly with Teamviewer.

Best Regards,

P.

 


@fx.pro

ekalyvio
25 Jan 2025, 11:54

The problem is not solved…

I have the same exact problem with an Azure Virtual machine. Connecting via remote desktop it reduces the CPU usage to 33%.

It is quite easy to be tested. Run any optimization test on the bot. Leave it running and disconnect from remote desktop (ensure you have the CPU usage at 100%). Reconnect and see the slider has gone to 33%…

Unfortunately due to such issue we can't optimize bots that could take up to a week or more to be optimized (as in this case it will take 3 weeks)…


@ekalyvio