The Beast stirs. He's got a slope.

[fxozgirl]

I have LookBackDays set to 20 (which I think is the default). My crim is AxiTrader. The difference between our charts is significant which would mean we will have quite different results.

Just checked mine is 20 as well, have you run the force history script?

[SteveHopwood]

I saw why there are no Bunker buy trades as soon as I looked at the code. Usual thingy - copy/paste bloop.

V 1b attached here.

[slowkey]

I saw why there are no Bunker buy trades as soon as I looked at the code. Usual thingy - copy/paste bloop.

V 1b attached here.

Thanks Steve ...

[slowkey]

Steve,

I did a quick run of bunker all by himself no other element turned on. He made 172 short trades and 821 long trades over a year, 90 percent winners but the problem is that the 10 percent of loosing trades makes him a looser. The average winner was 1.91 and looser -34.91 He makes a lot of small profits of 2 to 8 pips or so than will make a huge loosing trade. A little unrealistic to run him by him self but he is trading now and maybe just need his setting adjusted. I think he is too sensitive and taking to many trades so adjusting him some may decrease the amount of trades and increase the profit. I will look at that later to day after a nap. But the code is working as far as I can tell.

Doug

[cuzgeorge]

Hi all, Steve,
sorry, still cant help with the code, but here's an error in the pic about an integer value.
running slopey beast 1b since this morning.
hope this helps at least.
regards
cuz

[SteveHopwood]

Hi all, Steve,
sorry, still cant help with the code, but here's an error in the pic about an integer value.
running slopey beast 1b since this morning.
hope this helps at least.
regards
cuz

Bloody Hell fire, damnation and buckets of blood.

CrapMql4 insists that OrderModify() contains a ticket number declared as an integer. Global Variables, on which SB depends a lot, requires that the value it contains be a double. Gary said not to rely on the language making the appropriate conversion, 'cos it is crap, so I declared the relevant variable as a double. To make OrderModify work I had to declare a separate integer and copy the double into it.

Attached is V1c with the appropriate fix. I tell you, guys, the cowboys who mis-coded all this are in for trouble if I ever meet them.

Cheers George. Nice spot.

[cuzgeorge]

Thank YOU Steve, and for the quick-fix, will run on chart immediately.
cuz

[garyfritz]

CrapMql4 insists that OrderModify() contains a ticket number declared as an integer. Global Variables, on which SB depends a lot, requires that the value it contains be a double. Gary said not to rely on the language making the appropriate conversion, 'cos it is crap, so I declared the relevant variable as a double. To make OrderModify work I had to declare a separate integer and copy the double into it.

You're kidding me. It gave you a RUN-TIME error!?

In a proper language, it would automagically convert the double to a int, basically doing automatically what you did by hand.

A stupid language would give a compile error because it's too dumb to do the conversion. But it also generally gives you a language construct to force the conversion.

But to compile it without error, and then at runtime say "whoops, this isn't an integer" -- that's braindead.

It sounds like you need to be really careful with MQL. It's too stupid to do the right thing so you have to do it yourself. Be careful to use the right type for parameters -- converted to the right type of variable if necessary, like you did.

[SteveHopwood]

CrapMql4 insists that OrderModify() contains a ticket number declared as an integer. Global Variables, on which SB depends a lot, requires that the value it contains be a double. Gary said not to rely on the language making the appropriate conversion, 'cos it is crap, so I declared the relevant variable as a double. To make OrderModify work I had to declare a separate integer and copy the double into it.

You're kidding me. It gave you a RUN-TIME error!?

In a proper language, it would automagically convert the double to a int, basically doing automatically what you did by hand.

A stupid language would give a compile error because it's too dumb to do the conversion. But it also generally gives you a language construct to force the conversion.

But to compile it without error, and then at runtime say "whoops, this isn't an integer" -- that's braindead.

It sounds like you need to be really careful with MQL. It's too stupid to do the right thing so you have to do it yourself. Be careful to use the right type for parameters -- converted to the right type of variable if necessary, like you did.

Hehe. I am reasonably sure I have said this before, Gary. Welcome to my world.

[fxozgirl]

fxozgirl
The charts you posted have the 6th lines plotted at different levels to mine on all charts except GBPCHF which is the same as mine. I understood that the EA plotted these levels. I was wondering if you changed these manually?
Karl

Hmm...I have thought over this some more and realised this is more to do with how the sixth lines are drawn...either UseMax or UseChaserL

I have used my settngs for so long I had forgotten about this until macman posted above. I'm not sure if there's details in the beast user guide, alternatively you could go back to the original thread at FF and read up on it further there.