Posts made by roar

@FPorelli the id variable gets its value here, no need for anything else

I would guess just change this number in the code.
Alternatively, just run a visual backtest.

@gooseman ok, if MA has a variable timeframe as well, its better to use slightly different structure.

1. Start with the market selection loop
2. Record the currently selected market into "market" variable
3. Run a checkup in custom block: if market is this, set timeframe to this and set rsi target level to this
4. Apply the found timeframe to every next block
5. Run the MA and RSI conditions with the previously selected variable timeframes and target levels

https://fxdreema.com/shared/nvVoaSASc

@gooseman so you have different RSI timeframes and different RSI levels for each symbol?

In that case, I would first record the RSI on all timeframes into their own variables, also record the currently selected market, and then do the symbol + RSI check in one big condition block.
For the syntax, && means "and", || means "or".

This doesnt compile since I dont have all your variables, but I hope you get the idea
https://fxdreema.com/shared/D0LMD4Hnc

To avoid the unnecessary loading of all RSI timeframes for all symbols, you could first do a checkup for the correct TF for the selected symbol, but it is not strictly needed

@VanceDavid this is mainly an issue with Metatrader itself, there is not much Fxdreema EA builder can do about it.

Check this: https://www.youtube.com/watch?v=3T3XZDy5Vk0

Just put the market loop on top. Dont use the other filters - symbol or group - in other blocks.

If you have special settings for each symbol, then you need an array.

@FPorelli like this: https://fxdreema.com/shared/oMA9J5TZb

@ZakTrading before using pink blocks, you should always select your trade with the purple loop block. Sometimes a trade might be already selected and the pink block works alone, but it will cause bugs if the last selected trade is not what you wanted

Every object is listed in Objects list, and you can search through it in a loop

Basically you can just use the ChartOpen function: https://www.mql5.com/en/docs/chart_operations/chartopen

https://fxdreema.com/shared/h3f6nEY3

Tick data can be expected to take 10x more time...
Fxdreema projects are inherently slower, but there are some performance optimization you can do:

• move the "once per bar" to the top of your flow
• dont use the yellow (false) output of the "once per bar" I think its just a mistake in your project
• "close positions" block is known to cause infinite loops, see here: https://fxdreema.com/forum/topic/16494/close-positions-when-market-is-closed

Do you use tick data or rough data?

@talshemtov you need to declare a new constant for each MA setting. Find the correct enumeration from mql5.com:
https://www.mql5.com/en/docs/constants/indicatorconstants/enum_ma_method

@Crispypata just use this bad boy here

Datatypes (int, bool) are lower case

Like this, for example

Those price constants are determined by mql5 themselves: https://www.mql5.com/en/docs/constants/indicatorconstants/prices

"Average" might not be the optimal term there, but the calculation is correct nevertheless

@Mantadiver you have 10000 unique blocks without any pattern among the blocks?

If not, I'm willing to bet you can reduce at least 70% with some new structuring. You up for it?

https://fxdreema.com/forum/topic/16310/when-to-stop-oninit

Admin has already answered on this issue, there is no problem in their view

Only the orange output activates once per bar, yellow activates on every tick

@fxDreema thank you!