I switched over to the new bridge (unzipped, refreshed in MT4) and my Zorro instances all started displaying multiple prices in the Server Window while trading. It flicks rapidly between different assets and consistently has an exclamation mark next to it. Switching the tracked asset around a few times seems to stop the flickering but the exclamation mark remains.

I had a look at my server and it turns out MT4 is murdering all the CPUs with the new plugin, which may be related to the exclamation mark. I downgraded all of the MT4 instances to bridge 1.8 and CPU usage went back to normal.

I am testing the new bridge on my VPS. Running my own script with which I detected this issue originally. Seems to be running OK thus far. Will report back later.

Also, I am trying to run the test script that support supplied. It will no longer run on the same MT4 platform that it was running on with the old bridge and returns the following error after clicking 'Trade':

testScript compiling..............
Login MT4...
!Katalon Market Holding Pty Limited connected at UTC 22.03. 01:14

Loading EUR/USD prices.. no history!
No bars generated
Logout.. ok

Not sure what's going on there. Something of a mystery since this script was running just prior to updating the bridge. In addition, my own script is running on the same MT4 terminal using the new bridge at the same time. I am running Zorro S V1.42. And I confirm that I have updated the DLL in the Plugin folder.

For me too the CPU usage looks unusually high after installing the new bridge. Zorro is now consuming 50% more memory than the MT4 terminal (!), which is itself a very resource hungry application.

This implies that I wouldn't be able to run more than 1 or 2 Zorro instances on my VPS.

jcl, can this be improved?

To be clear, for me at least, the CPU usage is all on the MT4 side of the bridge. Zorro didn't seem to be unusually bad itself but each MT4 instance had a full CPU core pegged (and these aren't pushovers, they're all on a Xeon E5-2687W).

The Zorro memory consumption can not be improved by a bridge version, but by using less series in the script.

The CPU usage by MT4 with 1.9 is indeed 30% higher - with Bridge 1.9 it's 5.5% CPU load, compared to 4.1% with bridge 1.8. This can be reduced on the MT4 side by setting eventsetmillisecondtimer() to a higher value, like 100. And on the Zorro side you could reduce the load with a higher ticktime, but that would not be noticable since the Zorro CPU load is normally in the 1% area.

Katalon did not work for us anymore since Sunday, unrelated to the bridge. We assumed their server is down. But we'll check that again.

We're still having the same problems with Katalon. Sometimes it connects to their MT4 server, but after a few minutes it reports "Invalid account". This is unrelated to the bridge, it happens with just plain MT4. A new account can also not be opened. Whatever it is, it could be the reason why the historical data was unavailable.

I have been connected to Katalon via my original script all day. Nothing strange printed in the log file. But when I hit 'Result" I get the following chart, which is really strange:



It looks like it is now registering a bad tick on the downside. The chart is also printed from 17 March - the script was only started earlier today (22 March). The EUR/JPY chart at least shows some clean price history, but again it doesn't show the price history from when the script was started. I am not zooming the plots in the script.

I get the same message as before when trying to run the test script that support provided on a different broker via MT4 bridge 1.9:

testScript compiling...............
Login MT4...
!Royal Financial Trading Pty Ltd connected at UTC 22.03. 10:33

Error 053: EUR/USD unavailable!
No bars generated
Logout.. ok

I can not see a downtick in your chart, but it is hard to tell due to the low resolution. I see a yellow line from an indicator starting at zero. Can you check if there is really a downtick or not? Maybe during the weekend? The start date of your chart depends on your lookback period.

So why does the test script that worked fine on V 1.8 no longer work on V 1.9? What has changed? Its not the broker since I am connected to them via the bridge (different script) right now. Plus I have tried it on a different broker and got the same result.