Multi 10:4 Trader EA

[MrLong]

Hi Traders,

I've fixed a few bugs and will upload v1.07 on Sunday Afternoon.

Thanks for helping with the bugs and have a nice Weekend.

Andy

[candletiger]

I'm getting readings of .00 on all pairs with RSI2. Can someone help out here?

seems something is wrong

[MrLong]

was kinda funny, it opened 30 audnzd trades and closed them instantly

Fixed.

[Sojourner]

was kinda funny, it opened 30 audnzd trades and closed them instantly

I got a bunch of the AUDNZD did the exact same thing on FXCM

[bubo]

Fabulous work, MrLong!

There have been several questions why backtesting is not working. I had the same problem.

Some things to watch out for:

(1) The EA calls kernel32.dll - make sure to have it in your library folder, and for backtesting in your \tester\file folder. Not sure how essential this dll is to EA performance. The EA also calls for user32.dll (possible that some reported problems are from people with 64-bit windows?).

(2) Calling MarketInfo() will make it difficult for backtests when there is no connection to broker or on weekends. We might have to bypass that with a simplified solution for 'IsTesting()'.

Having said that, I am still not sure why backtesting is not giving me entries. Or do calculations fail because we have only one instrument in Empty4 backtesting? It should be possible though to calculate NB 10.4 just for one pair.

[bubo]

ok here's another one..

i set the max pairs to 8.. it's opening 20 pending.

Good idea, but perhaps a Zeljko filter could be more meaningful to contain risk?

[snailbeard]

A very elegant EA

Runs smoothly on Alpari UK Demo, not stressing CPUs at all

However, on FXDD Demo, (same PC) never completes the dash board, (as others have reported)
also one CPU is flat out 100% (status:sleeping; pipe_wait), for over an hour

It seems to be very picky about something

I'll see if I can pin it down a bit more...

[MrLong]

Fabulous work, MrLong!

There have been several questions why backtesting is not working. I had the same problem.

Some things to watch out for:

(1) The EA calls kernel32.dll - make sure to have it in your library folder, and for backtesting in your \tester\file folder. Not sure how essential this dll is to EA performance. The EA also calls for user32.dll (possible that some reported problems are from people with 64-bit windows?).

(2) Calling MarketInfo() will make it difficult for backtests when there is no connection to broker or on weekends. We might have to bypass that with a simplified solution for 'IsTesting()'.

Having said that, I am still not sure why backtesting is not giving me entries. Or do calculations fail because we have only one instrument in Empty4 backtesting? It should be possible though to calculate NB 10.4 just for one pair.

string Pairs[] = { "USDJPY" }; <== Add your pair here.
Highlight this line out like: ///CreateSymbolList();
Then try your back test, but back tests are only historical fundamentals and may never happen again, so if Iraq were invaded and we were trading oil, the back test would run over this event, that's my beliefs anyway.
Best Regards
Andy

[MrLong]

was kinda funny, it opened 30 audnzd trades and closed them instantly

Fixed.

are you updating the link on the first page ?

Yes

[MrLong]

ok here's another one..

i set the max pairs to 8.. it's opening 20 pending.

Good idea, but perhaps a Zeljko filter could be more meaningful to contain risk?

at this point, the EA works great.. but not setting TP or SL.. so when it opens a trade, you have to manage it manually

If Stealth is true, then the EA will manage the trade, assuming the EA is running,