I created similar thing because I can't see your project, and it seems to work here: http://fxdreema.com/shared/CD88sQECb
Note that TP as fixed size is calculated as TakeProfit-OpenPrice and transformed into pips, but if TP is below OP for buy trade, it will be incorrect. So, where is your TP in relation to OP for that trade? And what about other blocks - is "Start trades loop" pass?
Inside the loop you can access trade parameters in Condition in category "(in loop) Trade/Order in Loop", so you can use Condition to check the distance. Then you can close that trade with "(in loop) Close trade" block.
Or if you want to check the distance between the current price and SL, then "(in loop) Pips away from SL" can be used. At some point of view this is the real SL distance at the moment.
Maybe I don't understand what is the problem exactly, but I can see that you have two "Condition" blocks connected at the end, and they don't have a chance to work. In other words, blocks 4 and 7 are there for nothing.
There was some other EA builder (don't remember which of them) where blocks are connected in this way - actions first, conditions next, but in fxDreema the first to connect is the condition, and then action.
So, when you have Condition and it is true - it will execute next blocks connected to it. Not previous.
Maybe you should connect those conditions (4 and 7) after the other conditions, I don't know the strategy, but in any case yellow blocks should be above the green/red ones 
At least this one seems to work for me: http://fxdreema.com/shared/2FeRN6Cod
In demo:
2013.10.30 13:56:03 '1218115382': remainder of order #75764982 was opened : #75764983 buy 0.50 EURJPY at 135.187 sl: 134.187 tp: 136.187
2013.10.30 13:56:03 '1218115382': order #75764982 buy 0.50 EURJPY at 135.187 sl: 134.187 tp: 136.187 closed at price 135.159
2013.10.30 13:56:03 '1218115382': request in process
2013.10.30 13:56:03 '1218115382': request was accepted by server
2013.10.30 13:56:03 '1218115382': close order #75764982 buy 0.50 EURJPY at 135.187 sl: 134.187 tp: 136.187 at price 0.000
2013.10.30 13:56:03 '1218115382': order was opened : #75764982 buy 1.00 EURJPY at 135.187 sl: 134.187 tp: 136.187
2013.10.30 13:56:03 '1218115382': request in process
2013.10.30 13:56:03 '1218115382': request was accepted by server
2013.10.30 13:56:03 '1218115382': order buy market 1.00 EURJPY sl: 134.187 tp: 136.187
2013.10.30 13:56:01 Expert MT4 EURJPY,H1: loaded successfully
In backtest:
2013.10.30 13:57:42 2013.09.11 00:00 MT4 EURJPY,M1: close #1 buy 0.50 EURJPY at 133.178 sl: 132.178 tp: 134.178 at price 133.158
2013.10.30 13:57:42 2013.09.11 00:00 MT4 EURJPY,M1: open #1 buy 1.00 EURJPY at 133.178 sl: 132.178 tp: 134.178 ok
And I always end up with 0.5 lots
If it's really 3-trades scenario, I think it's better to group trades. If each trade is manipulated in the same way, then there is no need for groups.
"Start trades loop" may sound as something that creates loop (and it does that), but because you can choose to "loop" only one trade, after this trade is selected the loop will not continue with another trade. So, this block in this context can be named "Load last trade" or just "Load trade".
This block loads some trade, it reads it's parameters, and then you can modify some of them with pink blocks with names starting with "(in loop)". That's why I added this "(in loop)" - to know that this block should be used inside loop.
Also, parameters of that loaded trade can be accessed in the "(in loop)" section in "Condition" block or in other blocks that have options "Dynamic...".
These "(in loop)" parameters are somehow isolated, so you can use other blocks inside the loop - blocks that also have loops inside like "Close each trade".
Because "Start trades loop" is designed to be able to self-execute itself many times (for each filtered trade), when all this ends it goes to the yellow output, so the yellow output can be used to connect blocks that must be executed after the loop ends.
For MT4 I really recommend to always use "Start trades loop" (or other 2 loop blocks, if needed) before using "(in loop)" blocks or parameters.
In MT5 because position is selected by it's symbol this is not that mandatory, but in MT4 where you can have so many trades around, the EA must know with which one of them to work.
In MT4 you know you can have many trades at a time, but each one of them has fixed lot size. Closing part of it's volume is done with native MQL4 function, but it happens that the trade is first closed and then a new one is created (with volume size equal to the difference). So, if you have 1 lot and you decide to close 0.3 lots, this 1 lot is closed and 0.7 lots are openend. The newly created trade has different ticket number, but the same... I think it was the open time, or open price...
If you have trade with 1 lot, it should close that and reopen new one with 0.5 lot.
On the screenshot I can see opened trades, but how are they closed... or there are trades after closing... 
By the way, go to Options -> Project Blocks: Normalize IDs
Maybe you have different SL in both cases, but in the case where there is no trade SL is so small that makes lot size too big... and no trades is placed. You should see error message like "Not enough money to sell...". And then on the next candle SL is bigger and lots are small enough to open a new trade.
Error messages in Journal or Experts (when live trading) tabs.
Do you have error messages? And what project ID (or name) it this one?
Otherwise to check if conditions are fine... I use "Draw arrow" or other "Draw..." blocks, and also "Logic points tester" was made for this reason (but I found myself not using it). And if conditions are fine, but trading is not - then the problem is in the trading blocks. And I think that this is the case here.
Risk % of Equity is one of the volume (lots) option and it matters for the lot size of the future trade, it does not determine it's open price. But I don't think I understand the question.
What it point of entry? 
Use block: Counter: Pass "n" times
James, I will say this again - "Check distance between two levels" was not made to check only trade parameters, it was made to check two levels... no matter what levels. One level can be manually written 1 and the other can be manually written 2. This block does not select trades or orders and does not filter trades or orders, it just does not work with trades or orders, it works with two mathematical values coming from somewhere which in this block are called "levels".
What filters and selects trades is "Start trades loop" block, and it load only the last trade of any group, if needed. Then in "Check distance between two levels" you can choose parameters from "(in loop)...." category and this will be valid.
I can see that you are using trailing stop, so if you open fresh trade with fixed SL equal to the trailing stop... what's the difference, the stop is there anyway.
I used 3 groups because I understood it that way - everything starts with trade 1, trade 2 is placed by some rule (x pips above the 1st trade) and trade 3 is placed by another different rule (when SL of trade 1 is above OP). If trades 1, 2, 3 are closed everything starts again. So, maximum 3-trades strategy, or I can't see the rule to create more than 3. But I could be wrong. If the rule to open every trade is the same as for the previous trade, then no groups are needed.
Here on this forum they rely on me to get an answet
No, it's not "Close each trade", it's all about the conditions. And now they are exactly as you say, but note that Candle Close [0] is basically the current price and in the moment of opening the new bar is the same as Candle Close [1], so your conditions react at the very first moment when Candle Close [0] goes above/below Candle Close [1].
Try to compare 1 with 2 and 2 with 3. Also, where "Once per bar" is located (before or after conditions) also makes difference.
Don't focus on "Close each trade", it works as it should - when executed it closes trades you want... but the point is when it is executed?
Kamath, remember this email sent from me 5 days ago:
__Now you have:
Conditions -> Once per bar -> Close (Sell) -> Sell now
Conditions -> Once per bar -> Close (Buy) -> Buy now
so... what you have is that on every new candle you close old trade and open new one with the same direction.
This (http://fxdreema.com/shared/HhJKocjGd) creates trades like Buy-Sell-Buy-Sell on every opposite signal, but there are losses because... who says that when a candle starts to fall down (rise up) it will continue doing that at least until it closes. There are losses because sometimes after you receive signal that the candle goes up, it then starts to go down (and vice versa)[/quote:1lq41d2t]
Ah, and FXDREEMER also sounds good
This was some example that I used days ago to show something... and here you can see how buy-sell-buy-sell rule can be made without "Signals" block. This is the better way.
I don't understand this indicator, but I can say two things.
Buffers are always with some value, so I think you can't detect when certain color is present by asking if that buffer is > 0. But this can probably be said by comparing buffer with buffer... I notices that they overlap somehow, and I don't understand how, but it should be some rule for that.
About "Signals" blocks... each of them has internal memory that knows the last state, but this somehow makes them "soft" and not reliable. If the EA is restarted, all states are reset. So, if possible, don't use this block.
Such a flip-flop behaviour (to create buy-sell-buy-sell strategy) can be created with checking what type of trade is currently running in the moment when conditions happens. But if this is not your case and you only want to draw arrows... fine, no need to check trades.
Normally if the output folder is not correct, it should open Global Options automatically, or at least it should show you error message (message in red background that says that something is wrong). None of this happened?
It's true that I have to put a browse button, I have to check how is that possible with html because I still don't know how. But normally I copy/paste adresses (with Ctrl+C and Ctrl+V), so maybe because of this I don't see this as big problem... even when it happens very often for someone to write wrong MetaTrader directory.
Click on that "Empty" text and you can rename the project. When you create a new project, the first thing is to give it a name... and that name is used for the output file. I also have to make it possible to write custom file name, no matter what is the project name... but I'm not really sure if this is good idea.
What you should define in Global Options is the folder where MetaTrader is installed, for example:
C:\Program Files\MetaTrader 4
If you still have problems with this, I can help you with TeamViewer.