Edit: These dicussions really belong in the Dev thread, didn't intend to release this here since I just hit reply.

It appears that we need to do MarketInfo(Symbol(),MODE_STOPLEVEL)*Point

... line 700 and 701
Changes to:
Same change on 715

That is completely my fault. The documentation listed "MODE_STOPLEVEL 14 Stop level in points." but I didn't correct for it :/ That is what weekly builds are for I suppose. Mode 1 may be stable. I'm thinking about releasing 5.6.08 with mode 1 by default, listing the build as "stable" and making Mode 2 and mode 3 labeled "unstable - testing". Might be too complicated, but mode 1 has always appeared stable aside from weird broker issues.

I'm tempted to release a "logging" version as well for testers. It shouldn't be used on a daily basis, but logging would help a lot. I did create nearly 100G of logs on a single backtest (with optimization) but by default logging would be off.

So we have 3 choices...
1) make the two line change and release 5.6.8 as is.
2) Finish the extra logging and release 5.6.8 with logging off by default
3) Change the default mode to Mode 1 (which isn't as powerful but very functional) and release 5.6.8 as stable mode 1 only.

The typical user won't change the mode unless they read the documentation. Maybe when Mode 3 is stable we would mark it by default?

Feedback please...

Where is my third trade (mode3) of USD/JPY 2006/11 dec 11:43 ???

Attached Files

Statement 12 dec.htm (12.9 KB, 41 views)

Yep, thats error #130 and I thought I posted it. My mistake.
Yep, i've seen *point a lot of times and always wondered what does it do.
Thanks for explanation! I'll try to backtest using modified code.
I think that you can make 5.6.8 without logging and then add a 5.6.8L version with logging. But please include default settings instead of 0. Using prefsettings is good but seeing 0 everywhere makes me confused badly. Or make a pack of the EA and settings for every currency pair.
Also is there a way for me to backtest with 2 different currency pairs with different settings? Like testing EUR and GBP at the same time... If there is, I'd love to test all 4 main pairs on a single backtest (I understand it will take a few hours to do a 2,5 year backtest)

Phoenix 5.6.08 has been released. Mode 1 is set by default, please continue to help us debug mode 3. We didn't want people loosing money because mode 3 might have errors.
Phoenix - Development+Suggestions - MQ4 in Post#1

Switched yesterday to P5608 around 1100 PM GMT in mode 3
For now new trades openned since : +261
What it will be.. when this mode will NOT have errors !!!!
(Statement if you want)

2006.12.13 01:15:44 Phoenix_EA_v5_6_08 GBPUSD,M15: OrderModify 3 - Error # 6

2006.12.13 09:33:41 Phoenix_EA_v5_6_08 USDJPY,M15: Error Ordersend(138):

Statement welcome... Thanks.

Mode 3, FXDD, P5608, inside settings
Two statements of yesterday
One to day
start at openning last sunday

Attached Files

	Statement 12 dec.htm (12.9 KB, 50 views)
	Statement 122 dec.htm (17.8 KB, 29 views)
	Statement 13 dec.htm (18.5 KB, 39 views)

06:35:01 Phoenix_EA_v5_7_0 EURJPY,M15: initialized
14:42:24 Phoenix_EA_v5_7_0 USDCHF,M15: open #2061924508 buy 0.10 USDCHF at 1.2129 sl: 1.2049 tp: 1.2233 ok
14:42:24 Phoenix_EA_v5_7_0 USDCHF,M15: open #2061924510 buy 0.10 USDCHF at 1.2129 sl: 1.2049 tp: 1.2259 ok
14:42:27 Phoenix_EA_v5_7_0 USDCHF,M15: open #2061924512 buy 0.10 USDCHF at 1.2129 sl: 1.2049 tp: 1.2285 ok

I am testing p570 mode 3 on fxdd, this morning and there isn't bugs

I want to thank daraknor for great work about mode 3

giapel

I should update this thread to let the people who only check here know: 5.7.0 was released last night and it fixes these trade issues. I tested 3 data sources on 5 backtests and didn't get the error any more. (I had to hunt my data collection to cause the error, so this isn't an absolute guarantee.)

Mode 3 has significant changes. I removed the history checking, the global variables and a large part of the detection routine. about 60 lines of code with strange errors and erratic behavior replaced with 3 lines of code that are consistent.

As always, MQ4 file in post #1 of Dev thread. Details in the changelog.