Posts made by fxDreema

I don't even know how this indicator looks like, It can't work for me because an indicator called "TVI.ex4" is missing. But you should know what 2147485647 means and how to deal with it. And the short answer is - don't deal with it, you probably can't. I made "Condition" to not pass at all if one of it's operands eauqls to this number, this is also true for other blocks. So, use indicators when their value is something else. I'm not sure what is the question you want to ask me and I'm also not sure what to tell you, because I know you are here for long time and I because of that you must be one of these who knows everything even better than me.

So you end up profitable using fxDreema?

http://prntscr.com/7r9bvq
Or get High or Low from the candle in higher timeframe when possible

I just fixed those warnings (web version), but I don't think that they are responsible for stopping the EA from running. Well, I don't know what you mean by "it stops"

Well, my only touch with indicators is when someone is asking me how to work with some

This indicator uses another one called "TVI". It depends on what values it gives you. What kind of values do you receive from this indicator?

I think I don't have problems here, or at least not now. Here is what I tried: https://fxdreema.com/shared/OIpVq19Ad
And I set my Renko like this: http://prntscr.com/7qu4kg So I should have the same timestamp for a big row of candles. But Actual times are like this: http://prntscr.com/7qu5w9

What times do you have? I think the chance of having the same values for Volume in tho neighbour candles is bigger. By the way I'm talking for times because "Once per bar" knows recognizes a new candle by it's time.

Mmm I think there is no way to make object invisible, but I'm not sure. In these blocks I added all of the possible parameters available in MQL, or I am not aware of something else that can be added

96 or not, it depends on the selected timeframe for this calculation! And it's probably very good idea to select one if you are using this functionality. Otherwise there is similar, but using Time instead of candles. Or the simplest - use High and Low of Candle 1 in Daily timeframe

I don't know whyblock 6 and 11 are used, but be careful with "Draw..." blocks - their frist 2 settings are very important for the way they handle objects. In the case you will have a new line on every bar with name like step_line_buy + appendix.

Renko chart? I'm not working very often with offline charts, to be honest I lost track of the problems with them, but I will inspect this if you really think that there is a problem

Block 79 now wants to see 25 candles (in a row) where their Low is below BB's Low (for each independent candles). Just try this with lower number of candles.

You can also have "once per trade/order". This block has it's own memory and it does not care of anything else. Maybe it tried to create Buy (from 31) and it failed, then 22 will not pass again for the given trade. I don't know what happened there, there are many possible situatuins, this is just one of them.

Error 133 means Trade is disabled. Can you at least put a new trade manually?

Check current unrealized profit -> Close trades

For MT4 you can use Virtual stops by the way. Somewhere in the projects setting you can enable these. They are horizontal lines, but the EA keeps track on them and closes trades when needed. Of course, the EA must work for this to happen. But also you can set Emergency stops along with the Virtual stops, which are hard stops placed somewhere beyond the Virtual stops, just in case something goes wrong.

I tested your EA and the object looked fine, all the levels that you entered appeared on the chart. If you think that something is wrong, then show me some screenshot.

Here is what I have: http://prntscr.com/7pl9lm It updates every day.

Moving average will be calculated at 15:30 anyway, it's not important for indicators to be "used" before or after they are really needed and used. The first time the EA access to an indicator, it already knows it's all current and past values. Indicators are also independent from the EA in some sense.

You know... now "Round numbers detector" will works fine if the EA is restarted. This is a rule that I want to follow in general, this makes the whole EA more predictable. There are now some blocks that will reset if the EA is restarted - all flags, counters and "once per trade/order" - they all keep it's current state in local variables, which are cleared in case of restart. I don't like these blocks very much because of that. So I'm not really convinced to do such modifications to "Round numbers detector".

When you use Variables, at least you know from the beginning that they are temporary and you expect them to be cleared when restart. And there are some alternative ways to store information - in a file, in Terminal Variables, in chart objects. When I am saying objects, I can suggest to use horizontal line - you can create and keep modified the same line using only one block (Draw Line) and you can easily check it's value. The same line can be controlled from multiple Draw Line blocks as well. Plus, a horizontal line is something visible and it can be modified from the chart.

In you example the connection between 4 and 3 is probably wrong. You don't know what will be loaded from block 4. It will not be a trade for sure, but it will be some pending order, one of all if there are many. When you use pink block, always use "For each....". I mean, always, especially in MT4. And not visually above, but logically before.

I just added new mode in Trailing stop (each trade), MQL4 only, web version. I marked it as experimental because I'm not sure about it. You can test it and then tell me if it's ok and what should be different.

How it works... you write levels like this:

20/5, 30/10, 45/15

.. which means that when the profit reaches 20 pips, SL will be set to 5 pips (from the Open Price, not from the current price!), at 30 pips of profit SL will be set to 10 and so on...

It's also important to write groups in order starting from the minimum value. 20 first, then 30, then 40... But not 20, 40, 30. This is because MQL4 is very unfriendly when arrays are used and I don't want to add more calculations for sorting.

"Step" is still working. By default it is 1, so we actually have 21/5, 31/10, 46/15. I can exclude it from this mode and set it to always be 0, but... I don't know, people always want more options.

What I don't like in this way is that all numeric values are written in a single string, which means that it will be very ugly if someone wants to use some variable instead. That's why I marked it as experimental.

Otherwise similar functionality can be made using multiple pink blocks. Something like:
For each trade -> pips away from open price -> once per trade/order -> modify stops
but not only this, there must be multiple "pips away from open price" blocks and they must be ordered starting from the biggest profit. Yes, this is also ugly.

Well, obviously the % values that you enter are going to be the Description for each level, this is how I made it. Custom names... where can I put this in the options so it can be intuitive to be used. If you want price values that will be automatically updated, this is another story.