Multicharts 6.0 Beta 3 feedback
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
It appears to me that as of beta 3, if you have an indicator that calls a function, and the indicator is on a chart window, and you modify the function and verify it from PL Editor, the chart window says "verifying..." until you click over to the indicator and re-verify it, even though it has not changed.
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Guys, you really need to address the holidays issue.
With futures, namely the ES, the holidays option don't work since the futures markets trades almost 24 hours day.
For those like me, who takes the overnight session in consideration, if the holidays option is active (ie, with holidays written in QM), the ES chart (24 hours) continues to plot the bars traded during that holidays overnight session, but will cut half of the next days overnight session bars, since the ES usually starts to trade at 5PM EST but the holiday option will only stop at midnight, when the new day kicks in.
The solution is obviously deleting all holidays in QM, but this creates another problem when mixing overnight data with the regular session data since dates will not match.
Regards,
Fernando
With futures, namely the ES, the holidays option don't work since the futures markets trades almost 24 hours day.
For those like me, who takes the overnight session in consideration, if the holidays option is active (ie, with holidays written in QM), the ES chart (24 hours) continues to plot the bars traded during that holidays overnight session, but will cut half of the next days overnight session bars, since the ES usually starts to trade at 5PM EST but the holiday option will only stop at midnight, when the new day kicks in.
The solution is obviously deleting all holidays in QM, but this creates another problem when mixing overnight data with the regular session data since dates will not match.
Regards,
Fernando
It also seems that the "lookup" function that you can use to look for MBT accounts (forex, margin etc.) in the automation area only finds one account (instead of three), and it is not the right account number.
I enter the right account number, but no orders are ever transmitted to the broker...
I enter the right account number, but no orders are ever transmitted to the broker...
Last edited by duration on 02 May 2010, edited 1 time in total.
My happiness was pre-mature. No forex for me - only futures;) although I specified I want a forex demo account.
And lots of:
''The following error has occured:
*Unknown error(s)''
Their webmaster deserves ... a rise in salary
I'll wait for other forex brokers to be hopefully supported by MC.
And lots of:
''The following error has occured:
*Unknown error(s)''
Their webmaster deserves ... a rise in salary

I'll wait for other forex brokers to be hopefully supported by MC.
- Attachments
-
- unknown error.png
- (75.24 KiB) Downloaded 17426 times
-
- mbt no forex.png
- (17.29 KiB) Downloaded 17422 times
That's weird, they gave me a forex demo feed with MT 4... and there was no way to plot futures!My happiness was pre-mature. No forex for me - only futures;) although I specified I want a forex demo account.
And lots of:
''The following error has occured:
*Unknown error(s)''
Their webmaster deserves ... a rise in salary![]()
I'll wait for other forex brokers to be hopefully supported by MC.
I installed (for the first time) last Friday (2010/Apr/30) these GetAppInfo commands while using MC 6.0 beta 2.
WaveTopDownLineB_Value = GetAppInfo(aiHighestDispValue) - 2;
WaveTopDownLineT_Value = GetAppInfo(aiLowestDispValue) - 1;
It was working properly in that it was putting the text strings at the top/bottom of the screen using the resulting fields of these commands.
Friday Night I installed Beta 3 and today these commands are not working. They are both returning values very close to the close of the bar rather than values at the top or bottom of the screen. In MC 2.1.999.999 they were returning zero so I never used them. I guess I have to go back to doing calculations using the highest/lowest functions back maybe 1/2 of the chart size to ensure these text strings are out of the way a bit from the prices.
WaveTopDownLineB_Value = GetAppInfo(aiHighestDispValue) - 2;
WaveTopDownLineT_Value = GetAppInfo(aiLowestDispValue) - 1;
It was working properly in that it was putting the text strings at the top/bottom of the screen using the resulting fields of these commands.
Friday Night I installed Beta 3 and today these commands are not working. They are both returning values very close to the close of the bar rather than values at the top or bottom of the screen. In MC 2.1.999.999 they were returning zero so I never used them. I guess I have to go back to doing calculations using the highest/lowest functions back maybe 1/2 of the chart size to ensure these text strings are out of the way a bit from the prices.
- TJ
- Posts: 7675
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1018 times
- Been thanked: 2202 times
I have a number of functions and indicators using this keyword.I installed (for the first time) last Friday (2010/Apr/30) these GetAppInfo commands while using MC 6.0 beta 2.
WaveTopDownLineB_Value = GetAppInfo(aiHighestDispValue) - 2;
WaveTopDownLineT_Value = GetAppInfo(aiLowestDispValue) - 1;
It was working properly in that it was putting the text strings at the top/bottom of the screen using the resulting fields of these commands.
Friday Night I installed Beta 3 and today these commands are not working. They are both returning values very close to the close of the bar rather than values at the top or bottom of the screen. In MC 2.1.999.999 they were returning zero so I never used them. I guess I have to go back to doing calculations using the highest/lowest functions back maybe 1/2 of the chart size to ensure these text strings are out of the way a bit from the prices.
They are performing as usual.
Strange, now it is working. Well at least I am prepared now. I have the following code for it.
LOL, I am going to change the words to that song. "EARLY Monday Monday, can't trust that time"
Code: Select all
inputs:
UseGetApp("Y"),
if UseGetApp = "Y" then
WaveTopDownLineB_Value = GetAppInfo(aiHighestDispValue) - TopDownDistance
else
WaveTopDownLineB_Value = Highest(High,30) + TopDownDistance;
if UseGetApp = "Y" then
WaveTopDownLineT_Value = GetAppInfo(aiLowestDispValue) + TopDownDistance
else
WaveTopDownLineT_Value = Lowest(Low,30) - TopDownDistance;
- TJ
- Posts: 7675
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1018 times
- Been thanked: 2202 times
can't launch program
my computer has been acting strange lately,
I don't know if this is a beta 3 problem...
In the "Format Studies" window
when I click on the "Open Script" button,
I get a "Can't Launch Program" error message.

I don't know if this is a beta 3 problem...
In the "Format Studies" window
when I click on the "Open Script" button,
I get a "Can't Launch Program" error message.

- Attachments
-
- cant launch program.gif
- (10.69 KiB) Downloaded 17412 times
I was getting that same "can't launch whatever" in my database program when I tried to open a new form after running for a few hours. I found I had to close it right down and restart and it was good for another period of time. I was thinking that this started around the time I installed MC 6.0. I never saw it before that and I don't think it is any bigger. Actually I went back and cleared as much dead wood as I could and it still does it.
- TJ
- Posts: 7675
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1018 times
- Been thanked: 2202 times
Re: can't launch program
ok problem solved...my computer has been acting strange lately,
I don't know if this is a beta 3 problem...
In the "Format Studies" window
when I click on the "Open Script" button,
I get a "Can't Launch Program" error message.
I traced to the PLEditor Properties,
it was set to Run as Administrator.
I unchecked the box and the PLEditor launches as before.


- Attachments
-
- PLEditor Properties.gif
- PLEditor Properties
- (19.49 KiB) Downloaded 17420 times
There is a problem with Text_GetActive and Arw_GetActive. It thinks text is active when it is not. With Arw_GetActive it does the same thing. For me this is deadly and I have to do an immediate roll back to Beta 2.
I am now back on MC 6.0 beta2 and the problem is fixed. I still have beta3 on the notebook for now at least.
I am now back on MC 6.0 beta2 and the problem is fixed. I still have beta3 on the notebook for now at least.
-
- Posts: 199
- Joined: 25 Jan 2008
- Has thanked: 2 times
- Been thanked: 7 times
Application Error
Tonight I installed beta 3 and have had more than a dozen application errors. It is so unstable I can't use it. The latest Application Error happened while changing the settings on a strategy.
I have been doing some new things with additional data feeds so I can't be certain it is the new build. If it is, can I go back to the previous one without a full uninstall or will a patch/ another build be ready soon?
I typed in the last error message because the program freezes and does not appear to have sent it.
Thank you
DB
Address 0x7C91168B (2089883275)
Code: 0xC0000005(-1073741819)
Continuable 0x000000000(0)
Description: The instruction at")x
Error Code: 0xC0000005(-1073741819)
ExceptionType:0x000000000(0)
Module: C:\Windows system32\ntdll.dll
Process C:\Program Files\TS Support\MultiCharts\MultiCharts.exe
Thread ID:0x000014B0(5296)
Time:04.05.2010-21:31:08.593
I have been doing some new things with additional data feeds so I can't be certain it is the new build. If it is, can I go back to the previous one without a full uninstall or will a patch/ another build be ready soon?
I typed in the last error message because the program freezes and does not appear to have sent it.
Thank you
DB
Address 0x7C91168B (2089883275)
Code: 0xC0000005(-1073741819)
Continuable 0x000000000(0)
Description: The instruction at")x
Error Code: 0xC0000005(-1073741819)
ExceptionType:0x000000000(0)
Module: C:\Windows system32\ntdll.dll
Process C:\Program Files\TS Support\MultiCharts\MultiCharts.exe
Thread ID:0x000014B0(5296)
Time:04.05.2010-21:31:08.593
Beta 3 fixed an issue using ASCII Mapping on a Renko chart, however it seems to not have fixed it entirely.
With beta 2, nothing would load at all for an ASCII Map using a renko chart. With beta 3, some data loads but not all. I have tried several different sizes and lookback date settings, it seems to make no difference.
Attaching a few screens. Please assist, I need this functionality...



Thx,
Mike
With beta 2, nothing would load at all for an ASCII Map using a renko chart. With beta 3, some data loads but not all. I have tried several different sizes and lookback date settings, it seems to make no difference.
Attaching a few screens. Please assist, I need this functionality...



