found another issue, please also check it. please follow below steps: 1. export data in ASCII, choose time expressed in "Local", save it 2. import data in ASCII, find the previous file(export and import same instrument). Choose "Local" as time expressed 3. Then you will get the warning pop up, told ...

When I export the QM data, I select many instruments as a batch exporting. Then I get files more bigger except the first instrument with correct output. It seems exporting many times with your selection items, for examples, export item is "date/open/high/low/close/totvol" and the first one is correc...

Hi Alex, thank you for your clarify my issue, you had correct point out the question.
I had use MC and TWS for a long time, old version had no issue about the lag, but I not sure what version of MC or TWS should be fine, it seems 3 months ago will be fine.

I got a problem that bother me more and more. IB TWS unrealized P/L and MC shown always are not equal. MC shown lag more than few minutes, not a fix number in minutes, sometimes few seconds. <Windows 10, MC64 11.0 Build 16148, TWS 971> https://drive.google.com/open?id=1ndLvFe7RJtDuIllyUP4P6HQclnixDfm3

The step as below:
1. Open QM
2. Intrument->add symbol->from data sources->IQFeed
3. Future (i want to add QGCZ15, Gold December 2015)

but it does exist the check box of expired symbol.

I can not add the expired instruments because the option is canceled. Is there any method to add the expired instruments?

I use the newest version(9.1 Build 12010) of MC, I delete a lot of instruments. I found the database is still large and my Ramdisk is almost occupied. Can you release the method that decrease the database size?

Does anyone can explain what it's mean? Does that mean this strategy will perform better than backtesting in real?

Hi Henry:
How it can be? I had test more than 10 times on MC 8.8 and it must had wrong entry every time. Can you tell me what version do you test for?

Hi Henry:
Did you test it? It didn't work correctly, same as original status. Please ask you engineer to test it, and also for function-"barssinceexit(1)" on tick/50 point resolution chart. It's a bug obviously.

Hi Henny: It had 2 months passed. Would you please let me know this bug had been confirmed yet or not? It's not only on tick resolution but some kind of chart(like 50 point) has same issue on "barssinceexit(1)" function. There is no way to restrict abnormal trade. Please let me know do you plan fix ...

I had traced this issue more than 2 months. The issue is the entry order malfunction sometimes. My code constrains the entry order didn't come with the stop order. But no matter how I setup MC profile or add restriction in program code, the entry order generated come with the stop order filled immed...

I use tick resolution and trade 6 commodity at same workspace. And I use "ramdisk" for speed up strategy and protect my SSD, but I must delete the trading log manual about 6~8 hours because it's expand to more than 1G. It's huge if I wait to MC delete it at next time restarted. Can I disable it?

I'll try SP suggestion and check the performance improvement. Thanks again for SP.

I want the "skip identical tick" option on a strategy like on an indicator. If our every trade is triggered by price, why we don't skip identical tick to speed up the strategy action? I'm using 1 tick resolution for strategy calcutaion, I found MC(64 bit/8.8 Build 8967) had lost to record high/low s...