VHands Trading Simulator | Page 19 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

What ever happened to VHands? 1 reply

Trading simulator or practice tool 10 replies

MTF HMA + VHands Trade = Holy Grail? 6 replies

My fib journal, vhands an all! 40 replies

Exercise for Newbs using VHands 13 replies

Attachments: VHands Trading Simulator
Exit Attachments

VHands Trading Simulator

  • #361
  • Sep 16, 2010 8:29am Sep 16, 2010 8:29am
Quoting nubcake
you said you figured out how to download the history and had done so, so what has changed since then?

the last thing i can think of is you keep changing timeframes. if want to backtest on m15 then download m15, set the timeframe in the tester settings to m15, and get to it.
Nah, I always stick to my beloved 1HR chart. And yes, I figured out how to download it and did it. How come the history isn't still there?
  • #362
  • Sep 16, 2010 8:41am Sep 16, 2010 8:41am
dont know what is going on dude. something hokey is happening or you have set something incorrectly.

check the strategy tester journal and see if it is complaining about anything.
Congratulations ScalaFX for coming out of the closet!
  • #363
  • Sep 16, 2010 8:49am Sep 16, 2010 8:49am
Quoting nubcake
dont know what is going on dude. something hokey is happening or you have set something incorrectly.

check the strategy tester journal and see if it is complaining about anything.
Yeah definitely is.. The strategy tester journal is complaining like a bad bitch..
TestGenerator: unmatched data error (low value 1,2904 at 2010.07.23 22:00 is not reached from the least timeframe, low price 1.2905 mismatches).

And there is allot of this.. Perhaps 100-150 of these on several different numbers.. No idea whats wrong!
  • #364
  • Sep 16, 2010 8:58am Sep 16, 2010 8:58am
set the date + 1 from where it typically starts you from. check journal.

set back one day. check journal.

set back another day. check journal.

my guess is that the 3rd time you do this you will start seeing errors while the first 2 are clean
Congratulations ScalaFX for coming out of the closet!
  • #365
  • Oct 8, 2010 5:57am Oct 8, 2010 5:57am
Guys, I can't change the parameters with the lot size, stop loss in the metaeditor. When I change the parameters it won't let me compile or save the file.

Any Suggestions?
  • #366
  • Oct 9, 2010 5:54am Oct 9, 2010 5:54am
Quoting robster
Guys, I can't change the parameters with the lot size, stop loss in the metaeditor. When I change the parameters it won't let me compile or save the file.

Any Suggestions?
i suggest you give more information... such as any error messages etc.

edit : be aware that there is a limit to how low a number you can use. i think it is 0.1 , even though my broker allows trading down to 0.01 lots. this is possibly where you are having issues... without know more information of course of your specific error.
Congratulations ScalaFX for coming out of the closet!
  • #367
  • Nov 5, 2010 12:17pm Nov 5, 2010 12:17pm
Sorry for my english .
Do you know a time indicator that print time (type 20/08/2008 12:05:30 AM) and that work in backtesting? This indicator must be working, in backtesting .
This is important for the news , when you test the strategy in back-test on time frame h1 .
  • #368
  • Nov 25, 2010 5:09pm Nov 25, 2010 5:09pm
it's been a year or 2 since first reading this thread so i'm not sure if this is already mentioned somewhere...

but, pro tip : unless you have some need to do trade management within each bar then do yourself a favour and change the 'model' option from 'every tick' to 'open prices only'. you will note that in 'every tick' that high volume bars take far longer to resolve than low volume bars (and this makes perfect sense and is fair enough), but if you have no need to watch the action within each bar and only care for each bars resolved formation then set to 'open prices only' and you will be able to adjust the speed setting to whatever you find comfortably fast enough and it will be CONSISTENT and fluid.

for too long i had it set to 'every tick' due to my first musings way back when i first started playing with different ea strategies, and from then never bothered to even look at the model setting again. lately i don't care to know what's happening within each bar so the model setting is only being a burden set to each tick.

anyways...
Congratulations ScalaFX for coming out of the closet!
  • #369
  • Nov 25, 2010 8:31pm Nov 25, 2010 8:31pm
Quoting nubcake
it's been a year or 2 since first reading this thread so i'm not sure if this is already mentioned somewhere...

