Topics created by jstap

@stonegoldtz This is not the topic for that, create a question and place it it the questions forum.

MT5生成器在哪里打开页面

I tried to do this just to check if works to save the variables correctly. I guess I'm doing something wrong but I'm don't know what exactly 😅 https://fxdreema.com/shared/GrBXfdQ2b

@mohsenimi Generate a fresh question for this, it has more to it than a simple answer.

@jstap Interesting. Thank you.

Is awkward when you change a string to int, then work with what the FX block is doing so having to convert again 😊 the link below will do it.

MT5: https://fxdreema.com/shared/sOLiFCdqb
MT4: https://fxdreema.com/shared/DyQKz9f2b

@Miksen5Andrstq said in Using Fibonacci:

Fibonacci con zonas de soporte/resistencia.

Tu puedes unir estos dos video tutoriales y resolverás tu problema:

https://www.youtube.com/watch?v=Vl70r7j1x_0&pp=ygUwZmlib25hY2NpIHN1cHBvcnQgYW5kIHJlc2lzdGFuY2UgbGV2ZWxzIGZ4ZHJlZW1h

https://www.youtube.com/watch?v=cjiJ0pYmOWI&pp=ygUwZmlib25hY2NpIHN1cHBvcnQgYW5kIHJlc2lzdGFuY2UgbGV2ZWxzIGZ4ZHJlZW1h

Not working this code proper please explain properly

I still have some compilation errors but I don't know how to resolve them
https://fxdreema.com/shared/pc4YCZiOb

thanks jstap you are really good

Thank you for the advice that helped me a lot, @jstap. I also have some additional recommendations for those who encounter the same issues as I did or are interested:

When I used this code approach to create an MQL5 EA that uses Zigzag, I encountered the error: "Error: Cannot get value from a custom indicator. (handle=15 | error code=4806)" during backtesting/optimization, which caused the backtest/optimization to slow down.

Upon investigating the cause of this error, I found that it occurred because the Zigzag high/low at sequence 0 could not be found simultaneously. Specifically, if there is a high of 0, the low of 0 will also be missing, and vice versa. Therefore, for every Zigzag from FXdreema, when using high 0 and low 0, add an "indicator is visible" block to check if the value appears correctly before calling the Zigzag high 0/low 0 value.

Note: Other Zigzag IDs, i.e., those greater than 1, do not have this problem because the values are definitely present.

As shown in this example: https://fxdreema.com/shared/dMTrCKjG

Your welcome

@roar As I am sure you are aware, this uses market info, so converting to m5 is not simple 🙂 (probably the main reason why I don't use).

In here is the completed project: https://fxdreema.com/shared/3rOqOH3ve, I had to strip back and create separate for buys and sells, before adding the values together.

Hope people find this useful.

@alan-paredes2 hi, i'm almost done

@ontradingx sorry, correct is @FXDREEMA

@l-andorrà Your welcome

@doeveR
Maybe normalization by ATR can help. Say, divide the increment or slope, by ATR. Or you can even try the square root of ATR. That make sense as ATR is approximately proportional to time square. And the slope is given by increment over time.

Just make some test to see what you want

Thanks for sharing this @jstap