Posts made by fxDreema

Probably input parameters are not correct. Here is what I used and it works for me: http://prntscr.com/3voovo
Here is some test: https://fxdreema.com/shared/ywfH0oDJd

I think you should work with candle ID of 1 or more, because at 0 it gives EMPTY_VALUE (a very big number) all the time. try block "Indicator appear", or something else from "Indicators" category.

Is it working from the web version? I tried with "Draw Arrow" connected after (on trade) blocks, and it seems to work.
This, for example: https://fxdreema.com/shared/n88cGa4ed Here I work only with Group 1 and I have this result: http://prntscr.com/3vfcji
The very last local build (085) must be the same as the web version now

Well, the closed trade has "parent" trade even if you close it for the last time. To resolve the problem I added function to get the "child" ticket, so now there are 2 checks. I think purple blocks are enough

Arrows are objects, you can load objects and get some info from them, but this is not exactly a signal. Maybe some signal can be detected under "on Chart". Indicators should give their data and signals to the EA using their buffers. And when that is true, you can try those blocks in "Indicators" category. For example, "Indicator appear" is to be used with some biffer that represents arrow or line that is sometimes gone, sometimes present. Also "Condition" block, if it's something simple. And to be aware of what some indicator gives to the EA, use "Indicator tester" block to visually print data of one of it's buffers.

Project data is also saved in .mq4/.mq5 files, so you can import from them later. XML is... I think I will remove it.

Uuuummm, I think it will be better if everything is in the EA, so there will be no need to change input parameters all the time. Or two separate EAs, if one is not enough.

Haha yes. The reason is that the Condition block is a little bit locked... when I have to change something in it I need to change many other things as well, so I don't even want to think about this Otherwise this request is not something new, it's from the very beginning. But on the other hand when you have 1 block per condition, all conditions are clearly visible... ok, this does not sound very convincing

Run it as administrator and make sure that output directories are correct - they can be different if MetaTrader is in normal or portable mode.

True, it has weird problems sometimes, I see this "compression error" for the first time here, but I'm not surprised. If nothing helps I am available with TeamViewer, maybe I can try to make it work.
And now I'm gonna give you a free month because of these problems.

There is no special block or option for this, so..
https://fxdreema.com/shared/RaI9c8jTc
Well, not very elegant. I didn't tested it

There is a block to set SL to open price when there is some profit. If you want to know when certain trade is close to 0 after it was on profit before, without using stop-loss... well... this will be hard to do, because arrays and variables are needed, and this will work until the EA is running That's why in general, working with something solid like SL, TP or any other parameter that is part of the trade even when the EA is closed, is better

If you mean something else, give me more detailed description

Magic number is just another property of all orders, like stop-loss, take profit, symbol, type, ticket number, lots... but it's nowhere visible. You know that in MT4 you can run multiple EAs at once, but in the same time all orders are in one single pool, visually. So, the magic number is the property to allow every EA to recognize orders placed by it and to not touch others. Of course, if you have two EAs, one for EURUSD and another for USDJPY, then you can recognize orders by symbol name and no magic number is needed. But when two or more EAs work with EURUSD we must have something else.
And Magic number stays with the order on the server, so if you restart MT4 or even go in different MT4, that number will be there and the same EA will be able to continue working with it's own orders placed before.

Well, this is just a number after all, and I extended it in fxDreema to this number called "Group", so in the same EA we can place orders with different magic numbers. There is input parameter MagicStart, and the real magic number that order will take is MagicStart+Group. That Group number is 0 by default, so the real magic number that will be taken by default equals to MagicStart.

This is when you place order, for example with "Buy now". MagicStart is considered.
When searching for order, for example with "No trade is running", I added some more options, look at the "Group mode" parameter.

Because I don't really understand point 3, do you have problems detecting when to place the trade? I mean... do you detect your breakout successfully?

Ahaaa! Now it should be ok