but, pro tip : unless you have some need to do trade management within each bar then do yourself a favour and change the 'model' option from 'every tick' to 'open prices only'. you will note that in 'every tick' that high volume bars take far longer to resolve than low volume bars (and this makes perfect sense and is fair enough), but if you have no need to watch the action within each bar and only care for each bars resolved formation...
yeah mate

I dont even think the "every tic" is that accurate. It doesnt actually remodel the actual tic by tic movements just takes the m1 data uses the "volume" and randomlly tics it out I think.

I hate V hands. But for a free testing tool I guess you cant complain.
Time hides Nothing
  • #370
  • Nov 25, 2010 8:44pm Nov 25, 2010 8:44pm
Quoting CindyXXXX
yeah mate

I dont even think the "every tic" is that accurate. It doesnt actually remodel the actual tic by tic movements just takes the m1 data uses the "volume" and randomlly tics it out I think.

I hate V hands. But for a free testing tool I guess you cant complain.
it's impossible for mt4 to recreate proper ticks, so yes it always has been just a guesstimation on it's part of where it could be ticking, where it can be ticking, and where it should be ticking, to derive a rough candle tick-set based on volume.

it's only use is to get a bad idea of how a strat might work-out if the strat doesn't wait for bar closes before actioning (e.g. trailing a stop before bar close can in one instance be tagged but in another survive long enough for another part of the strat to function).

don't know why you hate vhands so much. it's pretty basic, but that's all one needs to start testing ideas. i wrote my own so that i could just keyboard it all and not have to pause and unpause etc... could just watch the chart and let it do it's thing while i pressed keys to open and close etc as the action unravelled.... but i lost the script when i had to reinstall mt4, and cbf recoding it just yet. tis on my todo list. i think LFH, LHF... whatever that other one is called, i think it's the exact same concept, except i'm going to go a bit further with mine when i redo it.
Congratulations ScalaFX for coming out of the closet!
  • #371
  • Nov 25, 2010 8:57pm Nov 25, 2010 8:57pm
Quoting nubcake
it's impossible for mt4 to recreate proper ticks, so yes it always has been just a guesstimation on it's part of where it could be ticking, where it can be ticking, and where it should be ticking, to derive a rough candle tick-set based on volume.

it's only use is to get a bad idea of how a strat might work-out if the strat doesn't wait for bar closes before actioning (e.g. trailing a stop before bar close can in one instance be tagged but in another survive long enough for another part of the strat to function).

don't know why you hate vhands...

Only reason i dont like it is because of the trade management. Cant move stops to BE or targets etc. So its a bit hard to do a realistic back test. The tic by tic is too slow and the open only only gets you in at the next open price so er just not a realistic simulation of the real thing. On the LHF ine you can drag your stops and targets around but then it only has stop orders and not limit orders. THeres always something lol. Lazy programmers coulda just gone that extra bit further to make it awesome. But anyway.

oh yea and lack of different timeframes sux. Better than nothing though.
Time hides Nothing
  • #372
  • Nov 25, 2010 9:11pm Nov 25, 2010 9:11pm
Quoting CindyXXXX
Only reason...

dragging stop losses and tp's is exactly how you do it in vhands... there's like 9 lines to pick and drag, 2 of which are market buy and sells... all the rest are limit and stop orders depending on which one and which direction.

edit : in case you weren't aware, to set or adjust stops and tp's on an already opened position in vhands you simply need to move the corresponding label (stoploss label, tp label), just like when you close an order you move the order number label... then you have to let it run a tick (unpause, then pause again) and you will be able to manually move the stoploss or tp up and down the chart to where you want.

/edit

as for the timeframe and tick issues, that is purely mt4's fault and no one elses. you can write an indicator to reformat to whatever timeframe you like (and i will be doing this... again it's on my list), so that's the easy workaround.

it seems to me that the only limitations of vhands which are actually it's problem and not mt4 issues are :

1 - having to pause to drag commands onto the chart, then unpause (not such a big deal, just frustrating if you only want to simply open and close which can be done by a keypress)

2 - having a set amount of lot size and trail stop distance options etc

3 - forgot, or there isn't a third.

