Topics created by james

Actually the reason of this logo to be there is not advertising, but recognizing that the EA is made with fxdreema. And it was fun for me to create it. In fact, this logo exists only in the MQL4 part, for MQL5 I was too lazy to create it 😆 And it can be easily removed from the output source code - it exists somewhere in "init()".

Also, I think that EA creators (in general) are good to quickly build some strategy and backtest it, but for professional use it's better to write the strategy in MQL4/5 from scratch. Because EA creators are made to be universal, the biggest part of the output code is trash. At least this is the case with fxDreema, I can admit that. Yes, the EA can work, but every EA can be written with less code from someone who knows how.

Well, I will add some option to enable/disable if this is what many people wants. This is already planned update 🙂

OK. No problem! 😄

Oops, missed that post 😳

I have no idea why is this happens, and again... if I see it here, I will fix it, but I don't know how to replicate it on my PC 😞

1.5 GB free memory.

I'll get back to you regarding access to my PC. Not sure if I'm permitted to allow it!

@haidang8055 I'm afraid this is not my field of expertise, sorry. Maybe miro or any real programmer could help with that.

Ok. Now I understand. Thanks very much for taking the trouble to assist me - and sorry for the silly question!

Thanks for the very quick reply, fxDreema.

I was using downloaded tick data from Dukascopy, and transforming it into MT4 history files using the excellent Tick Data Suite.

After I'd done some more research on this problem I decided re-install everything, and also give another broker a go. The first broker confusingly called its pairs GBPJPYSB (spread bet), whereas the second used the normal GBPJPY (even for spread bet). The tests seemed to work fine with the first broker (99%, etc) apart from the "Tester: exchange rate cannot be calculated" error at the start.

The key, therefore is the name of the pair. If the name of the history files don't exactly match the pair name the broker gives them (in my case GBPJPYSB instead of GBPJPY), then this error occurs.

Birt (of Birt's eareveiw.net - home of Tick Data Suite) said: "Just for future reference, FXT files created while connected to a broker that uses a suffix for the currency pair names will not work properly on brokers that do not use a suffix and vice-versa. In case you have to perform such a switch, you either have to recreate the FXT using the new broker or you have to hexedit the FXT and remove the suffix (or add it)."

Hopefully this information will assist someone else in the future who stumbles across this problem, and searches for an answer.

Anyway, all's well now.

Thanks again.

Hi

Great! 🙂 Thanks. That seems to be working now! 🙂

Thanks again.

Yeah, I noticed that before 😄 And it is something that I think for.

To go to the source code while using generator is something that doesn't make much sense. What you are doing is doing it whatever it takes, and that is very good 🙂