lt;? Xml:namespace prefix = st1 ns = urn:schemas-microsoft-com:office:smarttags /gt;lt;st1:City w:st=ongt;lt;st1lace w:st=ongt;Phoenixlt;/st1lacegt;lt;/st1:Citygt; relies on a former EA: Firebird (created by traderSeven). See the guide for additional information. Of all of the EA's I tried, Firebird was the initial EA that had the capability to make some cash. On the other hand it had some bad habits that could lead to a badly drawdown of your account. Lt;st1lace w:st=ongt;lt;st1:City w:st=ongt;Phoenixlt;/st1:Citygt;lt;/st1lacegt; is an attempt to preserve the very best of Firebird and to protect against the drawdowns of your account. lt;? Xml:namespace prefix = o ns = urn:schemas-microsoft-com:office:office /gt;lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
Maybe it's too soon to start lt;st1:City w:st=ongt;lt;st1lace w:st=ongt;Phoenixlt;/st1lacegt;lt;/st1:Citygt;. I didn't have the time to create all the necessary tests or implement appropriate error-controlling mechanism. Furthermore some parts need a little tweaking But Wednesday next week I will have my vaion but before that I would like to provide a bug-free lt;st1:City w:st=ongt;lt;st1lace w:st=ongt;Phoenixlt;/st1lacegt;lt;/st1:Citygt;. So my request to you would be to test this model and give me as much feedback as can before following Wednesday!lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
As starter of this thread and maker of lt;st1lace w:st=ongt;lt;st1:City w:st=ongt;Phoenixlt;/st1:Citygt;lt;/st1lacegt; I think it's just to create some rules. Well in fact only one: of course you are free to adapt lt;st1lace w:st=ongt;lt;st1:City w:st=ongt;Phoenixlt;/st1:Citygt;lt;/st1lacegt; in any way you need, but please don't post it in this thread! I want to maintain the code of lt;st1:City w:st=ongt;Phoenixlt;/st1:Citygt; as blank as possible and need to avoid that in the ending too many versions of lt;st1:City w:st=ongt;lt;st1lace w:st=ongt;Phoenixlt;/st1lacegt;lt;/st1:Citygt; are st in precisely the same thread and no one knows what variation is doing exactly what. Lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
Should you think that you have a practical addition or modifiion for lt;st1:City w:st=ongt;lt;st1lace w:st=ongt;Phoenixlt;/st1lacegt;lt;/st1:Citygt;you can post it in this thread. We can talk about it and if all of us agree I will implement it in lt;st1:City w:st=ongt;lt;st1lace w:st=ongt;Phoenixlt;/st1lacegt;lt;/st1:Citygt;.lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
I will use this first post for the upgraded versions of the EA, the indior and the manual.lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
That is all. Let us give it a try!lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
In the ZIP-file you'll get the following files:lt;ogt;lt;/ogt;
lt;ogt;lt;/ogt;
Phoenix_EA_v1_0. mq4-- the ”Expert Advisor”lt;ogt;lt;/ogt;
Phoenix_IND_v1_0. Mq4-- the indior to generate the SafeArea observable (seen manual) you don't need it for the EA to work!lt;ogt;lt;/ogt;
Phoenix Manual v1.0. P
Update 07/14/06:
Version 1.1
- Utilize the placing RoundupLots=true if your broker don't accept Lots like 0.24.
- Is now working for MicroAccounts
- Corrected a problem with GambleNow and MM
- SafeArea wasn't functioning for EURJPY. It does.
lt;! -- / message -lt;! -- attachments -
https://forexintuitive.com/attachmen...1712461227.zip
https://forexintuitive.com/attachmen...1398349046.mq4