Position Size Calculator

Discussion in 'MetaTrader Indicators' started by Enivid, Mar 27, 2012.

  1. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    I recommend using the latest version - 2.24.
     
  2. Teranox

    Teranox Newbie

    4
    0
    1
    I have looked and finding some Errors, but there are none.
    I think it happens when I place an Order through EA that has printed buttons on the chart
    The PSC remains half way in the background. I cant move it or calculate with it but I can still input values in its fields...
     
  3. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    It looks like the EA is messing with the PSC's panel objects, but I don't understand why and why there are no errors. Could you please attach the EA's source files here?
     
  4. Misanthropic

    Misanthropic Newbie

    7
    2
    3
    Thank you, i will try it out. I remember that metatrader 5 has had some kind of automatic update a few weeks ago. Maybe this is the reason for the failure? I will write again in here if this does not fix the problem.
     
  5. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    Are you talking about Build 2085 (June 13) update? It should work well with it. If you mean some beta version update, then there is no guarantee. Some beta version builds are too buggy.
     
  6. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    Position Size Calculator has been updated to version 2.25 to fix compilation errors in MT5 Build 2170 and later releases. Position Size Calculator for MT4 has also been updated to fix the same issues in case MQL4 gets similar updates in the future (which is quite probable).
     
  7. DT77

    DT77 Trader

    145
    19
    24
    Cool thanks
     
  8. Misanthropic

    Misanthropic Newbie

    7
    2
    3
    I just tried out trading with the newest version. So far it seems that the failure is gone on some pairs. But i noticed on some pairs (for example US500) that the position size is again way off. I think some others have also wrong values but not that extreme. If i enter a long on US500 with 100 euro risk and the price moves to target (about the same pips as my stop loss) i am merely 0.90 cent in profit but it should be 100 euro. I also have opened 2 trades with different percentage risk but both positions have the same profit/loss number all the time. This is impossible because the position size should be different. I think this is the problem in this case.

    I also just noticed that on US500 the maximum position size by marging does change if i change the leverage. This is not the case on the forex pairs so far. This means maybe that the US500 has a false default leverage set?
    [​IMG] [​IMG]
     
    Last edited: Oct 9, 2019
    Enivid likes this.
  9. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    Thanks for uncovering such a critical bug. It is now fixed in version 2.26.
     
  10. Misanthropic

    Misanthropic Newbie

    7
    2
    3
    Okay thanks. I found another failure in the pair XTI USD (oil). A test trade with 50 euro risk resulted in a close in 81.50 euro loss. This is more than 50 % off. Any guess what the reason could be here? The position size is changing but it is still somehow wrong.
     
    Enivid likes this.
  11. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    Just a heads up - I see the problem and I am currently working on it.
     
  12. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    Actually, after looking closer at the issue, there is a problem with margin calculation for the cases like XTIUSD + EUR account, but there isn't any problem with calculating the position size. Could you please check again? Perhaps, the 50 EUR risk you give as an input translates into 81.50 Result risk as calculated because of the too wide step combined with tight stop-loss? Attaching some screenshots would be helpful here.
     
  13. Misanthropic

    Misanthropic Newbie

    7
    2
    3
    https://www.directupload.net/file/d/5602/w2jv2yhp_jpg.htm

    I hope this link is okay. Somehow i can not upload pictures in form of a jpeg or something else. It shows the data of the trade that i exported from metatrader 5. Is this enough? I think in terms of a too tight stop loss the numbers don´t make sense. It was not a huge slippage or something like that. I think some other pairs do have a similiar issue.

    Maybe the best solution for me is just to convert my euro into dollars on IC market if i want to trade it on a real account? Maybe you can tell me if this issue is likely a problem because of the euro currency. I guess most people use dollar as base currency and i bet it will be the one which hopefully works perfect.
    [​IMG]
     
  14. Misanthropic

    Misanthropic Newbie

    7
    2
    3
    Here is another picture. The first one seems to have strange numbers /wrong orders. This one is a screenshot of the interface

    https://www.directupload.net/file/d/5602/vyv786d5_jpg.htm
     
  15. Enivid

    Enivid Administrator Staff Member

    11,717
    438
    114
    Did you try uploading an image via "Upload a File" button? It should work.

    It would be best to see the actual PSC panel with everything calculated and the resulting trade together to see what's going on. But from this image, I can see that the volume is 0.50, which is the minimum size allowed on XTIUSD at IC Markets. If your calculated position size was 0.31 for example, the calculator would display 0.50 as the result, which would lead to the loss of 81.50 EUR instead of the planned 50 EUR. If you look at the PSC panel, there are two columns - Input and Result:

    psc.png

    As you can see, the resulting risk is about 1.3 times higher than the given one because the position size cannot go lower than 0.5 lots on XTIUSD.

    I don't think that's the case. I have checked XTIUSD with EUR account on IC Markets and everything looks fine (except margin calculation, which is going to be fixed in the next version).
     

Share This Page