getting anything better is going to cost money, which you already know and are investigating. you'll need real-deal tick data etc, so you are going to end-up with quite a big package if you source something which fits your wants.
Congratulations ScalaFX for coming out of the closet!
  • #373
  • Nov 25, 2010 9:15pm Nov 25, 2010 9:15pm
Quoting nubcake
edit : in case you weren't aware, to set or adjust stops and tp's on an already opened position in vhands you simply need to move the corresponding label (stoploss label, tp label), just like when you close an order you move the order number label... then you have to let it run a tick (unpause, then pause again) and you will be able to manually move the stoploss or tp up and down the chart to where you want.

/.
Oh wow I never knew that! Hence my biggest frustration with it. Let me try...
Time hides Nothing
  • #374
  • Nov 25, 2010 9:19pm Nov 25, 2010 9:19pm
OMG... M8 ive used this soooo much and never even knew you could do that. Thanks. That is awesome
Time hides Nothing
  • #375
  • Nov 25, 2010 9:37pm Nov 25, 2010 9:37pm
Quoting CindyXXXX
OMG... M8 ive used this soooo much and never even knew you could do that. Thanks. That is awesome
lol. good to see you read the thread / manual
Congratulations ScalaFX for coming out of the closet!
  • #376
  • Dec 7, 2010 7:03am Dec 7, 2010 7:03am
just a little something something that i finally bothered to put together that may or may not help with backtesting ideas with vhands. they are very basic, but priority is function over form.

nbDayOpenTimes2Indi : to help visualize what the time is in tokyo (red), london (blue) and new york (white). i use an old P4L clock version on my real-time charts to know what's what right now, but backtesting and any historical charting is a small challenge to work-out what times were at any point. you need to change the charthouroffset value to whatever aligns the time in the indi to your chart.

nbDayOfWeekIndi : same reasoning as above to know what day of the week a chart is showing. is based only on the charts datetime, so if your charts date and time are out by a significant amount then too bad and the indi will show simply what the chart datetime is. the point is consistency. if you see something every 'monday' then you can consider that the next 'monday' on your chart might have something similar. 1 is monday, up to 5 for friday.

very basic indi's, but might help with keeping orientation within historical charts.
Attached File(s)
File Type: ex4 nbDayOfWeekIndi.ex4   2 KB | 647 downloads
File Type: ex4 nbDayOpenTimes2Indi.ex4   3 KB | 658 downloads
Congratulations ScalaFX for coming out of the closet!
  • #377
  • Dec 11, 2010 11:29am Dec 11, 2010 11:29am
and here's another something something that might be useful, or not. i am an M1 junky. so to run vhands or any backtesting in M1 makes it impossible to see the H1 for example. this indi will allow you to see whatever timeframe grouping you like up to 60minutes (H1). if you run it on anything other than an M1 chart then you will surely run into troubles if you try to do something fancy like show M6 but your chart is running on M15. this won't do you any good. just run it on M1 and then set your desired timeframe grouping value in the settings.

this has been on my todo list for ages. again, function over form is the goal. i only threw this together tonight. might still have bugs. enjoy.
Attached File(s)
File Type: ex4 nbMTFIndi.ex4   5 KB | 577 downloads
Congratulations ScalaFX for coming out of the closet!
  • #378
  • Dec 16, 2010 12:15pm Dec 16, 2010 12:15pm
Quoting nubcake
might still have bugs. enjoy.
which it did. no lows were being shown. fixed. attached.
Attached File(s)
File Type: ex4 nbMTFIndi.ex4   5 KB | 727 downloads
Congratulations ScalaFX for coming out of the closet!
  • #379
  • Jun 16, 2011 7:11pm Jun 16, 2011 7:11pm
Anybody able to get this to work on FXCM MT4 by boston Tech?
The Vhistory, and Vterminal wont even load on a chart.

Works fine on FXDD!

Thanks
  • #380
  • Jun 17, 2011 12:31am Jun 17, 2011 12:31am
you probably didn't set it up correctly and missed a key point or step. go back and re do it following the instructions exactly. vhands isn't robust and will break if you don't set up the indicators for it in the exact order it tells you to.

eww such an old crappy mtf indi...
Congratulations ScalaFX for coming out of the closet!
1 trader viewing now