Posts made by vnpython 0

thanks for clearing this ECN error thingy!

use custom mql code:
vSwapSell=NormalizeDouble(MarketInfo(Symbol(),MODE_SWAPSHORT),3);
vSwapBuy=NormalizeDouble(MarketInfo(Symbol(),MODE_SWAPLONG),3);
then out put to where you want them to

use custom mql code:
vSwapSell=NormalizeDouble(MarketInfo(Symbol(),MODE_SWAPSHORT),3);
vSwapBuy=NormalizeDouble(MarketInfo(Symbol(),MODE_SWAPLONG),3);
then out put to where you want them to

taken the day light saving into consideration... so now you know the server time, then you know how to determine the filter

@setsuna said in RSI entry:

@vnpython-0 it's a British time frame. I use gmt 8.00. But the biggest problem is to not trade when it's start

ask your broker on the chart time is it NY close (GMT3) or whatelse

i think first you need to find out what time zone your broker is using in order to filter out that time frame you wish to trade

dear all, this issue is resolved by the big boss already hehe

is your EA condition fixed on specific TF? or on current?

@miro1360 thanks and much appreciate your guidance! just hope the big boss @fxDreema can resolve the bug in fxd compiler...

@miro1360 i did read one of your earlier reply to someone also having this issue. but i dont understand how you do it.. do you mind guide me? i saw you replace enTimeFrames to TimeFrame using int declare and do away the whole enum enTimeFrames. But when i use your mod to compile under editor, it gives me error on tf-cu and i changed to TimeFrame and it compile nicely.

as i am still new on coding and your assistance would help me greatly

i wonder if our big boss know about this bug?

our dear boss here still able to access to all our profitable EAs hehe

0_1556008963847_Trend direction & force index - smoothed 4.mq4 this custom indie compile fine in mt4 with no warnings but when i use this to upload to 'MY INDICATOR' it says error found in 'enTimeFrames' which do not show in mql4 compiler. can @miro1360 or @fxDreema kindly take a look? could it be the bug?

you're right! i just use the date earlier and is resolved... must be due to position of candle to detect the crosses... eg: usually i use the date from 2010/01/01 to start and this might have caused the divide zero, and once i enter the start date to 2009/12/30 and the EA runs normally.. thanks miro for the clue!

hm... i usually have divide by zero.. what might be the cause @miro1360 ? i also post my issue in the bug area.. please help to see if able to resolve? not everytime and when that happens, i usually change the date start from 20xx/01/01 to 20xx/01/05 and resolve it. but there are times no matter what, just cannot resolve..

maybe dear @fxdreema can amend the block to miro's solution to avoid this issue altogether?

2019.04.11 13:04:15.138 2010.01.04 02:00:00 Testing pass stopped due to a critical error in the EA

2019.04.11 13:04:15.138 2010.01.04 02:00:00 SSL Testing NZDUSD,Daily: zero divide in '18464-28745.mq4' (5756,106)

happens when i am putting a parameter for an indicator to check the settings.. eg: parameter 28 for period is fine but when i use 29, the EA gave the above error.. any idea? @fxDreema

wow.. thats high level skill to learn... i hate math!

forgotten to search.. sorry haha

dear all senior in EA making, at this moment, i think fxdreem cant use the above data from a indicator? example: MA on ATR's value?

@roar thanks for replying. appreciate the effort