Posts made by Trader3487

maybe it's just something to do with mt4 testing mode

Can I set time frame in EA block to different time frame that chart is set to? For example, block in EA is set to M15 but mt4 chart that EA is attached to is set to H1. I tried running such an ea with mixed time frames in test mode on different time frames and it produced different results for each TF. It seems like each TF is blind to other TFs so if I set a M15 in one of the blocks and the EA is running on an H1 TF, it won't pick up the M15 instruction. If that's true, then is there a way to have TF setting in block mean true for that TF even if chart is on different TF?

Can you please restore "less than N Trades Open" block. This was very useful. Thank you

ok, so if I am understanding correctly, it is the same indicator located in "mt4\experts\indicators" but you update the custom indicators interface in fxdreema?

When I upload custom indicator Awesome.mq4 into fxdreema desktop version, it only shows 2 buffers (0 & 1). Just to make sure, the custom indicators are located in "mt4\experts\indicators" directory right? I already have Awesome.mq4 uploaded into fxdreema web version but I don't remember where I got it from and don't see how to download it.

Thanks

James, I think this might be what you are looking for: post/4948

this is amazing, thank you! Exactly what I was trying to figure out the last 2 months! I just tested it and it works - http://fxdreema.com/shared/vPW2evoee
I am sure no other program out there offers the set of features and level of support that your does so I hope it gets wide exposure and lots more people come to use it!

great, thank you very much! So how do I make a condition block that says "if 0.0001 (4 decimals)" then follow orange output?

I could adjust the trailing stop size but I have more than 30 chart symbols now and each one is a condition block. Additionally, I have to add a regular version of the symbol name (ex. EURUSD) for standard trading account and a micro version (ex. EURUSDmicro) for micro account. Not all brokers use same naming system so I have to add another 30 blocks for different naming system (ex. EURUSDm instead of EURUSDmicro and XAGUSD/XAGUSDm instead of SILVER/SILVERmicro). That's 90 blocks that need a title and connections to and from those blocks and I have those blocks in 2 places in my ea (in the OnInit and in the main section), so it's just a lot of clicking and connecting not to mention if I want to add another symbol I have to add another 4 blocks. screenshot attached.

The reason I need put all these condition blocks for chart symbols is in order to direct the ea to the proper trailing stop block. I am using 3 primary different trailing stops (blocks #104, 105 & 106) based on the number of decimals of the symbol. It would be so much easier if there was just 4 blocks that said "if chart is x decimal places" go to x trailing stop block or even 1 custom block that determined how many decimals the chart was and then directed output to the correct trailing stop block

......
ScreenClip.png

thanks for that information. I added a condition block and went to "Market properties" > "Symbol (market name)" on the left operand. Could I put "MarketInfo(Symbol(), MODE_DIGITS)" into the adjust field?

the method I was using to the s/l in trailing stop block was making too many server calls because 1 pip was always less than the broker's minimum s/l requirement so the server would return a message like "s/l too short. using minimum s/l of 86 instead". And since the block was running every tick and trailing stop step size was 1 pip and there were 8+ charts open, those server messages were filling up the log. Thankfully, the broker covered the trades they closed

We are back to the drawing board here because my broker kicked me off their server for trying to dynamically generate trailing by setting s/l value to 1 (i.e. too many calls to their server). I resolved the server load issue by rebuilding the trailing stop with variables but having a block that determines point format of current chart (2, 3, 4, or 5 decimal places) is essential so if you would be willing to make it an option, that would be really appreciated. It doesn't look like a difficult task since the information is already provided here, I just don't know how to put it into custom condition blocks that I can use - namely:

condition block 1: if current chart is 2-digits, then follow orange output.
condition block 2: if current chart is 3-digits, then follow orange output.
condition block 3: if current chart is 4-digits, then follow orange output.
condition block 4: if current chart is 4-digits, then follow orange output.

Thank you

oh, that's a good point. I did try with visual testing but that explains why it was missing most of the crossovers using the == method. Would you be able to attach an example ea showing the crossover at candle id = 0, I tried putting it together but it still shows crossover a bar behind. Thanks

blocks are missing in example titled "Price crosses Moving Average indicator above" on example page and documentation page

thanks for the additional information. I also reviewed the crossover documention here: http://fxdreema.com/documentation/proje ... er%20works

Using the method you provided, it still looks like the crossover is being detected a bar later than it actually happens (crossover happens in bar 1). I am looking for a way to detect crossover in current bar, which I guess just detects when line A meets line B, i.e. MA20[0] == MA40[0]. I tried setting up an arrow on the chart with this condition but it did not work (it detects first 2 crossovers and then stops):
http://fxdreema.com/shared/uW1Mhf3se Any ideas why?

ok, a bit confusing but basically, it's better to use the second diagram (in Area #2) if I want to check for both conditions?

so when you say "Normal case with cross width = 1, MA5[1] x> MA10[1] selected", that means crossover is happening in previous candle. If I want to detect crossover in current candle, wouldn't it have to be cross width = 0, MA5[0] x> MA10[0] - but there is no option for zero?

assuming both condition blocks cannot be true at the same time, aren't these two saying the same thing? For some reason, I don't get the same results.

http://fxdreema.com/shared/xuCIAMo6

......
test1.mq4

got it now, thanks

Yes, checking a range of previous candles would be more useful.

just to clarify, the number 1 in candle[1] means current candle - same meaning but different numbering than close[0] where 0 is current candle?

so "new bar + cross width" is # of bars going back? See attached screenshot. And just to confirm - I know you said that the candles in between are not check - if crossover happened at candle 1-5, then statement would not be true?

......
cross width.png

sorry, I'm still not understanding. If cross width is not the number of candles to check going backwards, what unit of measurement is cross width - is it a time value where 3 is units of whatever timeframe you are in? Thanks