EarnForex / PositionSizer

Calculate your position size based on the risk and account size and execute your trades with this free MetaTrader expert advisor.

Home Page:https://www.earnforex.com/metatrader-expert-advisors/Position-Sizer/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Invalid TP issue on some pairs like EURGBP

ecomaven opened this issue · comments

image

Noticed an issue as PSC will not calculate risk, reward or lots on a few pairs but works on others.
Strangely it does not display the Entry, TP or SL lines automatically on those pairs despite the Order Type being set to "Instant".
When changed to pending and Entry/TP/SL prices manually entered, still gives "Invalid TP"

image

Which broker/account is that? Is there any output in the Experts tab of the Terminal subwindow?

Broker is IC Markets
image

And which account type at IC Markets?

raw spread

demo

Can you provide the list of steps that you made to get this issue? I've just tried the PSC on EURGBP IC Markets Raw Spreads account and I couldn't reproduce the issue.

Strange. I just tried it again now and it works without my doing anything.

The steps are the simple and same. PSC is loaded as part of my template.

  • I open PSC and click "show lines".
  • Then click "Order type".
  • Then drag lines as necessary.

Maybe some weird setting value got saved into your template? If you add a fresh PSC does it have the same issue?

Was not a weird setting in template cause when i changed the pair from EURGBP to another pair EURJPY it worked but once I took it back to EURGBP it resumed showing that "Invalid TP".

As of now both with my template and fresh PSC, it works.

As of now both with my template and fresh PSC, it works.

By "it works" you mean that the issue is showing up or that everything gets calculated correctly?

Everything is getting calculated correctly atm

Did the issue appear just after upgrading the PSC from the previous version to 2.42?

Actually happened in 2.41 which spooked me and actually made me upgrade to 2.42. When the same thing happened in 2.42, I decided to write this issue

Wow! That's very strange. Let's wait for it to appear again then. Please try to remember all the preceding steps if this appears again, so that I could try to reproduce it and find the underlying cause. Thank you!

Should be addressed in 3.03.