Posts made by fxDreema

Ok, I change it in your way, I hope nobody will complain about that

Aaaaa you want SL to remain untouched. Well, it's not a bug, it's how I decided to be. I don't remember why I decided that. Normally if you say to the program to set SL to 0, it will clear it. But maybe it's better for the trailing stop to not touch it. I don't know, there is a chance for someone else to ask "Why when I set trailing stop to 0 it does not clear it?"

I tried this (on MT4 and MT5), with Trailing Stop set to 0, and as a result my stop was removed. Isn't this what you get?

The trailing stop block checks all trades one by one if their stop needs to be moved, and moves it when needed. This happens on every execution of this block. Recently I added this option "Trail what?", so now you can use that block to trail take-profits. One for stop-loss and another for take-profit will work fine.

Here is how to use this block: https://fxdreema.com/demo/mt4-trailing-stop
basically, make it run on every tick. In your case you can connect 2 blocks one after another somewhere under "on Tick", they will work.

This time filter works in the first 5 days of the month Try "Weekday filter" with combination with "Hours filter" or "Time filter".

With time filters, it should work. What project is this?

Interesting, I don't know why was that happened, but I know that there was some maintenance on the server, so maybe from that. Repaired?

You can use as many Trailing stop blocks as you want... well, until they start to beat each other. Inside you can choose to trail SL or TP

I saw another topic from you today, but for some reason it disappeared. On that project I got only buys, because there is no chance to reach the condition for sells when there is some buy trade around

Now if I have to do that, I have to replace the block because both ways are... let's say incompatible. But I have plans to make them compatible somehow.

Otherwise you can just write down the variable from Formula. Well, then in case you remove the Formula block you will probably get an error message. I can also suggest to try Variables.

This block, like all the other blocks with the same (pink) color are designed to work only after some of the "For each...." blocks! You have it after Break even, so the result from it will be... who knows.

Trading model:

• if Ask is X pips above the open price in case of Buy trade
• if Bid is X pips below the open price in case of Sell trade

Chart model:
-the same for Buy trade

• if Bid is X pips ABOVE the open price in case of Sell trade
  So here you don't care whether the trade is Buy or Sell. If Pips away is positive value, then it will detect when the current price goes X pips above the open price, and if negative value - below.

Double-sided model:

• If the price goes X pips away from the open price above or below, for Buy or for Sell

Oh boy, I have to reorganize your project completely again in order to understand what is going on Now what is not working? Some errors, weird behaviour?

You can use some variable which for example has values 0 or 1, and if it is 1 then that means the ALERT condition is on. There is a category of blocks "Flags" basically designed for such situations, but as I said the word "variable", you can use regular variables as well (look at the Variables).

Normally under "on Tick" everything is repeated on every tick, it's not like many people expect - every next block to wait for the previous to pass. No, there is no waiting

https://fxdreema.com/shared/pIFxAq1ud

And maybe "Once per bar" can be used somewhere, or some Candle ID can be 1 instead of 0... it depends.

In block 7 you should input some indicator, not Candle Close 0, I think it does not work because of this block.

https://fxdreema.com/shared/aa3gSlc9e

The main problem There is something that goes out of control in 277 where you divide that variable and also use it there, at some point the variable is becoming 0. My suggestion is to do /10000 somewhere else, probably where all the variables (including this one) are associated with values.

You are using some variable named "grid_space_var_II" in blocks 289 and 292, which has value 0 when it reaches 289. Inside 289 there is some endless loop (that I have to check) which causes the EA to hang. I will fix the problem with the loop, but there should be some value that is bigger than 0 for "Round numbers detector" anyway.

Well, if you look at the code you will most probably be confused. There are many different variable names and they can have certain values that you don't know. So I will not recommend to dig deeply into the output code, better try to do whatever you want to do in fxDreema I think that the output source code can be used to find problems, at least I use it only for that, but I also know the structure.

If there is enough interest and the platform is good, why not. I don't know personally what Ninja Trader is capable of, and I think it is also not free... wondering what will they say if someone is using their name in their products

With custom code only, not possible in Condition.