**John: I was trying it out with 5 min and 30 min bars together.Hi Steven,
Is your lowest resolution chart at least 1 minute bars (or greater) and do your final trigger signals come from this chart (or at least primarily from this chart). If you are not using a resolution below 1 minute then global mode is fine for you.
John.
MC6 Beta 1 Feedback
-
- Posts: 407
- Joined: 01 Jan 2008
- Been thanked: 3 times
Regarding this problem I reported on the first page,
1 update every 10 seconds
1 update every 9 seconds
1 update every 8 seconds
1 update every 7 seconds
1 update every 5 seconds
1 update every 1 second (should be 4 seconds)
1 update every 1 second (should be 3 seconds)
1 update every 1 second (should be 2 seconds)
1 update every 1 second
1 update every 1 second (duplicated the one above it)
2 updates every 1 second
2 updates every 1 second
3 updates every 1 second
5 updates every 1 second
10 updates every 1 second
11 updates every 1 second
10 updates every 1 second
11 updates every 1 second
12 updates every 1 second
14 updates every 1 second
16 updates every 1 second
20 updates every 1 second
25 updates every 1 second
33 updates every 1 second
50 updates every 1 second
100 updates every 1 second
The very quick jump up to very high speeds is really good for moving quickly to another practice point in the future. I have started to do this by sliding the contol right to the far right, watching the prices move quickly buy then pulling the slider very quickly back to the far left to stop it. At that point I use the jump button to move back to the exact start point and then if it existed I would use the button for a traders favorite speed.
As far as the useful speeds that are missing shown again below along with the "1 update every 1 second" which is also a good speed to work with,
1 update every 1 second (should be 4 seconds)
1 update every 1 second (should be 3 seconds)
1 update every 1 second (should be 2 seconds)
1 update every 1 second
I am finding 1 update every 1 second at times is just a touch too fast and if a favorite speed button was put on I might set it at "1 update every 1 second" then click the "-" button to back it off to one of the slightly slower useful speeds above. For a difficult trade I might back it off 2 speeds and for easier trades maybe only back it off one speed.
The interesting gaps in the higher speeds makes me curious how these speeds came about. If they were just randomly chosen then maybe some traders would want to fine tune the gaps and request a way to do that. For me including the missing ones is probably all I would ever request.
I layed out the exact slider control speeds I am getting when the "SpeedControlChart" as I call it is set to 10 second bars.However I noticed in the replay that the "1 update every 2 secs, 3seconds and 4seconds" is missing. It jumps directly from 1 update every 1 second to one update every 5 seconds yet there are snap positions for these other speeds.
1 update every 10 seconds
1 update every 9 seconds
1 update every 8 seconds
1 update every 7 seconds
1 update every 5 seconds
1 update every 1 second (should be 4 seconds)
1 update every 1 second (should be 3 seconds)
1 update every 1 second (should be 2 seconds)
1 update every 1 second
1 update every 1 second (duplicated the one above it)
2 updates every 1 second
2 updates every 1 second
3 updates every 1 second
5 updates every 1 second
10 updates every 1 second
11 updates every 1 second
10 updates every 1 second
11 updates every 1 second
12 updates every 1 second
14 updates every 1 second
16 updates every 1 second
20 updates every 1 second
25 updates every 1 second
33 updates every 1 second
50 updates every 1 second
100 updates every 1 second
The very quick jump up to very high speeds is really good for moving quickly to another practice point in the future. I have started to do this by sliding the contol right to the far right, watching the prices move quickly buy then pulling the slider very quickly back to the far left to stop it. At that point I use the jump button to move back to the exact start point and then if it existed I would use the button for a traders favorite speed.
As far as the useful speeds that are missing shown again below along with the "1 update every 1 second" which is also a good speed to work with,
1 update every 1 second (should be 4 seconds)
1 update every 1 second (should be 3 seconds)
1 update every 1 second (should be 2 seconds)
1 update every 1 second
I am finding 1 update every 1 second at times is just a touch too fast and if a favorite speed button was put on I might set it at "1 update every 1 second" then click the "-" button to back it off to one of the slightly slower useful speeds above. For a difficult trade I might back it off 2 speeds and for easier trades maybe only back it off one speed.
The interesting gaps in the higher speeds makes me curious how these speeds came about. If they were just randomly chosen then maybe some traders would want to fine tune the gaps and request a way to do that. For me including the missing ones is probably all I would ever request.
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
MC 6.0 plotting different data than MC 5.5
Hi.
Apparently MC 6.0 is not handling data as MC 5.5.
I used the same database in both MC versions. I copied TSSTORAGE.GDB into my laptop and compared the ES charts.
Please see images attached.
In them I focused on a especific day (26-11-2009, an holiday), but this type of issue is happening all over the database (from 11-12-2007 til today).
Basically, MC 6.0 is not plotting November 26. It jumps from 23:59, November 25 to 12:04, November 27.
As we can see in the images presented, MC 5.5 is plotting November 26.
How can the same database plot different results?
Why MC 6.0 not plotting the holidays? At least November 26 is an holiday. All the other days where this is happening, I didn't confirm if all are holidays.
Apparently MC 6.0 is not handling data as MC 5.5.
I used the same database in both MC versions. I copied TSSTORAGE.GDB into my laptop and compared the ES charts.
Please see images attached.
In them I focused on a especific day (26-11-2009, an holiday), but this type of issue is happening all over the database (from 11-12-2007 til today).
Basically, MC 6.0 is not plotting November 26. It jumps from 23:59, November 25 to 12:04, November 27.
As we can see in the images presented, MC 5.5 is plotting November 26.
How can the same database plot different results?
Why MC 6.0 not plotting the holidays? At least November 26 is an holiday. All the other days where this is happening, I didn't confirm if all are holidays.
- Attachments
-
- ES_MC5.5_26-11-2009.png
- (46.38 KiB) Downloaded 4185 times
-
- ES_MC6.0_26-11-2009.png
- (80.67 KiB) Downloaded 4177 times
- TJ
- Posts: 7740
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1033 times
- Been thanked: 2221 times
Re: MC 6.0 plotting different data than MC 5.5
Hi.
Apparently MC 6.0 is not handling data as MC 5.5.
....
That's a continuous contract.
Are you using the same rollover rules for both charts?
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Re: MC 6.0 plotting different data than MC 5.5
Yes.That's a continuous contract.
Are you using the same rollover rules for both charts?
I'm using the continuos IQFeed ticker (@ES#).
QM setting are also equal in both MC version.
I check this year, and this is always happening on holidays.
Is there a on/off switch to this?
I can't find it.
Please don't tell me that I need to delete the dates from the Holidays menu in QM. It would be quite awkward.
-
- Posts: 82
- Joined: 20 Jun 2009
- Been thanked: 1 time
Renko charts not going back far enough in history
Yes.Anyone else have a problem with Renko charts not going back far enough in history?
I am using esignal. For PF, Renko and Kagi charts it seems to get only 14 days of data.
LB looks fine.