Thx,
Mike
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear bowlesj3,There is a problem with Text_GetActive and Arw_GetActive. It thinks text is active when it is not. With Arw_GetActive it does the same thing. For me this is deadly and I have to do an immediate roll back to Beta 2.
In Beta 3 Multicharts behaves similarly to TS. We had multiple requests from users to change it that way. So the text is always active now.
Dear ctrlbrk,Beta 3 fixed an issue using ASCII Mapping on a Renko chart, however it seems to not have fixed it entirely.
With beta 2, nothing would load at all for an ASCII Map using a renko chart. With beta 3, some data loads but not all. I have tried several different sizes and lookback date settings, it seems to make no difference.
Attaching a few screens. Please assist, I need this functionality...
Please plot a chart with 1 tick resolution. Then go to Start --> Run, type "regedit", click Ok and go to HKEY_CURRENT_USER\Software\TS Support\MultiCharts\Shaper. Compare the MaxBars value with the number of bars on your 1 tick chart. If it is the same, then the maximum amount of bars is achieved. If you need more bars, you can increase the MaxBars value in the registry.
Best Regards,
Dave
Hi Dave Masalov,
Your very first post states:
1/ It defeats the purpose of the command completely (goes against what the help says)
2/ I never saw any request for this on the forum. I for sure would have commented on that.
Here is the help on that command.
Why would one use this command if it always returned a true answer (an object ID) even if no text was highlighted on the chart. How would the command know which one to return if nothing was active on the screen which is exactly what it was doing. When an object is not highlighted the command is suppose to return -1 and that is the way it logically should work. I (and probably many) have programmed very large amounts of code to use this command exactly this way. The way it is working in beta 3 renders the command effectively useless. Therefore what you essentially are saying is TSS has listened to users who are requesting that this command be made completely disfunctional when it was in fact working perfectly already. Are you sure it is not a TS employee asking for this hoping you will actually make the mistake of listening to them? It would be nice if Andrew would comment on this because your response is highly suspect.
If TSS is going to make this kind of a change, at the very least one should have an option to set that command to act the way it was intended in the help. If this command does act differently on TS then it would be wise to make a Text_GetActive_MC command that matches the help and it is very easy for the users to change all their code to match this with a simple search and replace. That way you get the best of both worlds (better than an option actually). Another way would be to have a option command that is placed in front of this command. Such as Option = "TS" or Option = "MC". However a warning that such as change is coming is certainly in order.
To be honest, this is a little scary. As stated above, I think there has to be a miscommunication here.
John.
Your very first post states:
This is unbelievable and I suspect you are misundertanding something!Dear bowlesj3,
In Beta 3 Multicharts behaves similarly to TS. We had multiple requests from users to change it that way. So the text is always active now.
1/ It defeats the purpose of the command completely (goes against what the help says)
2/ I never saw any request for this on the forum. I for sure would have commented on that.
Here is the help on that command.
The above help makes perfect logical sense.Text_GetActive
Returns a numerical value indicating the object ID number of the currently selected text object; returns a value of -1 if no text objects are currently selected.
Why would one use this command if it always returned a true answer (an object ID) even if no text was highlighted on the chart. How would the command know which one to return if nothing was active on the screen which is exactly what it was doing. When an object is not highlighted the command is suppose to return -1 and that is the way it logically should work. I (and probably many) have programmed very large amounts of code to use this command exactly this way. The way it is working in beta 3 renders the command effectively useless. Therefore what you essentially are saying is TSS has listened to users who are requesting that this command be made completely disfunctional when it was in fact working perfectly already. Are you sure it is not a TS employee asking for this hoping you will actually make the mistake of listening to them? It would be nice if Andrew would comment on this because your response is highly suspect.
If TSS is going to make this kind of a change, at the very least one should have an option to set that command to act the way it was intended in the help. If this command does act differently on TS then it would be wise to make a Text_GetActive_MC command that matches the help and it is very easy for the users to change all their code to match this with a simple search and replace. That way you get the best of both worlds (better than an option actually). Another way would be to have a option command that is placed in front of this command. Such as Option = "TS" or Option = "MC". However a warning that such as change is coming is certainly in order.
To be honest, this is a little scary. As stated above, I think there has to be a miscommunication here.
John.
Last edited by bowlesj3 on 06 May 2010, edited 45 times in total.
- TJ
- Posts: 7675
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1018 times
- Been thanked: 2202 times
Hi Bob,
Here is an explaination of what is suppose to happen and what is happening in MC 6.0 beta 3. It also explains the signficance of the change they have made.
Version MC - MC 6.0 beta2 and before:
What is suppose to happen:
Text_GetActive is suppose to return -1 if no text has been highlighted on the screen. Therefore if you highlight text the command returns the ID number for that text. Then if you click the background to unhighlight that text it then starts to return -1 again. This matches exactly what is on the help. If the user highlights a different text without clicking the background the command changes to return the new text ID number. If text_new creates text but it has not been highlighted the command returns -1. Therefore this command can be used to act as a way for the user to interactively control MC to execute studies. All they have to do is put letters out on the chart and they can interactively command MC to do whatever they want (within the limits of EL of course). They can put arrow drops out, highlight them and use this to feed data into their EL code (on the RSI subchart #2 or the main chart). They can use this interactive function wth Text, Arrows or Trend Lines. Very very powerful.
Version TS - MC 6.0 beta3:
What is happening now (that makes no sense what so ever):
Now (as of beta 3) Text Active returns an ID number. It never returns -1. Therefore you can not turn off this command if you click the background. I do not know how it selects the ID number. I think it is the last text that was put on the screen by the Text_New command. This goes directly against what the help says. When I discovered this, I immediately removed Beta 3 because at least 5 of my studies rely on this command operating properly and I am effectively dead in the water without it.
Here is the important part.
Users who are programmed for "Version MC" using these Whatever_GetActive commands for interactive input into MC can not longer do so. THERE IS NO WORK AROUND. On the other hand users new to MC (who can still use TradeSation) can also use the "Version MC" command by simply storing the ID from Text_new/Arw_New/TL_New in a variable as the last one put out on the chart which is what the Beta3 version of the commands are effectively doing. So they have helped these mysterious people complaining and seriously hurt their existing customers and potential new ones with no advantage to TSS at all.
Just how serious this is:
Had I not have stored the old versions of MC so I can still use it interactively, I would be getting out of the trading business as of Today (after 9 years of training). That is the significance of this change TSS put in without consulting users. So I figure the smartest thing TSS can do is creact a special thread saying "MC 6.0 beta3 changes that could stop code from working". Now that would sure get people's attention especially if it came from a well known TSS employee. That would show they care about existing users. Like TJ said. Two steps forward and one step back. The wisest thing users can do is keep their old versions (in the safety deposit box) because you never know what you might loose and according to the answer I got, just maybe you will NEVER GET IT BACK.
John.
Here is an explaination of what is suppose to happen and what is happening in MC 6.0 beta 3. It also explains the signficance of the change they have made.
Version MC - MC 6.0 beta2 and before:
What is suppose to happen:
Text_GetActive is suppose to return -1 if no text has been highlighted on the screen. Therefore if you highlight text the command returns the ID number for that text. Then if you click the background to unhighlight that text it then starts to return -1 again. This matches exactly what is on the help. If the user highlights a different text without clicking the background the command changes to return the new text ID number. If text_new creates text but it has not been highlighted the command returns -1. Therefore this command can be used to act as a way for the user to interactively control MC to execute studies. All they have to do is put letters out on the chart and they can interactively command MC to do whatever they want (within the limits of EL of course). They can put arrow drops out, highlight them and use this to feed data into their EL code (on the RSI subchart #2 or the main chart). They can use this interactive function wth Text, Arrows or Trend Lines. Very very powerful.
Version TS - MC 6.0 beta3:
What is happening now (that makes no sense what so ever):
Now (as of beta 3) Text Active returns an ID number. It never returns -1. Therefore you can not turn off this command if you click the background. I do not know how it selects the ID number. I think it is the last text that was put on the screen by the Text_New command. This goes directly against what the help says. When I discovered this, I immediately removed Beta 3 because at least 5 of my studies rely on this command operating properly and I am effectively dead in the water without it.
Here is the important part.
Users who are programmed for "Version MC" using these Whatever_GetActive commands for interactive input into MC can not longer do so. THERE IS NO WORK AROUND. On the other hand users new to MC (who can still use TradeSation) can also use the "Version MC" command by simply storing the ID from Text_new/Arw_New/TL_New in a variable as the last one put out on the chart which is what the Beta3 version of the commands are effectively doing. So they have helped these mysterious people complaining and seriously hurt their existing customers and potential new ones with no advantage to TSS at all.
Just how serious this is:
Had I not have stored the old versions of MC so I can still use it interactively, I would be getting out of the trading business as of Today (after 9 years of training). That is the significance of this change TSS put in without consulting users. So I figure the smartest thing TSS can do is creact a special thread saying "MC 6.0 beta3 changes that could stop code from working". Now that would sure get people's attention especially if it came from a well known TSS employee. That would show they care about existing users. Like TJ said. Two steps forward and one step back. The wisest thing users can do is keep their old versions (in the safety deposit box) because you never know what you might loose and according to the answer I got, just maybe you will NEVER GET IT BACK.
John.
Last edited by bowlesj3 on 06 May 2010, edited 1 time in total.
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
I have not been following this issue closely, but IF it is the case that TS handles these keywords differently and MC was updated for better EasyLanguage compatibility, then the solution is obvious as TJ suggested - add an MC specific keyword that has the more expressive behavior (as it's described here that it used to have) and simply document the difference so users can have either behavior including the more powerful one, and EL compatibility is also maintained.
Exactly Bruce and TJ. Seems we are all on the same page. In fact TSS was too with this command. bartype_ex which is an extension of bartype as I was told by Super. So a command Text_GetActive_ex is fine with me. Like I said we just do a search and replace and all is well again. Obviously Arw_GetActive_ex and TL_GetActive_ex would be included. While you are at it any not Arc_GetActive_ex
Just experienced an extremely odd and scary problem.
My trading buddy (via Skype) and I were chatting like usual. We were talking about some setups, calling out our buy or sell stop entries. Then we realized something, our prices were not matching at all (from data feed). I exclaimed to him "it's absolutely your side! Both my IQFeed and Zen Fire are showing exact same price, my side is correct!".
Wrong. After a couple minutes I realized my side was in error. What was wrong is the chart itself (actually, about 4 charts, all charts open in MC at that time) were all DELAYED. They were delayed like 3 or 4 minutes. The actual time stamp at the bottom of the chart was showing 3-4 minutes ago, even as bars were forming in "real time" on a range chart. Every chart was this same way --- 6 range, 12 range, 1-hour chart, 5 minute chart, all of them.
I couldn't believe what I was seeing. I even checked the Status Line, and it showed the Bid/Ask also "delayed" by this same time frame! The charts were basically delayed, for no apparent reason, and again both Zen Fire and IQFeed were matching identically --- this is not an actual data feed problem -- and my friends Zen Fire working perfectly at same time.
So, I exited MultiCharts and QuoteManager. When I re-loaded, everything was fine.
Still, you can imagine had I not noticed this I would have taken a trade using delayed data! And same thing with automated strategies! Extremely, extremely scary.
Ideas?
Mike
My trading buddy (via Skype) and I were chatting like usual. We were talking about some setups, calling out our buy or sell stop entries. Then we realized something, our prices were not matching at all (from data feed). I exclaimed to him "it's absolutely your side! Both my IQFeed and Zen Fire are showing exact same price, my side is correct!".
Wrong. After a couple minutes I realized my side was in error. What was wrong is the chart itself (actually, about 4 charts, all charts open in MC at that time) were all DELAYED. They were delayed like 3 or 4 minutes. The actual time stamp at the bottom of the chart was showing 3-4 minutes ago, even as bars were forming in "real time" on a range chart. Every chart was this same way --- 6 range, 12 range, 1-hour chart, 5 minute chart, all of them.
I couldn't believe what I was seeing. I even checked the Status Line, and it showed the Bid/Ask also "delayed" by this same time frame! The charts were basically delayed, for no apparent reason, and again both Zen Fire and IQFeed were matching identically --- this is not an actual data feed problem -- and my friends Zen Fire working perfectly at same time.
So, I exited MultiCharts and QuoteManager. When I re-loaded, everything was fine.
Still, you can imagine had I not noticed this I would have taken a trade using delayed data! And same thing with automated strategies! Extremely, extremely scary.
Ideas?
Mike
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Sirs,
Firstly, let me reassure you, that my post was approved by Dennis and Andrew and there is no miscommunication or misunderstanding there.
Text_GetActive and Arw_GetActive behavior was changed in order to be fully compatible with Easy Language. We did it because of numerous customer complaints to match the behavior of Multicharts with TS.
This change had been reported in this forum: http://forum.tssupport.com/viewtopic.php?t=6946
Best regards,
Dave
Firstly, let me reassure you, that my post was approved by Dennis and Andrew and there is no miscommunication or misunderstanding there.
Text_GetActive and Arw_GetActive behavior was changed in order to be fully compatible with Easy Language. We did it because of numerous customer complaints to match the behavior of Multicharts with TS.
This change had been reported in this forum: http://forum.tssupport.com/viewtopic.php?t=6946
We understand that it may cause inconveniences for some users and plan to add the MC version of the keywords in the future.BUGS FIXED
• Indicators are calculated differently in MultiCharts and TS (if they contain Text_GetActive,, TL_GetActive).
Get_Active returns the last drawing that was changed (eg. created or changed color or selected with a mouse).How could that work if all text is active? What if I have 20 different text objects on my chart? Which ID would it return? Am I missing something here?
Best regards,
Dave
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Hi Mike.After a couple minutes I realized my side was in error. What was wrong is the chart itself (actually, about 4 charts, all charts open in MC at that time) were all DELAYED.
Something similar is happening to me.
I have 2 charts (both 1 minute), different time stamps, and from time to time, one of them have a 1 to 2 minute delay relative to the other

Is this normal? I never noticed this before in previous versions

During this weekend I'll configure QM to eSignal feed since I'm going to cancel my IQFeed service, and I'm crossing my fingers that all my indicators work properly with the new feed.
Regards,
Fernando
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
During those wild 30 minutes free fall in the US, I had almost 5 minutes delayed chart data
3 things could have generated this:
1- the computer
2- MC
3- or the data feed (IQFeed)
I use MC since version 4, always with IQFeed, always the same PC, and never saw this type of delay before
Did any one notice any chart delay during this period with other data feed or better yet, also with IQFeed?
Fernando

3 things could have generated this:
1- the computer
2- MC
3- or the data feed (IQFeed)
I use MC since version 4, always with IQFeed, always the same PC, and never saw this type of delay before

Did any one notice any chart delay during this period with other data feed or better yet, also with IQFeed?
Fernando
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
You may want to pull up task manager and see if any of your cores/CPUs are maxed out at 100% (not just the overall CPU % figure) - it could be that indicator calculations are bogging it down in the busiest markets and it's just taking a while to catch up in periods of extremely hectic activity. I'm not saying that's what's happening for sure - but you need to check your CPU usage on an individual CPU basis to be sure and to rule that out.
I've got a Core i7 920 overclocked to 4ghz, 12GB, MC runs at about 2% load, I keep a widget open at all times to monitor cpu and memory load. It was nothing at all like that.
It wasn't during the 1,000 point drop in the afternoon, it was "business as usual" during mid-morning, after the open.
It wasn't the data feed. Zen Fire and IQFeed both had identical problem at same exact time, while friends Zen Fire is fine? No way. It's not the data feed.
I've never seen it prior to beta 3.
I'm hoping MC engineers can think of something that changed between beta 2 and beta 3 that could cause such a thing.
Mike
It wasn't during the 1,000 point drop in the afternoon, it was "business as usual" during mid-morning, after the open.
It wasn't the data feed. Zen Fire and IQFeed both had identical problem at same exact time, while friends Zen Fire is fine? No way. It's not the data feed.
I've never seen it prior to beta 3.
I'm hoping MC engineers can think of something that changed between beta 2 and beta 3 that could cause such a thing.
Mike
- RobotMan
- Posts: 375
- Joined: 12 Jul 2006
- Location: Los Altos, California, USA
- Has thanked: 31 times
- Been thanked: 13 times
- Contact:
That's what happens in fast markets. You put an order in and it gets filled where your chart has not traded yet. It's a weird feeling when you get so much slippage, but usually it means the market really wants to go in your direction.During those wild 30 minutes free fall in the US, I had almost 5 minutes delayed chart data
There are two different streams of info flowing. The chart data and the order "data". When you hear someone say something like, "wow, Zen-Fire is really fast", it means their market order got filled and confirmed almost instantly. It doesn't mean the chart data is updating really quickly. That's why co-location is so important to a big trader. Although 5 minutes seems like a long time, it's probably a combination of all three of the possible reasons you stated.
I was already done for the day when the market dropped and didn't get to see it. Not my cup of tea anyway.
To Dave Masalov
They way you handled the change scares me. I gave it thought the night after the first post about Text_GetActive to explain the way you changed it. I took the morning off the next day to backup all my trading related software including my programs and MC 2.1.999.999 and MC 6.0 beta(s) including beta2 which has the Text_GetACtive working as per the help and I put this copy in the Safety Deposite box. I did not look at the market until later in the day. Users need to protect themselves.We understand that it may cause inconveniences for some users and plan to add the MC version of the keywords in the future.
Last edited by bowlesj3 on 07 May 2010, edited 1 time in total.
Code: Select all
I was already done for the day when the market dropped and didn't get to see it. Not my cup of tea anyway.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
After a couple minutes I realized my side was in error. What was wrong is the chart itself (actually, about 4 charts, all charts open in MC at that time) were all DELAYED.
Hi Mike.
Something similar is happening to me.
I have 2 charts (both 1 minute), different time stamps, and from time to time, one of them have a 1 to 2 minute delay relative to the other
Is this normal? I never noticed this before in previous versions
During this weekend I'll configure QM to eSignal feed since I'm going to cancel my IQFeed service, and I'm crossing my fingers that all my indicators work properly with the new feed.
Regards,
Fernando
Dear ctrlbrk and arnie,
Could you please send us your log files so we can investigate the issues?
You can find log files here "%USERPROFILE%\Local Settings\Application Data\TS Support\MultiCharts\".
You should paste this line in Start --> Run and in the window that will pop up make a zip-folder. Please send this zip–folder to dmasalov@multicharts.com.
Best regards,
Dave
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Bruce,It appears to me that as of beta 3, if you have an indicator that calls a function, and the indicator is on a chart window, and you modify the function and verify it from PL Editor, the chart window says "verifying..." until you click over to the indicator and re-verify it, even though it has not changed.
We fail to reproduce the issue on our end. Could you please specify, what OS do you have and send the zip-file with your techniques as well as your workspaces to dmasalov@multicharts.com.
Best regards,
Dave
Regarding the TSS plan to eventually have a Text_GetActive (TS Version) and probably a Text_GetActive_ex (extended MultiCharts Version) if TSS employed my idea of using the (beta help) as a design framework which precedes beta programming work then the error TSS made would not have occured in that users would be giving feedback such that they would know in advance that this change was coming and they would have recommended the use of these commands before the commands came out rather than your having to react after the fact.
What if it is a more obscure command, you release a beta but have changed the command and the trader is using an automated system and has no idea you made this change without warning. I don't think traders in this situation would be happy if it causes losses in their system. However if they have been reading your beta-help and giving feedback to lock your beta help so it will not change before you start your beta programming when this I figure will be much more impressive to clients, much more efficient, much less risky to your company.
Think of beta help as an enhanced thinking cap which goes on before you start beta programming. Enhanced because you share it with the users (the ultimate in clear communication of what you intend on doing). Once you are happy with the beta help it becomes locked and you start the beta programming. You may realize things during prgogramming and go back to the users to communicate it back using the beta help on that command. Once it is cleared up you lock it again and complete the beta programming and release the beta. Once the official release it out there the Beta help becomes the real help for the final release.
What you did with Text_GetActive displays "lack of thinking cap" after the fact reacting. The bottom line is you have to create this help anyways so why not create it before the programming rather than after and get the benefit of the "enhance thinking cap". In time you will perfect this technique (probably very quickly because the users will be feeding you ideas to make the method better). What I am saying is if you try it and the idea first craps out do not give up because you probably just need added ideas required to make it work.
What if it is a more obscure command, you release a beta but have changed the command and the trader is using an automated system and has no idea you made this change without warning. I don't think traders in this situation would be happy if it causes losses in their system. However if they have been reading your beta-help and giving feedback to lock your beta help so it will not change before you start your beta programming when this I figure will be much more impressive to clients, much more efficient, much less risky to your company.
Think of beta help as an enhanced thinking cap which goes on before you start beta programming. Enhanced because you share it with the users (the ultimate in clear communication of what you intend on doing). Once you are happy with the beta help it becomes locked and you start the beta programming. You may realize things during prgogramming and go back to the users to communicate it back using the beta help on that command. Once it is cleared up you lock it again and complete the beta programming and release the beta. Once the official release it out there the Beta help becomes the real help for the final release.
What you did with Text_GetActive displays "lack of thinking cap" after the fact reacting. The bottom line is you have to create this help anyways so why not create it before the programming rather than after and get the benefit of the "enhance thinking cap". In time you will perfect this technique (probably very quickly because the users will be feeding you ideas to make the method better). What I am saying is if you try it and the idea first craps out do not give up because you probably just need added ideas required to make it work.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
I think the next highest replay feature priority after fixing the missing replay slider speeds (which of course has been done) is the space bar shortcut key to pause and restart the replay. It is more important than the favorite speed idea, etc. If there are other competing uses for the spacebar maybe a different key could be used.
Dear bowlesj3 and brendanh,I understand the design logic of not wanting autotrading to be accidentally enabled by keyboard mishap, but if the shortcut keys are 3 key combinations this will not happen, and anyway there is a confirmation dialogue. Disclaim any responsibility from TSS against losses arising from MC automation, but please be aware of how MC is used in the real world by systems traders, and give us shortcut keys for the following automation functions:
1. Enable\disable automation (preferably different shortcut keys for each).
2. Buttons in dialogues when automation is exited. Simply underline a letter in the button text to denote the shortcut key as per normal Windows standards.
We will give users the possibility to customize all commands in the next version of MultiCharts.
Sounds good Dave.
Just one more thing I want to add to that "beta help" idea. If you ever try it and find that your competition gets too much of a jump on your ideas one of these secondary ideas to make it work could be "only letting users see it who have submitted very useful ideas etc" in other words restricting it to those on your side instead of against you.
Just one more thing I want to add to that "beta help" idea. If you ever try it and find that your competition gets too much of a jump on your ideas one of these secondary ideas to make it work could be "only letting users see it who have submitted very useful ideas etc" in other words restricting it to those on your side instead of against you.
I experienced the exact same thing again. In fact, it is happening right now.Dear ctrlbrk and arnie,After a couple minutes I realized my side was in error. What was wrong is the chart itself (actually, about 4 charts, all charts open in MC at that time) were all DELAYED.
Could you please send us your log files so we can investigate the issues?
You can find log files here "%USERPROFILE%\Local Settings\Application Data\TS Support\MultiCharts\".
You should paste this line in Start --> Run and in the window that will pop up make a zip-folder. Please send this zip–folder to dmasalov@multicharts.com.
Best regards,
Dave
I think your post was missing part of the info. The .zip file is 34mb for just the Logs folder, I'm assuming your email cannot handle that. Was there just one specific folder you needed? Or I could break it up until a multi-file rar.
Mike
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
The bottom line is you have to create this help anyways so why not create it before the programming rather than after and get the benefit of the "enhance thinking cap". In time you will perfect this technique (probably very quickly because the users will be feeding you ideas to make the method better). What I am saying is if you try it and the idea first craps out do not give up because you probably just need added ideas required to make it work.
Dear bowlesj3,Just one more thing I want to add to that "beta help" idea. If you ever try it and find that your competition gets too much of a jump on your ideas one of these secondary ideas to make it work could be "only letting users see it who have submitted very useful ideas etc" in other words restricting it to those on your side instead of against you.
It is a very good idea, indeed. We will try to update the help when releasing new versions in the future. However it is not realistic for the moment.
Dear Mike,I experienced the exact same thing again. In fact, it is happening right now.
I think your post was missing part of the info. The .zip file is 34mb for just the Logs folder, I'm assuming your email cannot handle that. Was there just one specific folder you needed? Or I could break it up until a multi-file rar.
Mike
Excuse me for not expressing myself clearly. Please send us all log files using http://rapidshare.com/. You can make a multi-file rar as well.
- TJ
- Posts: 7675
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1018 times
- Been thanked: 2202 times
I found Skype is the easiest method to transfer large files....
Excuse me for not expressing myself clearly. Please send us all log files using http://rapidshare.com/. You can make a multi-file rar as well.
Hi Dave,
Regarding this in the beta3 announcement
Here is the main point. Please do not change the beta 2 version functionality in beta 4 by combining the TS beta 3 features into the MC beta 2 version features. "Text_GetHighlighted" is a perfect name for the beta 2 version and it works great for all the huge amount of hours I spent programming with it. If you want to create some sort of combined command then maybe "Text_GetActive_ex" is better for that 3rd version.
Summaried:
Text_GetActive (is really Text_LastChanged - beta 3)
Text_GetActive_Ex (is a mixture of beta 2 and beta 3 versions)
Text_GetHighlighted (does exactly what the beta 2 version did).
So if you did this I (and other users using it for interactive input to their studies) would just recompile my code using Text_GetHighlighted. Not a problem.
Another thing. I have been considering writing something to scan all the EL code in those text files that will tell me what studies contain a keyword. Maybe some day you could provide this.
Regarding this in the beta3 announcement
and• Indicators are calculated differently in MultiCharts and TS (if they contain Text_GetActive,, TL_GetActive).
It is mildly unfortunate that the TS version command was not "Text_GetLastChanged". I was going to say that "Text_GetActive" is much more appropriate for the text which is currently highlighted. However just writing that sentence made me realize that the functionality in your help suggests that a better name is "Text_GetHighlighted". To enhance your help you might be smart to emphasize that this command can be used to make MC's EL code interactive and explain a few examples of how it might be used. Maybe create some sample scripts that start Interactive_whatever. Mention in the help that they start with Interactive_Get_Active returns the last drawing that was changed (eg. created or changed color or selected with a mouse).
Here is the main point. Please do not change the beta 2 version functionality in beta 4 by combining the TS beta 3 features into the MC beta 2 version features. "Text_GetHighlighted" is a perfect name for the beta 2 version and it works great for all the huge amount of hours I spent programming with it. If you want to create some sort of combined command then maybe "Text_GetActive_ex" is better for that 3rd version.
Summaried:
Text_GetActive (is really Text_LastChanged - beta 3)
Text_GetActive_Ex (is a mixture of beta 2 and beta 3 versions)
Text_GetHighlighted (does exactly what the beta 2 version did).
So if you did this I (and other users using it for interactive input to their studies) would just recompile my code using Text_GetHighlighted. Not a problem.
Another thing. I have been considering writing something to scan all the EL code in those text files that will tell me what studies contain a keyword. Maybe some day you could provide this.
Last edited by bowlesj3 on 07 May 2010, edited 3 times in total.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
I have seen that kind of thing happen a good bit. My suggestion would to implement a bad tick filter method, kicking out trade ticks if they're too far from the last trade in percentage terms or if they're otherwise invalid (zero, negative, etc.)
Dear Bruce and geizer,Back-filter might be interesting. Also this need to be launched on demand.
If users are given an option to confirm the correction of each suspected bad tick - I can see some use of it.
Thinking the percentage might not be reliable enough. How about using Standard Deviation function to filter suspected abnormal ticks? But even then this should not be relied upon in thin markets. Extended trading hours being one example.
Our developers are already working on such filter. It will be implemented in MultiCharts in the future.
As far rating the value of the beta 2 text_getactive versus the beta 3 text_getactive I remember first finding out about the beta 2 version and I instantly saw a great deal of value in it. I still can not see any value in the beta 3 version and can see all sorts of work arounds to achieve that same function if I did have a use for it but absolutely no way to work around the beta 2 version being missing.
Maybe some of those users who complained could explain some way of making good use of the beta 3 version or the TSS staff could pass it on. I am thinking in terms of saving time or making money.
Maybe some of those users who complained could explain some way of making good use of the beta 3 version or the TSS staff could pass it on. I am thinking in terms of saving time or making money.
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
This is really very simple - all EasyLanguage keywords should work as closely as possible to TS for language compatibility, in order to maximize the value of the MultiCharts platform as an EasyLanguage compatible platform. Separately, extended versions of keywords should be provided where appropriate to extend this functionality in areas that are MultiCharts specific. The fact that an EasyLanguage keyword doesn't have an immediately obvious use (which happens all the time - there are dozens of deprecated keywords that are kept purely for backwards compatibility but aren't really very useful anymore) isn't as important as the fact that it needs to work like it does on TS for compatibility reasons - as a separate issue, the extended keywords should be as functional as they can be made to be, whether TS supports those functions or not.
The oversight that was made here was to have an EasyLanguage keyword that did something that broke TS compatibility in the first place - keywords with a different behavior should be different keywords not the same one TS has but doing something different (even if it's clearly arguably more useful), so the compatibility issue does not arise and then there's freedom to focus on the most useful possible behavior apart from compatibility.
MultiCharts is doing exactly the right thing - fixing the keyword for compatibility, and introducing a new keyword with the extended functionality. It would have been nice if it hadn't happened in quite this order (if the extended keyword had been added at the same time as the original keyword was fixed) or had more clear notice along the way so users would know just what to look for and change when something breaks code compatibility, but it was clearly an oversight and one they're working on correcting so I give them kudos for stepping up and doing the right thing.
Both goals are worthy and separate: 100% EasyLanguage compatibility, and the most useful extended feature set with new keywords.
The oversight that was made here was to have an EasyLanguage keyword that did something that broke TS compatibility in the first place - keywords with a different behavior should be different keywords not the same one TS has but doing something different (even if it's clearly arguably more useful), so the compatibility issue does not arise and then there's freedom to focus on the most useful possible behavior apart from compatibility.
MultiCharts is doing exactly the right thing - fixing the keyword for compatibility, and introducing a new keyword with the extended functionality. It would have been nice if it hadn't happened in quite this order (if the extended keyword had been added at the same time as the original keyword was fixed) or had more clear notice along the way so users would know just what to look for and change when something breaks code compatibility, but it was clearly an oversight and one they're working on correcting so I give them kudos for stepping up and doing the right thing.
Both goals are worthy and separate: 100% EasyLanguage compatibility, and the most useful extended feature set with new keywords.
All true Bruce but it does not answer the question. Here is the point. I have at least 2 times reviewed every single command in the manual looking for a way to use the commands and done the same for every single non strategy related study and function that comes with MC (except strategies that line up with my strategy). I do it more than once because of what you said and at times knowledge of one can make a use for another appear. So my question is for that purpose (except this one stands out). Maybe this is a non beta 3 topic.
Last edited by bowlesj3 on 07 May 2010, edited 6 times in total.
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
Sorry, what's the question?
If the question is what's the use of the current behavior, it's that there are existing indicators that rely on it working that way in EasyLanguage (probably that originated on TS, but one of the advantages of MultiCharts is that it can run EasyLanguage code), and they don't work as they should on MultiCharts.
I don't know the specific details of why it was done this way originally on TS - it's probably a legacy behavior that's been that way for many years if I am understanding the issue reported. I wouldn't be at all surprised to inquire about this at TS and find out nobody can even remember why it was done that way because it's been so long - that happens some times.
Changes to code behavior can be extremely painful - sometimes things that seem clearly like an error or omission become so ingrained in thousands of lines of code that they just can't be changed, and most platform vendors try very hard not to pull the rug out from under anyone relying on an existing behavior. However, beta releases aren't to that standard necessarily, and it's understood that betas are still a work in progress and being reviewed and worked on as apparently was the case here. (Although again, in 20/20 hindsight, I'm sure we all can agree it would have been great if they could have put the new keyword in the same release that fixed the old one, and updated the documentation accordingly with detailed build notes on why it was done and what was done.)
(This was not my issue report originally. It could very well be that the original report came to MultiCharts other than via the forum, for instance by email or live support chat - the forums are largely for peer support, so I wouldn't necessarily expect the person who originally reminded them the behavior doesn't match TS to respond here as they may not even read the forums.)
If the question is what's the use of the current behavior, it's that there are existing indicators that rely on it working that way in EasyLanguage (probably that originated on TS, but one of the advantages of MultiCharts is that it can run EasyLanguage code), and they don't work as they should on MultiCharts.
I don't know the specific details of why it was done this way originally on TS - it's probably a legacy behavior that's been that way for many years if I am understanding the issue reported. I wouldn't be at all surprised to inquire about this at TS and find out nobody can even remember why it was done that way because it's been so long - that happens some times.
Changes to code behavior can be extremely painful - sometimes things that seem clearly like an error or omission become so ingrained in thousands of lines of code that they just can't be changed, and most platform vendors try very hard not to pull the rug out from under anyone relying on an existing behavior. However, beta releases aren't to that standard necessarily, and it's understood that betas are still a work in progress and being reviewed and worked on as apparently was the case here. (Although again, in 20/20 hindsight, I'm sure we all can agree it would have been great if they could have put the new keyword in the same release that fixed the old one, and updated the documentation accordingly with detailed build notes on why it was done and what was done.)
(This was not my issue report originally. It could very well be that the original report came to MultiCharts other than via the forum, for instance by email or live support chat - the forums are largely for peer support, so I wouldn't necessarily expect the person who originally reminded them the behavior doesn't match TS to respond here as they may not even read the forums.)
You jumped me or something. here is the response. It is an extension of the above.
I guess it is just burning curiosity with me to ask "What can this command buy me"? I spent a fair bit of time at break trying to figure out how to use it (of course when the MC version command comes back). Of note, I am on beta2 on the main machine and beta3 on the notebook so I do not have to reload the day again from TWS (the nightly copy over sticks).
And if you question the use of the MC version I can quickly come up with at least 10 very good uses (some for fully automated traders I would think too).
I guess it is just burning curiosity with me to ask "What can this command buy me"? I spent a fair bit of time at break trying to figure out how to use it (of course when the MC version command comes back). Of note, I am on beta2 on the main machine and beta3 on the notebook so I do not have to reload the day again from TWS (the nightly copy over sticks).
And if you question the use of the MC version I can quickly come up with at least 10 very good uses (some for fully automated traders I would think too).
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
Let me see if I can answer that, although I'm sure there are any number of possible answers. In TS, I believe when you select a text object manually with the mouse, it becomes the "active" one, and this command would return that text object. However, if from code, you use commands like Text_SetLocation or Text_SetString on another object, that object then becomes active. The reason for this is probably lost in time - for instance, it might have originally been the thought that users could use this to grab the most recently updated text object without saving its ID in a variable (although to me, that doesn't sound like the best approach and I'm sure it probably doesn't to you either - who knows why it was done that way, but it was...). However, as a work-around, if you want it to always be the one you manually selected, you can simply call text_getactive at the beginning of your calculation, do whatever you're going to do with the other objects, and then at the end, call Text_SetStyle or another similar command on the one you saved originally, making it active again, and thus preserving the one that was manually selected as always the active one. That should be a 100% work-around to make it like what you're wanting it to do by simply saving the value and calling Text_Set* after your calculation on that same original manually selected object.
While it may not be obvious why text_getactive should return an object that you "selected" using text_setlocation etc. instead of manually, it's been that way a long time, so it's important to not break that for the hundreds if not thousands of EL programs out there - and the above method lets you work around this if you want it not to do that. And, of course, an extension that's MC specific can just always return the manually selected one and ignore your programmatic selections.
Make sense?
While it may not be obvious why text_getactive should return an object that you "selected" using text_setlocation etc. instead of manually, it's been that way a long time, so it's important to not break that for the hundreds if not thousands of EL programs out there - and the above method lets you work around this if you want it not to do that. And, of course, an extension that's MC specific can just always return the manually selected one and ignore your programmatic selections.
Make sense?
agree with Bruce,This is really very simple - all EasyLanguage keywords should work as closely as possible to TS for language compatibility, in order to maximize the value of the MultiCharts platform as an EasyLanguage compatible platform. Separately, extended versions of keywords should be provided where appropriate to extend this functionality in areas that are MultiCharts specific.
....
....
TS Support has two options:
1. Focus on making PowerLanguage compatible with EasyLanguage, thus acknowledging EL leadership position and accepting the role of the follower.
2. Change the rules of the game and make PowerLanguage THE NEW STANDARD.
It requires a change how EasyLanguage is percieved both by TS Support team and EL users. This requires the focus on improving EasyLanguage (while maintaining 100% compatibility).
- -What can be improved in EasyLanguage?
-What is the single most important shortcoming of EL? What is 2nd, 3rd?
- - Enhance EL by implementing extended a set of (PL) commands.
- Maintain compatibility with EL
--
Pavel
All true (zero doubt at all): Translation: make it easy to come over and keep clients using MC by giving more than they had before. A no brainer actually (MS used it with Word Perfect so it is not a new marketing strategy).
Regarding how it was done with the Text_GetActive command, my suggestion is that if they know a command is going to run differently for sure they should create a thread in a standard format something like this.
"MC 6.0 b3, Whatever-Command, May not work and why."
Inside the first post explain it.
I am suggesting a new thread for every single command that is going to potentially give a user a very nasty surprise. Had I have seen the above notice it would have cost me a 5 minute read. Instead it cost me 1 hour to install, 1 hour to uninstall (during trading hours because I never thought something like this could ever happen) and a heck of a lot of distraction with forum discussions. TSS surely knows, it is not possible for them to know all the creative uses a user has and just how critical it is to them.
When it comes time for the official release there WILL BE USERS who refuse to use beta out there. They see the short little mention in the release notes and it goes right over their head (kind of like the fine print idea). However this is not good for TSS. What I am suggesting would warn users of the dangers of an upgrade. Better yet, email them in a standard format. Even better do it during the Beta Help stage if they ever use it. Lastly I suppose the ultimate is to provide a warning and list of commands that may not work when the user tries to install (with option(s) to auto-convert to the new command name).
So the above paragraph is still active since the official release is not out yet and as we know there is a command lurking out there for this one. If I can come up with 10 or more very valuable uses for this command to solve problems then there are probably others who can do better and come up with 20. This command is a hot potato is what I am saying. Gee if TSS ever puts in custom tool bars so I can store different colors of arrows to put on the chart very quickly I will be using this command even more (maybe 15 uses for it). Like I said, the MC version of Text_GetActive and Arw_GetActive is a very powerful interactive command.
Regarding how it was done with the Text_GetActive command, my suggestion is that if they know a command is going to run differently for sure they should create a thread in a standard format something like this.
"MC 6.0 b3, Whatever-Command, May not work and why."
Inside the first post explain it.
I am suggesting a new thread for every single command that is going to potentially give a user a very nasty surprise. Had I have seen the above notice it would have cost me a 5 minute read. Instead it cost me 1 hour to install, 1 hour to uninstall (during trading hours because I never thought something like this could ever happen) and a heck of a lot of distraction with forum discussions. TSS surely knows, it is not possible for them to know all the creative uses a user has and just how critical it is to them.
When it comes time for the official release there WILL BE USERS who refuse to use beta out there. They see the short little mention in the release notes and it goes right over their head (kind of like the fine print idea). However this is not good for TSS. What I am suggesting would warn users of the dangers of an upgrade. Better yet, email them in a standard format. Even better do it during the Beta Help stage if they ever use it. Lastly I suppose the ultimate is to provide a warning and list of commands that may not work when the user tries to install (with option(s) to auto-convert to the new command name).
So the above paragraph is still active since the official release is not out yet and as we know there is a command lurking out there for this one. If I can come up with 10 or more very valuable uses for this command to solve problems then there are probably others who can do better and come up with 20. This command is a hot potato is what I am saying. Gee if TSS ever puts in custom tool bars so I can store different colors of arrows to put on the chart very quickly I will be using this command even more (maybe 15 uses for it). Like I said, the MC version of Text_GetActive and Arw_GetActive is a very powerful interactive command.
Last edited by bowlesj3 on 09 May 2010, edited 8 times in total.
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Hey guys, is it me or beta 3 has some sort of "bug" regarding eSignal Data Manager?
At first I thought I couldn't have eSignal and MC open at the same time since that would force Data Manager to lock the password down, but then I closed eSignal software and the same thing happened, every time I call for a symbol in MC, Data Manager locks down.
Since I still have MC 5.5 in my laptop I decided to test this and with 5.5 version there's no problem with Data Manager.
I have both eSignal and MC opened, calling symbols in both of them and Data Manager continues to run.
Man, I chose the wrong time to switch data feed
Let me try with beta 2 to see if this still happens.
I'll be in touch...
At first I thought I couldn't have eSignal and MC open at the same time since that would force Data Manager to lock the password down, but then I closed eSignal software and the same thing happened, every time I call for a symbol in MC, Data Manager locks down.
Since I still have MC 5.5 in my laptop I decided to test this and with 5.5 version there's no problem with Data Manager.
I have both eSignal and MC opened, calling symbols in both of them and Data Manager continues to run.
Man, I chose the wrong time to switch data feed

Let me try with beta 2 to see if this still happens.
I'll be in touch...
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Unfortunately, beta 2 have the same reaction, Data Manager locks down.
See Image attached where you can see eSignal software unable to access data.
I open eSignal, then MC, and after calling a symbol in MC, Data Manager locks.
Apparently, I'm going back to version 5.5 since, at least in my laptop, is the only one capable to deal with both programs at the same time
Sorry for the image size but it's my true desktop size.
See Image attached where you can see eSignal software unable to access data.
I open eSignal, then MC, and after calling a symbol in MC, Data Manager locks.
Apparently, I'm going back to version 5.5 since, at least in my laptop, is the only one capable to deal with both programs at the same time

Sorry for the image size but it's my true desktop size.
- Attachments
-
- print-desktop.gif
- (196.03 KiB) Downloaded 17555 times
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
Henrik,
I just do something like this in my strats:
Mike
I just do something like this in my strats:
Code: Select all
inputs:
target1 (20);
stoploss (20);
vars:
TickSize (MinMove/PriceScale);
SetStopContract;
SetStopLoss((stoploss * TickSize) * BigPointValue);
SetProfitTarget((target1 * TickSize) * BigPointValue);
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
I don't know what to say.
I've just installed MC 5.5 version and I was
Th same thing happened again. As soon as I call for a symbol on MC and if eSignal software is open, Data Manager blocks the password and despite MC continues to be able to receive requested data, eSignal software don't as shown in the picture attached above.
Now I don't know what to thought since the combination of MC 5.5 and eSignal software don't produce this situation in my laptop
I've already reinstalled eSignal and the problem continues.
What could be the cause of this?
I've just installed beta 3 again, waiting for tomorrow TSSuppot can have a look at this.
Regards,
Fernando
I've just installed MC 5.5 version and I was

Th same thing happened again. As soon as I call for a symbol on MC and if eSignal software is open, Data Manager blocks the password and despite MC continues to be able to receive requested data, eSignal software don't as shown in the picture attached above.
Now I don't know what to thought since the combination of MC 5.5 and eSignal software don't produce this situation in my laptop

I've already reinstalled eSignal and the problem continues.
What could be the cause of this?
I've just installed beta 3 again, waiting for tomorrow TSSuppot can have a look at this.
Regards,
Fernando
Connection with MBT:
On Sunday afternoon MBT-Login is not possible for some hours.
When you have open MC in this time with realtime-data and download-history => yes than MC trys to login in background to MBT without a stop.
But after some mismatched logins MBT locks the MBT-account.
Its very annoying
Its the second weekend 
Now I can't trade until I chatted mit MBT and unlock the account.
suggestion: MC could stop try login after 3 attemps!
On Sunday afternoon MBT-Login is not possible for some hours.
When you have open MC in this time with realtime-data and download-history => yes than MC trys to login in background to MBT without a stop.
But after some mismatched logins MBT locks the MBT-account.
Its very annoying


Now I can't trade until I chatted mit MBT and unlock the account.
suggestion: MC could stop try login after 3 attemps!
Last edited by Henrik on 09 May 2010, edited 1 time in total.
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact:
That's a good point - hammering the server will cause your account to be locked for IB as well, and MB does have some maintenance times, although they're down from what they were last year because as they reworked their process to support MT intregation they were able to reduce the daily downtime somewhat as part of that process. (There used to be three different windows of times every 24 hours it went down.)
A common software approach to this type of problem is what we call an exponential back-off. In other words, if login fails, try again in X minutes/seconds, and if that fails, try in 2X minutes/seconds, and if that fails, try in 4X minutes/seconds, etc. up to some maximum time that's designed to avoid being flagged as abusive, yet is frequently enough to get you back on in a reasonable amount of time. Remember, although it's tempting to say you want in the very second it's possible, the vast majority of such downtimes are because of things like internet disruptions or actual server down time, and hammering the server with constant login requests is the sort of thing that will make the broker want to not have you as an account because you may (likely unintentionally) cause them problems.
A common software approach to this type of problem is what we call an exponential back-off. In other words, if login fails, try again in X minutes/seconds, and if that fails, try in 2X minutes/seconds, and if that fails, try in 4X minutes/seconds, etc. up to some maximum time that's designed to avoid being flagged as abusive, yet is frequently enough to get you back on in a reasonable amount of time. Remember, although it's tempting to say you want in the very second it's possible, the vast majority of such downtimes are because of things like internet disruptions or actual server down time, and hammering the server with constant login requests is the sort of thing that will make the broker want to not have you as an account because you may (likely unintentionally) cause them problems.
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
With the markets opened I could see that the problem is with eSignal Data Manager and not with the software itself.
When I open MC, eSignal Data Manager opens and my charts start to be updated, so far so good.
The problem is when I open or even reload a chart. Data Manager turns red and MC stops to update the charts.
Even after closing Data Manager and reopen it again, it continuous after a while to block the connection.
I need to close MC and then reopen it again, without ever open a chart because otherwise, I lose the connection.
At this moment I have also eSignal software opened with a quote board and everything is working fine, but like in MC, if I call a new symbol, the connection is cut off again.
When I open MC, eSignal Data Manager opens and my charts start to be updated, so far so good.
The problem is when I open or even reload a chart. Data Manager turns red and MC stops to update the charts.
Even after closing Data Manager and reopen it again, it continuous after a while to block the connection.
I need to close MC and then reopen it again, without ever open a chart because otherwise, I lose the connection.
At this moment I have also eSignal software opened with a quote board and everything is working fine, but like in MC, if I call a new symbol, the connection is cut off again.
I created a base Interactive script that anyone can use to interactively exacute a study from the chart screen (just insert whatever you want it to do in the correct place within a copy of this base script). As an example, you might want it to clear old trend lines from your chart prior to a certain time or date. Insert that loop in this script and you just highlight the letter on the chart and it is done. Once it is complete you remove the highlight.
It will not work on Beta 3 because it depends on the Text_GetActive old MC version logic but it will work on any version of MC before Beta 3. When TSS restablishes the MultiCharts Based logic behind this command you will need to make the required adjustment.
http://forum.tssupport.com/viewtopic.php?p=33280#33280
It will not work on Beta 3 because it depends on the Text_GetActive old MC version logic but it will work on any version of MC before Beta 3. When TSS restablishes the MultiCharts Based logic behind this command you will need to make the required adjustment.
http://forum.tssupport.com/viewtopic.php?p=33280#33280
I've found the same bug which was discussed many times for beta 1 and beta2. If you change the symbol in the same chart you get the data mixed with the old and new symbol. I thought it was fixed, but it seems to be the same problem.
Seems to me a cache problem. I changed the symbol in the chart from @FGBL to @FESX. The result is attached as a screenshot.
Kind regards.
Mike
Seems to me a cache problem. I changed the symbol in the chart from @FGBL to @FESX. The result is attached as a screenshot.
Kind regards.
Mike
- Attachments
-
- MC6Beta3bug.png
- (16.02 KiB) Downloaded 17556 times
- RichardTodd
- Posts: 12
- Joined: 18 Feb 2010
- Location: Dallas
- Been thanked: 2 times
- Contact:
I just want to point out that in beta3 the range bars still have bad uptick/downtick counts, as described here:
http://forum.tssupport.com/viewtopic.php?t=7155
I haven't noticed an official response in that thread and it's starting to fall away into the forum history. In short, the numbers are wacky, and some of the bars have more reported uptick/downtick volume than the total volume so far for the day! It happens on several datafeeds, but only on range bars as far as I know.
thanks,
Richard
http://forum.tssupport.com/viewtopic.php?t=7155
I haven't noticed an official response in that thread and it's starting to fall away into the forum history. In short, the numbers are wacky, and some of the bars have more reported uptick/downtick volume than the total volume so far for the day! It happens on several datafeeds, but only on range bars as far as I know.
thanks,
Richard
Walk Forward Performance Reports
I played a little with the Walk Forward Optimizer of MC and was wondering about the way MC handles Walk Forward. It seems to just show the results for the single In-Sample and Out-of-Sample Periods but does not combine them to one whole backtest.
Other vendors (NT or AB) have the ability to choose (or even write an own) target criteria and the backtester combines the single OOS Trades (choosen by the target criteria) to one single performance report (equity curve and performance numbers).
Is it planned to implement this ability also in MC?
Other vendors (NT or AB) have the ability to choose (or even write an own) target criteria and the backtester combines the single OOS Trades (choosen by the target criteria) to one single performance report (equity curve and performance numbers).
Is it planned to implement this ability also in MC?
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Mike,I've found the same bug which was discussed many times for beta 1 and beta2. If you change the symbol in the same chart you get the data mixed with the old and new symbol. I thought it was fixed, but it seems to be the same problem.
Seems to me a cache problem. I changed the symbol in the chart from @FGBL to @FESX. The result is attached as a screenshot.
Kind regards.
Mike
Please make sure that the "Merge Data Sources into a Single Chart" checkbox in the Format Instrument --> Instrument is unchecked.
Dear Henrik,Suggestion:
All TP and SL - commands based on profit.
for example: setprofittarget(100) => 100 $ TP
Why not based on pips?
Please add commands with pips instead of amount...
for example: setprofittargetpips(30) => 30 pips TP
this make everything easier, for commands like setpercenttrailing etc.
I have forwarded your suggestions to our programmers. They will consider a possibility of such implementation.
Connection with MBT:
On Sunday afternoon MBT-Login is not possible for some hours.
When you have open MC in this time with realtime-data and download-history => yes than MC trys to login in background to MBT without a stop.
But after some mismatched logins MBT locks the MBT-account.
Its very annoying Its the second weekend
Now I can't trade until I chatted mit MBT and unlock the account.
suggestion: MC could stop try login after 3 attemps!
Dear Henrik and Bruce,That's a good point - hammering the server will cause your account to be locked for IB as well
I would suggest you to use Offline Data Server Mode on Sunday to avoid this problem. (File --> Preferences --> Data Server Mode)
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Richard,I just want to point out that in beta3 the range bars still have bad uptick/downtick counts, as described here:
http://forum.tssupport.com/viewtopic.php?t=7155
I haven't noticed an official response in that thread and it's starting to fall away into the forum history. In short, the numbers are wacky, and some of the bars have more reported uptick/downtick volume than the total volume so far for the day! It happens on several datafeeds, but only on range bars as far as I know.
thanks,
Richard
Our engineers have confirmed it is a bug, which will be fixed in the official release of MultiCharts 6.0
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear duration,Hello,
Just to let you know that only the strategy analysis sheet is exported to .xls from the Portfolio Backtester (using Office 2010 beta 64 bit).
Office 2010 is a relatively new application. Portfolio Backtester was not designed for it. This issue will be fixed soon.
Dear Henrik,Why I can't make a walk forward optimizion only in a chart, but not in the portfolio optimizer?
Its annoying because if I make a walk forward optimizion in a chart, I can't use the other charts or workspace because the progress-window is blocking/locking MC....
The fact that portfolio backtesting uses all cores makes it unrealistic to access your charts when portfolio optimization is running. We would recommend you to use the second computer for that purpose.
Discovered a problem that I don't know how to overcome. If there is something I don't know please help me to find a solution, otherwise it seems to me like a small bug.
The problem:
Maximizing a subchart is impossible when Title Bar is set to "Off" in chart window properties.
Right click on the Chart is showing "Maximize subchart" option ... but it's unavailable (is always gray).
I also updated the list of keyboard shortcuts requesting a "maximize subchart" shortcut in this thread (item #31):
http://forum.tssupport.com/viewtopic.ph ... g+subchart
Please can someone from TS Support investigate the matter.
Thanks
--
Pavel
added later
The above problem is a direct consequence of another inconvenience/bug (which I am trying to avoid by disabling chart title bars) apparently very old issue:
http://forum.tssupport.com/viewtopic.php?t=3552
Please consider both of these issues together.
The problem:
Maximizing a subchart is impossible when Title Bar is set to "Off" in chart window properties.
Right click on the Chart is showing "Maximize subchart" option ... but it's unavailable (is always gray).
I also updated the list of keyboard shortcuts requesting a "maximize subchart" shortcut in this thread (item #31):
http://forum.tssupport.com/viewtopic.ph ... g+subchart
Please can someone from TS Support investigate the matter.
Thanks
--
Pavel
added later
The above problem is a direct consequence of another inconvenience/bug (which I am trying to avoid by disabling chart title bars) apparently very old issue:
http://forum.tssupport.com/viewtopic.php?t=3552
Please consider both of these issues together.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Mike,Dave,
I just wanted to pause a moment and say "THANK YOU" for your attention to this thread, I find it quite comforting and a welcome improvement from the relative silence in recent weeks from MC staff
THANKS DAVE!
Mike
You are welcome.
Dear Pavel,Discovered a problem that I don't know how to overcome. If there is something I don't know please help me to find a solution, otherwise it seems to me like a small bug.
The problem:
Maximizing a subchart is impossible when Title Bar is set to "Off" in chart window properties.
Right click on the Chart is showing "Maximize subchart" option ... but it's unavailable (is always gray).
I also updated the list of keyboard shortcuts requesting a "maximize subchart" shortcut in this thread (item #31):
http://forum.tssupport.com/viewtopic.ph ... g+subchart
Please can someone from TS Support investigate the matter.
Thanks
--
Pavel
added later
The above problem is a direct consequence of another inconvenience/bug (which I am trying to avoid by disabling chart title bars) apparently very old issue:
http://forum.tssupport.com/viewtopic.php?t=3552
Please consider both of these issues together.
Regarding the first issue, we failed to reproduce the problem. As long as you have at least one subchart, the "Maximize subchart" option is available (not gray), regardless of your Title Bar settings. This option can be unavailable only if you do not have any subcharts, just the main chart in the window. Which is logical, because in that case there is no subchart to maximize.
As for the scaling issue, this behavior is normal. There are several solutions to avoid problems when you have lots of small charts on a workspace:
- Use Window menu to switch between charts.
- Make several workspaces with larger chart windows and use the Detach Window and Stick Window options.
- Set Title Bar as "Off"
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear TJlink color disappeared
It is a known bug which occurs in Windows Vista and higher. It is in our fix list and will be fixed soon.
Dear sptrader,Beta3 ONLY_ For the second day in a row on 2 different computers, continuous contracts won't update (ES with IB), they stop overnight.
Could you please precise if the data stops updating when IB unloads? If yes, what happens if you restart IB?
My FDAX working fine, here are my settings:MC Version 6.0 Beta 3 (Build 3276)
I am still getting zero ticks from zenfire happens on FDAX havent checked other instruments. Should have been fixed in beta 3...not for me
• Ticks with the zero price on historical data from Zen-Fire are not filtered out.



Mike
Thank you for your statemant!Connection with MBT:
On Sunday afternoon MBT-Login is not possible for some hours.
When you have open MC in this time with realtime-data and download-history => yes than MC trys to login in background to MBT without a stop.
But after some mismatched logins MBT locks the MBT-account.
Its very annoying Its the second weekend
Now I can't trade until I chatted mit MBT and unlock the account.
suggestion: MC could stop try login after 3 attemps!Dear Henrik and Bruce,That's a good point - hammering the server will cause your account to be locked for IB as well
I would suggest you to use Offline Data Server Mode on Sunday to avoid this problem. (File --> Preferences --> Data Server Mode)
But: with this solution I can't download historical datas (from MBT, from IB, from Barcharts...) and its not a solution for future...
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Henrik,Thank you for your statemant!
But: with this solution I can't download historical datas (from MBT, from IB, from Barcharts...) and its not a solution for future...
If you use the offline data server mode only on Sundays, you should not have any problems as the market is closed. You can use your historical data from the Quote Manager in the offline mode.
Regarding futures, could you please precise, why it is not a solution?
Thank you for read and think about it.Dear Henrik,Thank you for your statemant!
But: with this solution I can't download historical datas (from MBT, from IB, from Barcharts...) and its not a solution for future...
If you use the offline data server mode only on Sundays, you should not have any problems as the market is closed. You can use your historical data from the Quote Manager in the offline mode.
Regarding futures, could you please precise, why it is not a solution?
Its no solution because the User did not see directly if connection to MBT failed - and very fast you have a locked account.
And: maybe you want to activate Strategys on sunday morning or did not want to disable strategy from last week because open trades => both is not possible because hammering MBT on sunday.
Solution: Quotemanager/Preferences Broker MBT:
1.) reconnect after xxx seconds
2.) stop reconnect after xxx failed try's.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Nick,MC Version 6.0 Beta 3 (Build 3276)
I am still getting zero ticks from zenfire happens on FDAX havent checked other instruments. Should have been fixed in beta 3...not for me
• Ticks with the zero price on historical data from Zen-Fire are not filtered out.
If you had zero ticks before you installed beta 3, they won't be filtered. You should delete them manually. Only ticks that you download after installing beta 3 are filtered.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Henrik,Thank you for read and think about it.
Its no solution because the User did not see directly if connection to MBT failed - and very fast you have a locked account.
And: maybe you want to activate Strategys on sunday morning or did not want to disable strategy from last week because open trades => both is not possible because hammering MBT on sunday.
Solution: Quotemanager/Preferences Broker MBT:
1.) reconnect after xxx seconds
2.) stop reconnect after xxx failed try's.
You are welcome. I have forwarded your suggestions to the developers. We will consider this option.
I know from other software, they implemented a timed login.Dear Henrik,Thank you for read and think about it.
Its no solution because the User did not see directly if connection to MBT failed - and very fast you have a locked account.
And: maybe you want to activate Strategys on sunday morning or did not want to disable strategy from last week because open trades => both is not possible because hammering MBT on sunday.
Solution: Quotemanager/Preferences Broker MBT:
1.) reconnect after xxx seconds
2.) stop reconnect after xxx failed try's.
You are welcome. I have forwarded your suggestions to the developers. We will consider this option.
I can setup: sunday, 17:00 or when ever the market starts.
I trade against MB at the moment, and i start everythin on sunday.
But i use DDE for receiving tick data, but i can login on sunday.
The quote and order servers are not available, thats true, but login is successfull. When the market starts, quote and order server are up and i dont need to do anything.
i will try it this weekend with beta3, to see what the problem is.
Re: "maximize subchart"Dear Pavel,Discovered a problem that I don't know how to overcome. If there is something I don't know please help me to find a solution, otherwise it seems to me like a small bug.
The problem:
Maximizing a subchart is impossible when Title Bar is set to "Off" in chart window properties.
Right click on the Chart is showing "Maximize subchart" option ... but it's unavailable (is always gray).
I also updated the list of keyboard shortcuts requesting a "maximize subchart" shortcut in this thread (item #31):
http://forum.tssupport.com/viewtopic.ph ... g+subchart
Please can someone from TS Support investigate the matter.
Thanks
--
Pavel
added later
The above problem is a direct consequence of another inconvenience/bug (which I am trying to avoid by disabling chart title bars) apparently very old issue:
http://forum.tssupport.com/viewtopic.php?t=3552
Please consider both of these issues together.
Regarding the first issue, we failed to reproduce the problem. As long as you have at least one subchart, the "Maximize subchart" option is available (not gray), regardless of your Title Bar settings. This option can be unavailable only if you do not have any subcharts, just the main chart in the window. Which is logical, because in that case there is no subchart to maximize.
As for the scaling issue, this behavior is normal. There are several solutions to avoid problems when you have lots of small charts on a workspace:
- Use Window menu to switch between charts.
- Make several workspaces with larger chart windows and use the Detach Window and Stick Window options.
- Set Title Bar as "Off"
Dave, what I was looking for is to maximize the chart Window, but confused it with subchart. As I can see that there is no way whatsoever to maximize the chart window when Title Bar is set to "Off". Too bad.
Re: "Scaling Issue"
I am sorry, but the behavior is NOT normal. You missing the point why I'm turning off title bars - because current implementation causes many errors when clicking on relatively small size windows. When title bars turned off, a new problem arises which is inability to maximize the chart window. The suggestion to make windows larger and break them into different work spaces is not suitable for me. There is a reason why I need so many windows visible at a time. Your response tells me TS Support is stubborn to accept the fact that "Title Bar auto-hide" implementation is half-done. Sure, denying the problem is much easier than attempting to find a solution to a problem. I guess that TSS spent less time discussing the problem than I spent time truing to find more efficient ways to work around these problems and wasting time for extra clicks and repairing trend lines that were accidentally displaced as a result of what you call "normal" behavior. Then multiply the time wasted by single user by a number of users.
Basically the way I interpret your (TSS) response to the problem I reported is "shut up, no one else reported the problem. We are not going to question our opinion on what's normal. We have more important problems to work on".
Thanks TSS for ignoring and denying the problem.
Re shortcut keys:
1. Enable\disable automation (preferably different shortcut keys for each).
2. Buttons in dialogues when automation is exited. Simply underline a letter in the button text to denote the shortcut key as per normal Windows standards.
Thanks Dave, another position of mine was wrongly closed when IB exited for nightly maintenence tonight. Greater control over these options will be greatly appreciated.Dear bowlesj3 and brendanh,
We will give users the possibility to customize all commands in the next version of MultiCharts.
Dave Masalov
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
"Linked to All" does not work in some circumstance
Dear TS Support,
Frankly this request/bug report was long due, but I was reluctant to send it because way too many times the response I receive from TSS is like: "the behavior is normal". Please investigate the current algorithm behind the "Linked to All" feature. The details are provided below:
"Link to All" doesn't work in the following circumstances:
1. Suppose we have a workspace with 4 chart windows each displaying a different instrument. For example: AAPL, INTC, GOOG, and NVDA. Symbol linking is set to "Not linked" for all of the above charts.
2. Next we create the 5th window with symbol IBM and set symbol linking to "Link to All". The purpose of this 5th window is to display an intraday resolution of the symbol plotted with with in some other window in daily/weekly resolution.
Problem/question: How can I force the new chart window (with "linked to all" activated) to be actually linked to any other window?
Things I tried / Is it a reasonable solution ?
I tried the following:
Made the first (AAPL) window active by mouse click, then typed AAPL in the command line - nothing happens. If I type some other instrument, example: CSCO, then both the 1st and my new 5th window will update and plot CSCO chart. Only after that if I type in the command line AAPL again, the symbol in the 5th window will be updated to AAPL. This is inconvenient, and demand unnecessary wiggling with the mouse - way too much. Even assuming this is a bug, which need to be fixed the "Linked to All" can be greatly enhanced as described below:
Suggestions / Improvements:
It appears a common sense to have "Linked to All" window behave as following:
- Force linking of the 5th window if symbol typed in the command line (EVEN IF SYMBOL IS THE SAME)
- Very Important: Link to the Active Chart Window by default - ALL THE TIME. In other words just link to whatever window the mouse pointer is placed into (truck the active chart window). This will allow automatic chart linking when reviewing charts. For example in a workspace with many smaller size daily resolution charts, the chart with intraday resolution and will be linked to all. This will allow to take a quick look at intraday charts by selecting windows with daily resolutions. By implementing the above the use of "Linked to All" feature will become much more valuable, and will not be limited to a scanner.
--
Thank you for considering,
Pavel
Frankly this request/bug report was long due, but I was reluctant to send it because way too many times the response I receive from TSS is like: "the behavior is normal". Please investigate the current algorithm behind the "Linked to All" feature. The details are provided below:
"Link to All" doesn't work in the following circumstances:
1. Suppose we have a workspace with 4 chart windows each displaying a different instrument. For example: AAPL, INTC, GOOG, and NVDA. Symbol linking is set to "Not linked" for all of the above charts.
2. Next we create the 5th window with symbol IBM and set symbol linking to "Link to All". The purpose of this 5th window is to display an intraday resolution of the symbol plotted with with in some other window in daily/weekly resolution.
Problem/question: How can I force the new chart window (with "linked to all" activated) to be actually linked to any other window?
Things I tried / Is it a reasonable solution ?
I tried the following:
Made the first (AAPL) window active by mouse click, then typed AAPL in the command line - nothing happens. If I type some other instrument, example: CSCO, then both the 1st and my new 5th window will update and plot CSCO chart. Only after that if I type in the command line AAPL again, the symbol in the 5th window will be updated to AAPL. This is inconvenient, and demand unnecessary wiggling with the mouse - way too much. Even assuming this is a bug, which need to be fixed the "Linked to All" can be greatly enhanced as described below:
Suggestions / Improvements:
It appears a common sense to have "Linked to All" window behave as following:
- Force linking of the 5th window if symbol typed in the command line (EVEN IF SYMBOL IS THE SAME)
- Very Important: Link to the Active Chart Window by default - ALL THE TIME. In other words just link to whatever window the mouse pointer is placed into (truck the active chart window). This will allow automatic chart linking when reviewing charts. For example in a workspace with many smaller size daily resolution charts, the chart with intraday resolution and will be linked to all. This will allow to take a quick look at intraday charts by selecting windows with daily resolutions. By implementing the above the use of "Linked to All" feature will become much more valuable, and will not be limited to a scanner.
--
Thank you for considering,
Pavel
I was wondering why the live results do not match with the Performance Report...View - Performance Report I think is what you are looking for.Is there a way to see the live-performance (trades) of a strategy? I can't find such thing...?
It seems that the performance report is only a simple backtest in the time of enable-strategy.
Scalping in Backtests is impossible. I cant so analyse the trades if the performance report based ob backtest, not on real trades you see in the position tracker.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Pavel,Re: "Scaling Issue"
I am sorry, but the behavior is NOT normal. You missing the point why I'm turning off title bars - because current implementation causes many errors when clicking on relatively small size windows. When title bars turned off, a new problem arises which is inability to maximize the chart window. The suggestion to make windows larger and break them into different work spaces is not suitable for me. There is a reason why I need so many windows visible at a time. Your response tells me TS Support is stubborn to accept the fact that "Title Bar auto-hide" implementation is half-done. Sure, denying the problem is much easier than attempting to find a solution to a problem. I guess that TSS spent less time discussing the problem than I spent time truing to find more efficient ways to work around these problems and wasting time for extra clicks and repairing trend lines that were accidentally displaced as a result of what you call "normal" behavior. Then multiply the time wasted by single user by a number of users.
Basically the way I interpret your (TSS) response to the problem I reported is "shut up, no one else reported the problem. We are not going to question our opinion on what's normal. We have more important problems to work on".
Please do not exagerate things. We understand your point of view. And we do recognise there is a problem here. However it is not a five minutes fix and changing this behavior requires some very complex calculations to be done. It is not possible for the moment.
The "Link to All" feature depends on changes made to other charts. However, when you type the same symbol name in the command line, you do not actually change anything."Link to All" doesn't work in the following circumstances:
1. Suppose we have a workspace with 4 chart windows each displaying a different instrument. For example: AAPL, INTC, GOOG, and NVDA. Symbol linking is set to "Not linked" for all of the above charts.
2. Next we create the 5th window with symbol IBM and set symbol linking to "Link to All". The purpose of this 5th window is to display an intraday resolution of the symbol plotted with with in some other window in daily/weekly resolution.
Problem/question: How can I force the new chart window (with "linked to all" activated) to be actually linked to any other window?
We understand that it may cause inconveniences and plan to change this behavior in the future. We will consider your suggestions. Thank you.
Dear sptrader,** Thanks Dave !
You are welcome.
Dave, Thank you for support.Dear Pavel,
Please do not exagerate things. We understand your point of view. And we do recognise there is a problem here. However it is not a five minutes fix and changing this behavior requires some very complex calculations to be done. It is not possible for the moment.
...
The "Link to All" feature depends on changes made to other charts. However, when you type the same symbol name in the command line, you do not actually change anything.
We understand that it may cause inconveniences and plan to change this behavior in the future. We will consider your suggestions. Thank you.
I entirely understand the time constraints and rely on TS Support expertise to consider implementing suggested improvements when time and opportunity allows.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Holidays option help to filter incorrect data, if it is not done by a data provider.
In MC holidays are seen in the astronomical sense: when you plot a chart all data corresponding to the holiday's date (exchange timezone) is ignored.
It is done this way because holidays start and end at different time: there are differences in different holidays on the same exchange, same holidays on different exchanges (or from different data providers). There is no single system.
We plan to add the possibility to set start and end time for holidays in the future. This should solve the problem.
If you use IB, IQFeed or TS as a data provider, then to get ES futures data after holiday starting at 17-00, you can just turn the holidays option off. (for ex. set Holday List as 'None' in the exchange settings in the QM).
Could you please explain what do you mean by : "The solution is obviously deleting all holidays in QM, but this creates another problem when mixing overnight data with the regular session data since dates will not match."?
Please send a screenshot with some explanations.
In MC holidays are seen in the astronomical sense: when you plot a chart all data corresponding to the holiday's date (exchange timezone) is ignored.
It is done this way because holidays start and end at different time: there are differences in different holidays on the same exchange, same holidays on different exchanges (or from different data providers). There is no single system.
We plan to add the possibility to set start and end time for holidays in the future. This should solve the problem.
If you use IB, IQFeed or TS as a data provider, then to get ES futures data after holiday starting at 17-00, you can just turn the holidays option off. (for ex. set Holday List as 'None' in the exchange settings in the QM).
Could you please explain what do you mean by : "The solution is obviously deleting all holidays in QM, but this creates another problem when mixing overnight data with the regular session data since dates will not match."?
Please send a screenshot with some explanations.
Feature suggestion:
Please add "Seconds" to the "Bar magnifer" (see picture) for backtesting strategy.
Because recording Ticks (bid/ask/trade) from several instruments is a little bit unstable, but seconds are OK.
Please add "Seconds" to the "Bar magnifer" (see picture) for backtesting strategy.
Because recording Ticks (bid/ask/trade) from several instruments is a little bit unstable, but seconds are OK.
- Attachments
-
- secondadd.JPG
- (56.38 KiB) Downloaded 17751 times
Another Feature suggestion:
Add a new Field "Description" for paramaters.
For example in the code:
And now you can see the Description "Size of Posi" when you hold over the mousepointer when you format Signal>=Parameters.
OK, Posisize is a bad example, but I have sometimes very complex Parameters, and after some weeks I have to look in the code what I write as commentar (in power editor).
Add a new Field "Description" for paramaters.
For example in the code:
Code: Select all
Inputs:
PosiSize(1,"Size of Posi");
OK, Posisize is a bad example, but I have sometimes very complex Parameters, and after some weeks I have to look in the code what I write as commentar (in power editor).
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Hi Dave.

Where is the "None" option on the Holiday list?
When I said:
Holidays run between midnights.
So if today were an holiday in the states, ES futures would start the new day at 1700 EST as usual.
MC though, would not show this data since it would treat this day as an holiday. Only after midnight MC would start to retrieve ES data since the holiday would be officially over and a new day would began.
The problem would then be the lack of 7 hours of trading that MC woudn't show for that day on ES chart, because those 7 hours would be included on the holiday session, a session, that due to QM Holiday option, would not be shown on MC.
If I'm not mistaken, Dennis promised a on/off button for the Holiday option in a future MC version.
Regards,
Fernando
Apparently you have a QM version different from mine (MC 6 beta 3)(for ex. set Holday List as 'None' in the exchange settings in the QM).

Where is the "None" option on the Holiday list?
When I said:
It is because there is no other way to turn off the Holidays option.The solution is obviously deleting all holidays in QM
What I mean by this is what you said previously regarding the option that a MC future version will have:but this creates another problem when mixing overnight data with the regular session data since dates will not match.
Taking ES for an example, ES trades between 1530 and 1515 (next day) EST.We plan to add the possibility to set start and end time for holidays in the future.
Holidays run between midnights.
So if today were an holiday in the states, ES futures would start the new day at 1700 EST as usual.
MC though, would not show this data since it would treat this day as an holiday. Only after midnight MC would start to retrieve ES data since the holiday would be officially over and a new day would began.
The problem would then be the lack of 7 hours of trading that MC woudn't show for that day on ES chart, because those 7 hours would be included on the holiday session, a session, that due to QM Holiday option, would not be shown on MC.
If I'm not mistaken, Dennis promised a on/off button for the Holiday option in a future MC version.
Regards,
Fernando
Agree with Arnie on adding the On/Off Holiday button so it can be accessible from MC toolbar.
Another issue in MC Beta 3:
Two title Bar icons are not aligned with others. Noticed this immediately after customizing the appearance of windows (OS version: Windows 7). I changed the following: Title Bar width, Caption Buttons size, and border padding. The image is attached.
Thank you,
Pavel
Another issue in MC Beta 3:
Two title Bar icons are not aligned with others. Noticed this immediately after customizing the appearance of windows (OS version: Windows 7). I changed the following: Title Bar width, Caption Buttons size, and border padding. The image is attached.
Thank you,
Pavel
- Attachments
-
- Misalignment.PNG
- (2.22 KiB) Downloaded 17786 times
Suggestion:
Write own text in status-bar of a chart (or/and title bar).
Why?
I have several charts open with different funtions und indicators. Sometimes I have problems to find quickly the right chart because some charts are similar.
How?
At time you can change some things in the status line. But you can not write a text. maybe it can be implemented?
(Alternate: change titel of the title bar of a chart)
Thank you for think about it, TS team!
Write own text in status-bar of a chart (or/and title bar).
Why?
I have several charts open with different funtions und indicators. Sometimes I have problems to find quickly the right chart because some charts are similar.
How?
At time you can change some things in the status line. But you can not write a text. maybe it can be implemented?
(Alternate: change titel of the title bar of a chart)
Thank you for think about it, TS team!
BUG-Report (IntrabarOrder & Variables)
BUG-Report (IntrabarOrder & Variables):
Hi,
i have been working with Intra-Bar Order Generation and found a bug.
Settings: “Allow unlimited entries and exits per bar”
Code:
Line 111 is the end of the Code.
On a Intra-Bar Order Generation (tradingtime=true, FentryO=true, BentryO=true and not rlong)
it executes an long order position just as it should.
The variables “Trail” and “rlong” are receiving new values but only temporary. WHY?
They keep there new values until the end of the code. Starting the code over again they have there old values back but not the new ones.
This happens over and over again until the end of the Bar. If the entry is still valid the variables Trail and rlong keep there new values permanently.
BUT now this is the big fail... when the entry is not valid at the end of the bar the variables Trail and rlong have there old values back and not the new assigned ones BUT the MarketOrder is out.
The variables values should not change from last Line 111 to first Line 1 but it does
Log from the print Lines
Line 1 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 65 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 74 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 111 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 1 rlong: FALSE Marketposition: 0.00 date: 1100330.00 907.00
Line 65 rlong: FALSE Marketposition: 0.00 date: 1100330.00 907.00
Line 74 rlong: TRUE Marketposition: 0.00 date: 1100330.00 907.00
Line 111 rlong: TRUE Marketposition: 0.00 date: 1100330.00 907.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 908.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 908.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 908.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 908.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 910.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 910.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 910.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 910.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 911.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 911.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 911.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 911.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 912.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 912.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 912.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 912.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 913.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 913.00
[...]
Hi,
i have been working with Intra-Bar Order Generation and found a bug.
Settings: “Allow unlimited entries and exits per bar”
Code:
Code: Select all
print("Line 1 rlong: ",(rlong)," Marketposition: ",marketposition," date: ",date," ",time);
...
vars:
rlong(false),
rshort(false),
iBBO(0),
iBBU(0),
tradingtime(false),
BentryO(false),
BentryU(false),
FentryO(false),
FentryU(false),
RATR(0),
Trail(0);
...
print("Line 65 rlong: ",(rlong)," Marketposition: ",marketposition," date: ",date," ",time);
//Enter
if (tradingtime and FentryO and BentryO and not rlong) then
begin
buy next bar at market;
Trail=Close-RATR;
rlong=true;
end;
print("Line 74 rlong: ",(rlong)," Marketposition: ",marketposition," date: ",date," ",time);
…
print("Line 111 rlong: ",(rlong)," Marketposition: ",marketposition," date: ",date," ",time);
Line 111 is the end of the Code.
On a Intra-Bar Order Generation (tradingtime=true, FentryO=true, BentryO=true and not rlong)
it executes an long order position just as it should.
The variables “Trail” and “rlong” are receiving new values but only temporary. WHY?
They keep there new values until the end of the code. Starting the code over again they have there old values back but not the new ones.
This happens over and over again until the end of the Bar. If the entry is still valid the variables Trail and rlong keep there new values permanently.
BUT now this is the big fail... when the entry is not valid at the end of the bar the variables Trail and rlong have there old values back and not the new assigned ones BUT the MarketOrder is out.
The variables values should not change from last Line 111 to first Line 1 but it does
Log from the print Lines
Line 1 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 65 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 74 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 111 rlong: FALSE Marketposition: 0.00 date: 1100330.00 906.00
Line 1 rlong: FALSE Marketposition: 0.00 date: 1100330.00 907.00
Line 65 rlong: FALSE Marketposition: 0.00 date: 1100330.00 907.00
Line 74 rlong: TRUE Marketposition: 0.00 date: 1100330.00 907.00
Line 111 rlong: TRUE Marketposition: 0.00 date: 1100330.00 907.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 908.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 908.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 908.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 908.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 909.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 909.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 910.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 910.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 910.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 910.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 911.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 911.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 911.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 911.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 912.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 912.00
Line 74 rlong: TRUE Marketposition: 1.00 date: 1100330.00 912.00
Line 111 rlong: TRUE Marketposition: 1.00 date: 1100330.00 912.00
Line 1 rlong: FALSE Marketposition: 1.00 date: 1100330.00 913.00
Line 65 rlong: FALSE Marketposition: 1.00 date: 1100330.00 913.00
[...]
-
- Posts: 734
- Joined: 09 Apr 2010
- Location: Texas
- Has thanked: 483 times
- Been thanked: 273 times
- Contact:
MC (IB data) Continuous Contracts Bug ?
I just noticed that if I use continuous contracts and 50 days back(30 min chart), I get the ES June contract prices, However if I use 100 days back, I get the correct ES Sept contract prices- see attached.
Bug ??????
Bug ??????
- Attachments
-
- Continuous Contracts Problem.jpg
- (54.02 KiB) Downloaded 17745 times
BUG-Report (IntrabarOrder & Variables):
I think my last posting is hard to understand (BUG-Report (IntrabarOrder & Variables).
Here a summary:
Intrabarorder activated, bar magifer activatet.
MC did not save parameters in a variable, when intrabaroder activated.
Only at close of a bar, but only if the condition true.
Please fix this, because its a big bug!
Here a summary:
Intrabarorder activated, bar magifer activatet.
MC did not save parameters in a variable, when intrabaroder activated.
Only at close of a bar, but only if the condition true.
Please fix this, because its a big bug!
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Re: BUG-Report (IntrabarOrder & Variables):
I think my last posting is hard to understand (BUG-Report (IntrabarOrder & Variables).
Here a summary:
Intrabarorder activated, bar magifer activatet.
MC did not save parameters in a variable, when intrabaroder activated.
Only at close of a bar, but only if the condition true.
Please fix this, because its a big bug!
Please report this through the Feedback/Bug Report option on MC.

-
- Posts: 14
- Joined: 25 Aug 2007
Optimize failed
As attached JPGs, MC6 beta3 failed to optimize.
If I move the mouse to Optimization Criteria tab and click, error message prompts as in OptimizeFailed.JPG.
When I try to modify the startvalue and endvalue for optimization.
The program halted and then crashed. [OptimizeHalt.JPG]
問題事件名稱: APPCRASH
應用程式名稱: MultiCharts.exe
應用程式版本: 5.0.3276.203
應用程式時間戳記: 4bd6a1d1
錯誤模組名稱: StackHash_090c
錯誤模組版本: 6.1.7600.16385
錯誤模組時間戳記: 4a5bdadb
例外狀況代碼: c0000374
例外狀況位移: 000c283b
作業系統版本: 6.1.7600.2.0.0.256.48
地區設定識別碼: 1028
其他資訊 1: 090c
其他資訊 2: 090c8f54f4ba4e79e36bdaf67354c176
其他資訊 3: cbe7
其他資訊 4: cbe70d4dbcf21dbb3ff391945fbeef4c
[OS: WIndows 7 Traditional Chinese]
If I move the mouse to Optimization Criteria tab and click, error message prompts as in OptimizeFailed.JPG.
When I try to modify the startvalue and endvalue for optimization.
The program halted and then crashed. [OptimizeHalt.JPG]
問題事件名稱: APPCRASH
應用程式名稱: MultiCharts.exe
應用程式版本: 5.0.3276.203
應用程式時間戳記: 4bd6a1d1
錯誤模組名稱: StackHash_090c
錯誤模組版本: 6.1.7600.16385
錯誤模組時間戳記: 4a5bdadb
例外狀況代碼: c0000374
例外狀況位移: 000c283b
作業系統版本: 6.1.7600.2.0.0.256.48
地區設定識別碼: 1028
其他資訊 1: 090c
其他資訊 2: 090c8f54f4ba4e79e36bdaf67354c176
其他資訊 3: cbe7
其他資訊 4: cbe70d4dbcf21dbb3ff391945fbeef4c
[OS: WIndows 7 Traditional Chinese]
- Attachments
-
- OptimizeHalt.JPG
- (95.86 KiB) Downloaded 17739 times
-
- OptimizeFailed.JPG
- (49.44 KiB) Downloaded 17751 times
Re: Optimize failed
You should normally be able to change the optimizable inputs as per attached picture to arrive at number of simulations greater than 1.When I try to modify the startvalue and endvalue for optimization.
The program halted and then crashed.
I suggest to speak directly to TSS help desk and they can remotely diagnose the issue of MC's halting.
- Attachments
-
- Optimize non Failed.JPG
- (50.24 KiB) Downloaded 17739 times
Renko chart type display problem
Hello,
I'm using MC 6.0 beta 3.
The Renko display problem for longer timeframes (backtesting) seems still to exist:
For every instrument I chose the last couple of days are displayed correctly (appro. 7-10 days), but going back more to the past the chart is empty - no bars shown at all.
This was already mentioned in an earlier post (March) and commented as "will be fixed", but in beta 3 the problem still exists:
http://forum.tssupport.com/viewtopic.ph ... torder=asc
If I adjust the selected timeframe, e.g. by shifting the displayed chart data 3 month backwards or so, again the last 7-10 days are shown, the rest is not displayed.
This is reproducable for all instruments and all data sources (ASCII or Zen), thus corrupted tick data can be excluded.
The same happens with 3LB chart type, thus it seems to be a bug for all non-time-based chart types?
Kind regards from Germany
aknip
I'm using MC 6.0 beta 3.
The Renko display problem for longer timeframes (backtesting) seems still to exist:
For every instrument I chose the last couple of days are displayed correctly (appro. 7-10 days), but going back more to the past the chart is empty - no bars shown at all.
This was already mentioned in an earlier post (March) and commented as "will be fixed", but in beta 3 the problem still exists:
http://forum.tssupport.com/viewtopic.ph ... torder=asc
If I adjust the selected timeframe, e.g. by shifting the displayed chart data 3 month backwards or so, again the last 7-10 days are shown, the rest is not displayed.
This is reproducable for all instruments and all data sources (ASCII or Zen), thus corrupted tick data can be excluded.
The same happens with 3LB chart type, thus it seems to be a bug for all non-time-based chart types?
Kind regards from Germany
aknip
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Henrik,Another Feature suggestion:
Add a new Field "Description" for paramaters.
We will implement this feature in the future.
Dear Fernando,Apparently you have a QM version different from mine (MC 6 beta 3)
Where is the "None" option on the Holiday list?
The "None" option is situated in QM --> Tools --> Exchanges & ECNs --> Edit --> Holiday List
If I'm not mistaken, Dennis promised a on/off button for the Holiday option in a future MC version.
Dear Sirs,Agree with Arnie on adding the On/Off Holiday button so it can be accessible from MC toolbar.
This feature will be implemented in the future versions of MultiCharts.
Dear Pavel,Another issue in MC Beta 3:
Two title Bar icons are not aligned with others. Noticed this immediately after customizing the appearance of windows (OS version: Windows 7). I changed the following: Title Bar width, Caption Buttons size, and border padding. The image is attached.
This problem should disappear after restarting MultiCharts.
Dear Henrik,Suggestion:
Write own text in status-bar of a chart (or/and title bar).
We will consider your suggestions in the future development.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
When I try to modify the startvalue and endvalue for optimization.
The program halted and then crashed. [OptimizeHalt.JPG]
The Renko display problem for longer timeframes (backtesting) seems still to exist:
For every instrument I chose the last couple of days are displayed correctly (appro. 7-10 days), but going back more to the past the chart is empty - no bars shown at all.
Dear Sirs,
This bugs should be fixed in the beta 4 version of MultiCharts 6.0
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Henrik,Hi,
i have been working with Intra-Bar Order Generation and found a bug.
Settings: “Allow unlimited entries and exits per bar”
Please try to use the IntraBarPersist keyword.
It is used in variable and array declaration statements, before a variable or array name, to specify that the value of the variable or array elements are to be updated on every tick.
If IntraBarPersist is not specified, the value will be updated at the close of each bar.
Usage
Declaration:[IntraBarPersist]Name(InitialValue1)
Please read the Help file for more information.
Actually, according to my research the problem you mention Bob is one if missing ticks. I found the post with a revised subject name.
http://forum.tssupport.com/viewtopic.ph ... sing+ticks
If ticks are missing it will mess up your volume info for sure (kind of obvious). The big question then becomes, "If MC is made so it processes every tick in every study and the user has a lot of studies, can it get all these done before the next tick arrives from the exchange?". More importantly, "if it can not keep up how will the user get assistance such that they can decide if they should 1/ get a faster machine or 2/ eliminate some studies or 3/ make changes to select studies to reduce processing and speed them up and how will they know if it worked.".
Intrabarpersist is confusing but I am pretty sure it works as it is suppose to. I have a post that explains it.
http://forum.tssupport.com/viewtopic.php?t=6871
the help explains it only partially.
It just occured to me that is a very good way to explain intrabarpersist using code that represents what MC is doing. I will add a post to the above thread right now.
http://forum.tssupport.com/viewtopic.ph ... sing+ticks
If ticks are missing it will mess up your volume info for sure (kind of obvious). The big question then becomes, "If MC is made so it processes every tick in every study and the user has a lot of studies, can it get all these done before the next tick arrives from the exchange?". More importantly, "if it can not keep up how will the user get assistance such that they can decide if they should 1/ get a faster machine or 2/ eliminate some studies or 3/ make changes to select studies to reduce processing and speed them up and how will they know if it worked.".
Intrabarpersist is confusing but I am pretty sure it works as it is suppose to. I have a post that explains it.
http://forum.tssupport.com/viewtopic.php?t=6871
the help explains it only partially.
It just occured to me that is a very good way to explain intrabarpersist using code that represents what MC is doing. I will add a post to the above thread right now.
- RobotMan
- Posts: 375
- Joined: 12 Jul 2006
- Location: Los Altos, California, USA
- Has thanked: 31 times
- Been thanked: 13 times
- Contact:
Hi John,
You have done more research than anyone else on the forum concerning this issue and I trust your conclusions. I don't know what the problem is. I only know what the results are; unreliable volume counts intrabar in any indicator research I try to do even though the charts themselves update reliably and all the volume is there in each bar on the chart.
I think I remember SUPER doing some tests in TS and IBP works fine. Andrew addressed the issue as TS is single threaded and MC is multiThreaded.
http://forum.tssupport.com/viewtopic.php?p=29535#29535
so that's why I said what I did.
You have done more research than anyone else on the forum concerning this issue and I trust your conclusions. I don't know what the problem is. I only know what the results are; unreliable volume counts intrabar in any indicator research I try to do even though the charts themselves update reliably and all the volume is there in each bar on the chart.
I think I remember SUPER doing some tests in TS and IBP works fine. Andrew addressed the issue as TS is single threaded and MC is multiThreaded.
http://forum.tssupport.com/viewtopic.php?p=29535#29535
so that's why I said what I did.
Hi Bob,
I can explain what is happening to cause your volume bars to be giving the incorrect readings,
Price on a bar is fine because the high tick comes through and the low tick comes through and the open tick and the close tick too.
Volime bars exists because some of the ticks have come through and each of those ticks provide part of the volume for the volume bar.
However if even one tick is missing for the bar then the total volume for that bar will be incorrect (the volume bar will not be high enought or tall enough).
John.
P.S.
Now this is interesting. If MC it faced with situations where ticks come in just way to fast no matter how fast our computer is (and as a result of having too many studies that we feel are critical) and if we are traders like myself that do not use volume at all (YET at least), then if MC was smart enough to bypass ticks that do not provide a high/low/open/close, them maybe skipping ticks is a good sneaky way to get around the high volume fast market problem (but only during those times and under total control of the trader and fully reported to them too). For me, when markets start to show 10 second bars that are longer than my stop loss setting I stay out until things settle down a bit. If MC could report better in this area I would know if MC is having trouble before such long bar extremes. It would be very useful if MC could report and control in this area,
MC could easily know to skip executing studies for ticks that are not high/low/open/close. Very easy code involved (however like I say, it must be an option the trader must decide to switch on if MC reports it is having trouble keeping up with the high rate of tick arrival).
So an interesting question for you Bob is this. "have you never found an open/high/low/close that was incorrect?". I think the only way to research this properly would be to feed the same data into MC and TS then compare them (maybe super could modify my script to do this since I do not have time at the moment). IF MC and TS are the same here then the question becomes, "Is MC currently smart enough to properly skip ticks that are not open/high/low/close, but unwisely doing this without notifying the trader?"
It should be interesting how this all pans out when MC6.? is complete. I am not surprised that MC 6.? is taking a while to finalize. This is a big issue to say the least.
I can explain what is happening to cause your volume bars to be giving the incorrect readings,
Price on a bar is fine because the high tick comes through and the low tick comes through and the open tick and the close tick too.
Volime bars exists because some of the ticks have come through and each of those ticks provide part of the volume for the volume bar.
However if even one tick is missing for the bar then the total volume for that bar will be incorrect (the volume bar will not be high enought or tall enough).
John.
P.S.
Now this is interesting. If MC it faced with situations where ticks come in just way to fast no matter how fast our computer is (and as a result of having too many studies that we feel are critical) and if we are traders like myself that do not use volume at all (YET at least), then if MC was smart enough to bypass ticks that do not provide a high/low/open/close, them maybe skipping ticks is a good sneaky way to get around the high volume fast market problem (but only during those times and under total control of the trader and fully reported to them too). For me, when markets start to show 10 second bars that are longer than my stop loss setting I stay out until things settle down a bit. If MC could report better in this area I would know if MC is having trouble before such long bar extremes. It would be very useful if MC could report and control in this area,
MC could easily know to skip executing studies for ticks that are not high/low/open/close. Very easy code involved (however like I say, it must be an option the trader must decide to switch on if MC reports it is having trouble keeping up with the high rate of tick arrival).
So an interesting question for you Bob is this. "have you never found an open/high/low/close that was incorrect?". I think the only way to research this properly would be to feed the same data into MC and TS then compare them (maybe super could modify my script to do this since I do not have time at the moment). IF MC and TS are the same here then the question becomes, "Is MC currently smart enough to properly skip ticks that are not open/high/low/close, but unwisely doing this without notifying the trader?"
It should be interesting how this all pans out when MC6.? is complete. I am not surprised that MC 6.? is taking a while to finalize. This is a big issue to say the least.
- RobotMan
- Posts: 375
- Joined: 12 Jul 2006
- Location: Los Altos, California, USA
- Has thanked: 31 times
- Been thanked: 13 times
- Contact:
Hi John,
Maybe I do not understand. In my testing I see each bar receiving ALL the data. However, that same data is missing from being represented in an indicator that uses IntraBarPersist.
Ie: I can set up a volume bar chart and in subgraph 2 each histogram of "Ticks" shows a full bar of volume. If I run an indicator that counts volume using IBP in subgraph 3 at the same time, it does not see all the volume.
If I run a second or third IDENTICAL chart window at the same time, I get different results in subgraph 3 using the exact same data.
So my conclusion is that, internally MC sees *all* the upticks and downticks volume, but the indicators using IBP are unable to calculate them consistently. Hopefully this will all be moot shortly.
Maybe I do not understand. In my testing I see each bar receiving ALL the data. However, that same data is missing from being represented in an indicator that uses IntraBarPersist.
Ie: I can set up a volume bar chart and in subgraph 2 each histogram of "Ticks" shows a full bar of volume. If I run an indicator that counts volume using IBP in subgraph 3 at the same time, it does not see all the volume.
If I run a second or third IDENTICAL chart window at the same time, I get different results in subgraph 3 using the exact same data.
So my conclusion is that, internally MC sees *all* the upticks and downticks volume, but the indicators using IBP are unable to calculate them consistently. Hopefully this will all be moot shortly.
Hi Bob,
I went over your response a few times and I am pretty sure it is the missing ticks problem now that I remember the research.
The reserve word ticks is reproting correctly (meaning that by the end of the bar when "barstatus = 2" this reserve word has the correct number). What happens is there are times when the study is not executed for every tick coming in and yes you should be using intrabarpersist for your own totalling you set up and yes it is working properly but if your study is not executed even one time for a tick in the mid bar point your total will be lower. So that explains why your independant count is lower. Let me show an example. Lets say there are 10 ticks in this bar. I represent each tick below.
So if the study does not get executed for tick #4 then your count can not be correct. Your count would be even worse if you removed intrabarpersist. You must have it in there to be correct. But in addition to this the study has to have been executed on tick #4 in order for your total to be correct. But executions of the study are getting missed for ticks that are coming in. Maybe my terminology needs to be changed to "Missing study executions (for specific ticks that exist according to the ticks reserve word)". In other words is it not the ticks that are missing but rather the study executions that are missing. I guess that is my fault. Glad you brought the issue up again.
So your statement "the data is there" is correct (tick #4 is there), but it is in fact not getting prcessed by the study because the study is not getting executed for tick #4 (and there is on magical way for your count to get incremented if that study is not executed).
I went over your response a few times and I am pretty sure it is the missing ticks problem now that I remember the research.
The reserve word ticks is reproting correctly (meaning that by the end of the bar when "barstatus = 2" this reserve word has the correct number). What happens is there are times when the study is not executed for every tick coming in and yes you should be using intrabarpersist for your own totalling you set up and yes it is working properly but if your study is not executed even one time for a tick in the mid bar point your total will be lower. So that explains why your independant count is lower. Let me show an example. Lets say there are 10 ticks in this bar. I represent each tick below.
Code: Select all
ticks your count
1 1
2 2
3 3
(notice the gap)
5 4
6 5
7 6
8 7
9 8
10 9
So your statement "the data is there" is correct (tick #4 is there), but it is in fact not getting prcessed by the study because the study is not getting executed for tick #4 (and there is on magical way for your count to get incremented if that study is not executed).
- RobotMan
- Posts: 375
- Joined: 12 Jul 2006
- Location: Los Altos, California, USA
- Has thanked: 31 times
- Been thanked: 13 times
- Contact:
Hi John,
I was just about to return your PM, but then I noticed this post and thought it would be better to reply here.
Here is the post (including my PL code) where I actually did several instances of the same indicator in the same chart and should have gotten the same results.
http://forum.tssupport.com/viewtopic.php?p=29388#29388
As I read over your post, I believe we are talking about the same thing only from different angles.
Single threading: It's like a catcher on home plate trying to catch a single ball thrown by the pitcher.
Multi threading: It's like a catcher on home plate trying to catch balls thrown by all the infielders.
Intrabarpersist drops a few balls. Am I close?
I am thinking that Andrew needs to tell his code to only use single threading through 1 CPU for an indicator whenever IBP is involved because using wait states or using a buffer probably won't work. (disclosure: I am not a programmer and Andrew is probably shaking his head at the last statement.)
---------------------
I looked up the post from an old thread where we were talking about IBP and I think it might be better to continue the conversation there for posterity's sake.
I was just about to return your PM, but then I noticed this post and thought it would be better to reply here.
Here is the post (including my PL code) where I actually did several instances of the same indicator in the same chart and should have gotten the same results.
http://forum.tssupport.com/viewtopic.php?p=29388#29388
As I read over your post, I believe we are talking about the same thing only from different angles.
Single threading: It's like a catcher on home plate trying to catch a single ball thrown by the pitcher.
Multi threading: It's like a catcher on home plate trying to catch balls thrown by all the infielders.
Intrabarpersist drops a few balls. Am I close?
I am thinking that Andrew needs to tell his code to only use single threading through 1 CPU for an indicator whenever IBP is involved because using wait states or using a buffer probably won't work. (disclosure: I am not a programmer and Andrew is probably shaking his head at the last statement.)
---------------------
I looked up the post from an old thread where we were talking about IBP and I think it might be better to continue the conversation there for posterity's sake.
Hi Bob, I think the thread above on IntraBarPersist (the one I created
http://forum.tssupport.com/viewtopic.php?t=6871
) would be good to continue it. The last post of that thread has the intrabarpersist logic which I derived from all my tests on intrabarpersist. I will also review your code and see if I can figure out how the intrabarpersist logic might effect it. I will get back to this topic tonight after trading.
http://forum.tssupport.com/viewtopic.php?t=6871
) would be good to continue it. The last post of that thread has the intrabarpersist logic which I derived from all my tests on intrabarpersist. I will also review your code and see if I can figure out how the intrabarpersist logic might effect it. I will get back to this topic tonight after trading.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear sptrader,I just noticed that if I use continuous contracts and 50 days back(30 min chart), I get the ES June contract prices, However if I use 100 days back, I get the correct ES Sept contract prices- see attached.
Bug ??????
We could not analyze the situation, because there is no Custom Futures formula on the screenshot (it is in the Descripion),
However, such situation is possible, if you made one or both of following actions at the time between creating 50 daysback and 100 daysback charts:
- changing the formula in the Custom Futures settings, i.e. 12VOC to 11VOC,
- adding symbols which participate in the CF chart plotting, i.e future U0 was added before plotting the second chart.
Did you do anything like that?
Are you able to reproduce the problem, if you do not change CF settings at the time between plotting two charts as well as do not add/delete symbols from database?
Please try to do Reload for this window - does the problem disappear?
If you are able to reproduce the problem, please come to our Live Chat so we can connect to your PC remotely and analyze it.
You can also give us the CF formula (SymbolCode from Edit Custom Futures dialogue) and tell what ES futures do you have in your QuoteManager database.
Dear Henrik,Feature suggestion:
Please add "Seconds" to the "Bar magnifer" (see picture) for backtesting strategy.
Because recording Ticks (bid/ask/trade) from several instruments is a little bit unstable, but seconds are OK.
Could you please precise why recording ticks is unstable?
Open too much charts to record tickdata from (for example) all FX-pairs - after a few days MC chrashed.
I think because of the 32Bit-Limitation.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Dear Henrik,
Recording ticks with "Skip ticks with identical prices" option enabled is very similar to collecting seconds, because the majority of ticks within a second are with identical prices. Only ticks with different prices are saved in the database.
Could you please describe your crash problem in details?
If you are able to reproduce the crash problem, please come to our Live Chat so we can connect to your PC remotely and analyze the problem.
Recording ticks with "Skip ticks with identical prices" option enabled is very similar to collecting seconds, because the majority of ticks within a second are with identical prices. Only ticks with different prices are saved in the database.
Could you please describe your crash problem in details?
If you are able to reproduce the crash problem, please come to our Live Chat so we can connect to your PC remotely and analyze the problem.
Thank you, Dave.
Could you please describe your crash problem in details?
If you are able to reproduce the crash problem, please come to our Live Chat so we can connect to your PC remotely and analyze the problem.
Now I use only Quotemanager to record Ticks and not MC with open charts.
Now I have no more crashes.
Dave,Dear Pavel,Another issue in MC Beta 3:
Two title Bar icons are not aligned with others. Noticed this immediately after customizing the appearance of windows (OS version: Windows 7). I changed the following: Title Bar width, Caption Buttons size, and border padding. The image is attached.
This problem should disappear after restarting MultiCharts.
Thank you for response.
Restarting MultiCharts (as well as OS Windows) has no effect - buttons remain misaligned.
Another screen shot is attached for convenience.
This is a non-issue, however. Just a cosmetic effect.
--
Pavel
- Attachments
-
- Icons are not aligned.PNG
- (2.42 KiB) Downloaded 17761 times
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Regarding that old issue “Studies not getting executed on every tick.” I wrote a new script which is attached to both 1/ retest this problem and 2/ prove that intrabarpersist does work.
Regarding #2 it has proven that there is in fact no problem with “intrabarpersist”. This was done by creating a Global variable execution count as backup to the main IntraBarPersist execution count and testing to be sure that they never go out of line.
Regarding #1 it appears that MC 6.0 beta 2 is running much better than MC was performing before. However if you run the attached script on the 1-minute bars (and you run it for 10 or so minutes) it does produce the message
“The previous tick did not cause execution.”. Meaning the two execution counts in the study have fallen behind the ticks count. You get a chimes.wav sound to let you know. Note: if you do too many fileappend writes fileappend will eventually abort. This is why I put a maximum input parameter into the script. This will abort the script if you get more than the maximum number of these. Anyone running this may want to set this maximum very high and just let the file append abort. I also included this maximum because there is no point in running the script all day. Also, I have noticed that at times MC will run a long time without creating this error. Much better.
Also it seems that MC is consistently executing the study twice for the first tick of the bar and the last tick of the bar (it never did this conistently in the past). This occurs when the message “Dup tick count” is written to the file. There is no alert for this since it would drive the trader crazy. I am curious why TSS would have MC doing this.
For anyone new to this issue I do not recommend going back to the old threads on this issue below. However for anyone who was involved before these may be of useful reference.
Bobs thread that started the investigation.
http://forum.tssupport.com/viewtopic.php?t=6307&start=0
The last thread I created.
http://forum.tssupport.com/viewtopic.ph ... =duplicate
Again the new test script is below. It is much simpler than the big one I created for comparing with TS (which super was using).
Regarding #2 it has proven that there is in fact no problem with “intrabarpersist”. This was done by creating a Global variable execution count as backup to the main IntraBarPersist execution count and testing to be sure that they never go out of line.
Regarding #1 it appears that MC 6.0 beta 2 is running much better than MC was performing before. However if you run the attached script on the 1-minute bars (and you run it for 10 or so minutes) it does produce the message
“The previous tick did not cause execution.”. Meaning the two execution counts in the study have fallen behind the ticks count. You get a chimes.wav sound to let you know. Note: if you do too many fileappend writes fileappend will eventually abort. This is why I put a maximum input parameter into the script. This will abort the script if you get more than the maximum number of these. Anyone running this may want to set this maximum very high and just let the file append abort. I also included this maximum because there is no point in running the script all day. Also, I have noticed that at times MC will run a long time without creating this error. Much better.
Also it seems that MC is consistently executing the study twice for the first tick of the bar and the last tick of the bar (it never did this conistently in the past). This occurs when the message “Dup tick count” is written to the file. There is no alert for this since it would drive the trader crazy. I am curious why TSS would have MC doing this.
For anyone new to this issue I do not recommend going back to the old threads on this issue below. However for anyone who was involved before these may be of useful reference.
Bobs thread that started the investigation.
http://forum.tssupport.com/viewtopic.php?t=6307&start=0
The last thread I created.
http://forum.tssupport.com/viewtopic.ph ... =duplicate
Again the new test script is below. It is much simpler than the big one I created for comparing with TS (which super was using).
- Attachments
-
- A_TestTicks_SimpleWithGVCntAsWell.zip
- (4.39 KiB) Downloaded 701 times
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times
Regarding that old issue “Studies not getting executed on every tick.”
Dear bowlesj3,Also it seems that MC is consistently executing the study twice for the first tick of the bar
Thank you for testing these problems. These are known issues which will certainly be fixed. However, this will take a considerable amount of time as profound changes in the program architechture are required.
Hi Dave,
Yes, I am not surprised actually. However it seems as though it is a lot better now than the last time I did these tests (at least when it comes to missing an execution of the study when a tick comes in).
Thanks,
John
P.S. We have to thank Bob for his persistance. Had he not have kept complaining (and had he not have created that first script I used as a base), I never would have thought to test this. I am not sure why I decided to test the ticks output against his count. Natural programmers curiosity I think.
Yes, I am not surprised actually. However it seems as though it is a lot better now than the last time I did these tests (at least when it comes to missing an execution of the study when a tick comes in).
Thanks,
John
P.S. We have to thank Bob for his persistance. Had he not have kept complaining (and had he not have created that first script I used as a base), I never would have thought to test this. I am not sure why I decided to test the ticks output against his count. Natural programmers curiosity I think.
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Hi guys.
I know that beta 4 was just released, and I'm installing it at this very moment, but I've just receive this error when I closed beta 3.
Just want to know if this is an known issue.
Thanks,
Fernando
I know that beta 4 was just released, and I'm installing it at this very moment, but I've just receive this error when I closed beta 3.
Just want to know if this is an known issue.
Thanks,
Fernando
- Attachments
-
- MC_error.JPG
- (38.29 KiB) Downloaded 17754 times
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 487 times