Topics created by iagnew

@iagnew In your right tree what are you delaying from? This tree will never activate because the left tree will always be active before the right, if the right is supposed to activate after the left make each block for each tree have a different group number, above the delay of the right put a if trade block containing the group of the left tree.

https://fxdreema.com/shared/rPCeO0jRd

There are a variety of ways to build a "remote control". A simple variant might be this one. It's only a suggestion, I haven't tested it. I only use MT5. 11 and 13 also control SELL. However, the indicator may only switch once, otherwise every tick is bought.

@iagnew , do you need all 7 conditions to pass before open a trade? Wow!

I'd do like this, connect all 7 condition blocks to a single AND block, then Once per bar, then Buy@Sell block.

Hi folks! To update this thread on bulky Project Saving/Syncing failures that may appear from time to time.

This typically happens to the extended Projects with more than 500+ connected Condition Blocks.

Not sure if the solution I've found was already described on this Forum or in any of the platform Manuals, but just for the Community contribution sake:

There is no need to store all the Condition blocks you've already built once in the same Project if those planned to be used for the future use on new Projects, as that entails that your Project will eventually become more bulky and unexportable.

In case anyone needs to use any of the older Condition blocks or some parts of the previous Projects you've already built, FXDreema actually supports Copy/Paste operations through the OS Default Clipboard BETWEEN THE DIFFERENT PROJECTS

Example: one can store his older Condition Blocks in a single "Archive project", occupying any of the Project tabs: OnInit/OnTick/OnDeinit etc for a later use on a new Project, and copy a certain Condition Blocks from the "Archive project" to any new project through the clipboard, when required

The only requirement would be the "Archive Project" must remain exportable, to make sure you always keep a local recovery backup copy.

This allows keeping the new Project lightweight, while retaining access to the older Condition blocks through an "Archive Project", thus the building and syncing operations on a new Project will be performed much more efficiently and quickly

Additionally, by organizing a personal FXDreema workflow according to the scheme described above, user can significantly optimize the time spent on EA testing and building operations, as he can always use parts of his previous Projects to start with or enhance on the new Projects WITHOUT REBUILDING SAME BLOCKS FROM THE GROUND UP each time

Hope that will help many of the aspiring FXDreema users moving forward

Sorry for drawing you back, if you can show a sample of the multiple condition connected by modify variable, the explanation will be much clearer. please help a friend. Thank you in advance.

@iagnew More like this: 0_1650795326562_094adfce-6d81-46e0-b3ef-0afb5ad80f6a-image.png

@iagnew You can use a condition block limiting your maximum accepted margin to trade.

@iagnew Use a variable instead of a constant, whatever condition you set to change this, will change the used lot.

@iagnew Yes so a tick could come in, this is what makes meta trader do something, just after the price is at the right point.

0_1643931762319_872845e6-4979-4380-a19b-28f21a5fac59-image.png

You may not need to do this, test to find out.

@iagnew You're welcome.

@iagnew Interesting. This means we can say 45 groups is the maximum number of groups than can be used effectiviely. Good to know. Thank you for sharing.

@iagnew The admin recommends to export the Ea into mq4 and then change the file extension manually into mq5. Then import it again to your account.

@iagnew you could create a variable that put true/false when your conditions happen https://fxdreema.com/forum/topic/11289/pass-one-bar-candle

Put the modify variables block

Or another way to do it, is with turn on/off blocks below/above your conditions

@iagnew https://fxdreema.com/shared/d4mmzmlXc

Yes, to rename that "mql4" folder to "MQL4". I have never seen this folder lower case before 😮

ucp.php?i=profile&mode=reg_details

or in the generator => Profile -> Profile info & edit -> Edit profile -> Change password

@haidang8055 No. None of them can be changed with Global Variables. You wil need 'normal' variables as described here:

https://fxdreema.com/instructions/builder/constants-and-variables

Simply forget Global Variables and Terminal Variables for your 2 EAs unless you want to communicate two separate MT4 platforms.

Thanks a lot.

To know if some indicator can be used, and how, I created "Levels tester" block. Connect this block with "Just pass" and load the custom indicator inside. Choose one of the buffers available. Run that EA (in visual mode) and in the chart you will see levels of the buffer.

Something like this? http://fxdreema.com/shared/Uzvugs75d

When backtesting, white checksigns are the moments where it tries to close the trade, yellow x-signs are the moments where it says that no close will happen on the next check.

Those 3 blocks on the right are optional, they does not matter in the strategy and can be removed. Block "a" is connected between "5" and "10" because otherwise "10" changes the environment for "a".

Every "n" minutes - this is a block who can pass once at the last minute in the period. When started for the first time, it does not pass.