What about the "AutoTrading" button?
For the EA to work with only manual trades, set Magic Start Number in the Project Options to 0... I think it will work. Or "MagicStart" input parameter that comes with every EA. Both are the same thing.

I don't really understand what are the breakout rules, but here is something for the 2X part: https://fxdreema.com/shared/8nZymUnhc
Before Buy now, SL is calculated as the difference between ASK and ZigZag. The result is something like 0.0023, which is what I call "price fraction". In Buy now I used this directly, I named the global variable "SL".

Some day...

I think you need to know (and feel) how things work. Indicators are arrays of data, what the EA knows are all indicator points in the past - there is 1 point with value for every single candle. So RSI can move up/down in the current candle, but when that candle ends, RSI freezes at it's last state and only this value remains.

So how to know when RSI goes from 75 down to 70? It depends, for what time? The easiest thing is to look at the previous candle and the current candle. Or in the last X previous candles? Or you don't care if it reached 75, you may want it to just cross the 70 mark, which can be detected easily - by looking at what was the last RSI value and comparing it to the current value. Or Looking at the value in the previous tick and comparing it to the current tick (if it was above 70 just a while ago and now it is below 70, then it crossed below). The last thing is also a little bit tricky, because this event may repeat few times in few seconds, because the price always moves up and down.

In short - it depends. What I posted above is some easy way to detect such a crossovers, but you may have different requirements, or none, as very often we don't know what we really want, or the thing we think we want can be made in much simpler way.

So... what calculations do you need exactly? But looking at your project... I don't know it looks too weird for me to use tens of blocks to make something that can be explained simply as "crossover".

I can suggest to play with Condition block and blocks in "Indicators" category a little bit. For example, place "Indicator rise" -> "Draw arrow" and see what will happen. Then try something similar with another block. Also use "Indicator tester" to see how indicators work, what values they give to the EA. All this in Visual backtest mode

casebefx, what have you changed in Windows? Basically fxdreema.exe wants to have full access in MT4/MT5 files and folders, because it wants to write those files there, but newest Windows versions are a little bit of weird, more restrictive and "protected". Set fxdreema.exe to run as administrator, this is the best suggestion I can give.

Also make sure that you write files in the right output directories. Because now MetaTrader can work in "normal" or portable mode, and what is normal is to have experts in some strange looking folder somewhere deep in AppData. Here is a topic I wrote about these problems before: viewtopic.php?f=2&t=2374

The local version is actually Server + Chrome Browser + Web App (fxDreema itself) all packed into single .exe file using 3rd party software. And yes, it goes heavy and slower with more and more blocks, as every web page goes heavy and slow when it has to print many data. HTML/CSS/JS is normally heavy stuff, especially in last years. But it was at least 10 times as bad few months before! Back then 100 blocks were enough to make it respond slow, but I spend some time to optimize those processes and now it's in the best way I can make it.

When you click to generate output file, then PHP starts to work to combine all blocks into a single file. This is where things can break, but on the server side.

What I can suggest... to make everything in a better more optimized way. But I understand that this requires experience Building projects in fxDreema is like programming, but without writing code. What bad programmers do is to use the same code again and again, to do copy/paste of the same things and use them two or more times with little differences. Eventually they end up with some code that is big and hard to understand, aka "spaghetti code". The best is if 1 part of code is written at 1 place (as function) and used multiple times, so there are not tons of different copies of the same thing. But again, this is hardcore, not easy. This is what I do for the last year - I solve problems like this, I'm getting deeper into how to make something as simple as possible, as accurate as possible, as lightweight as possible and as flexible as possible. Hardcore

Learn to use loops (cycles) and to reuse things (blocks, small groups of blocks). When you need to use big group of blocks (more than 3-4 blocks) more than 2 times in the same project, this is big red alert - the same result can be achieved with less blocks for sure! If they does not exists, if something can be added as functionality... this is one of the things I am here, so ask me

Uuuuum Try again?