Posts made by roar

there is something better already - try the "history" button on upper right

@bossx
In the builder, you see the menu on left: first there is constants, then there is variables. These are the lists of constants and variables.
Read more: https://fxdreema.com/help/working-with/constants-and-variables

I used a simple formula to calculate the values - after trade the formula calculates a new variable that is bigger than the old one, and then it replaces it.

In the "on Init" tab you see a small system that resets the sequence to the first lot amount. You can copy those blocks to your Ontick process to reset whenever you need

https://fxdreema.com/shared/sj5zjSuL

but you should reset the sequence at some point, yeah ?

In other words, the 4 pairs can say if the ea trades or not?
You will need global variables, so the eas can talk to each other

your link doesn't work
while in builder, go top-left, Projects -> Create a shared copy

@roar said in FRACTALS DEFINITION:

https://fxdreema.com/shared/xzRcbD5db

i modified the example to store the fractal prices, and then compare them to candle0

this one. at least appears to me

yes, yes, i did just that

https://fxdreema.com/shared/xzRcbD5db

i modified the example to store the fractal prices, and then compare them to candle0

here.
https://fxdreema.com/shared/XLFjbWlcd
it checks once per bar, if there is a fractal.
if it is fractal up, it modifies the variable to 1
if it is fractal down, it modifies the variable to -1

now you can just check the variable value, is it 1 or -1

block 9 is actually useless, because the variable must be 1 if it is not -1 (except beginning, its 0 then)

this example doesn't care about candle 0, it just checks fractal states. if you need the fractal's price, not state (up or down), you will need more variables to store that price data.

Fractal formation is something like up, up, top (arrow paints here), down, down.
So the fractal appears on candle id 2

So you want the ea to remember the last fractal state, was it up or down? This can be done with a variable.

by default, thats how every ea works. every tick.
maybe you are using "once per bar" block or testing with model "open prices only" - just change these to work every tick

@fxfun said in MT4>>MT5:

• Using all CPU cores for calculation and backtesting in 64-bit, can make it 500% faster.
• Partial order filling
• More Pending Order Types
• Built-in Economic Calendar (Programmable triggers for news events, I suppose. If Yes = Great.)
• Order Depth.
• Backtesting multi-currencie EAs at the same time etc. Multi-threaded. Multi-currency. Real ticks.
• Better reports.
• More Timeframes (finally).
• More markets, like stock exchanges.
• Native SQL Export.
• Distributed computing (multi server power) etc.

I totally agree with you, I would prefer MT5 over MT4 any day
Couple more pros:

• position netting (at least it suits my particular needs)
• better strategy tester interface
• more reliable backtesting
• ability to use fxdreema's comment block to track variable values while visual testing (i need dis)

I remember the admin saying he hates mt5 because he has to deal with its retarded coding, luckily we users don't

yeah, "once per bar" definitely is slower than every tick action.
But in my opinion, every ea that needs to work faster than once per bar is 100% bullshit

it shouldn't lag 2 candles with this setup

Yes, if you use "once per bar", you should use id1, because id0 would always have only candle-open data.

indicators are just calculations based on some candles. you see, everything starts from the price.
so you can think candle id is actually same as indicator id

my example would surely work for the buy part.
unless you test "once per bar", then you have to use older IDs - replace id1 with id2, and id0 with id1

yes, you want the bear candle to be id1, and bull candle id0

https://fxdreema.com/shared/Kd93k3tR

I think the desktop version is not updated anymore.
But there's a simple way to work around the problem, just use some temporary variable.
Like this: