I have exactly the same problem and it is certainly not related to times of high market activity. The problem appeared only recently, can be seen after hours, is IQfeed-specific as it does not occur when I use a different data feed and manifests only at one of two trading computers with the same ver...

When will the list of improvements be posted for the latest release (8.8.8963.400)? There is nothing about this release on the page the "list of improvements" link in MC updater points to.

I see incorrect crosshair cursor tracking on workspaces with multiple windows in them. The horizontal line shows different price levels in different windows of the same instrument. The problem is seen across instruments (CL, ES, GC, 6E, 6J), on tick and minute charts and with two different data prov...

@arnie: I haven't used range bars the way you do to spot 1 tick gaps, but I see your point. Just to reiterate my main point, I have nothing against the current range bars in MC, just asked to add no-gap range bars (basically, an MC adaptation of RangeNoGap bars available for other trading platform) ...

Henry, Thank you for your response and for the description of MC point bar logic. Are you aware that the original bars do not seem to stay within the designated fixed rage when plotted? Please see the attached image showing an 8 point(original) candle chart with individual bar ranges (H-L) plotted a...

"The same goes for making the open equal to the previous close in a range bar. This simply is NOT how the market will happen in real trading" What exactly do you mean by this? Market can and does trade the same price more than once. Happens all the time. Therefore, closing the current bar at the fir...

These are pretty strong statements. How exactly does the use of no-gap range bars produce fake data and failed backtests? Could you elaborate? Quite a few traders out there, including myself, are finding correctly constructed no-gap range bars necessary for successful use of their trading methods. T...

No-gap range bars are well known and implemented in the other competitive platforms. In brief, they are constructed such that each bar closes and the next one starts when the old one has met the designated range. The range bars currently implemented in MC are constructed such that each bar closes an...

Could you please implement no-gap range bars as a standard bar type in Multicharts? I know this had been brought up before and the response from Multicharts was in the form of a recommendation to use the command line and enter "X point(original)" there to create the old version of range bars the MC ...

Still no progress with Transact?

So, your previously stated end of the year ETA is withdrawn... This is quite disappointing.

So, how much longer before we see 64 bit MC?

Stan, I have seen the advertisement and spoke with Transact after it appeared on their web site. Whatever your impressions may be regarding the status of Transact data feed availability, I as an interested customer received the response mentioned in my previous post. The bottomline is both parties (...

I called Transact abut this and basically got blown off in a fairly polite way. The message was: We don't really know if it works, so please talk to your broker at Infinity. Maybe he will know if this is really available for you to use. It seems neither MC nor Transact actually know what is going on...

Transact is not mentioned in your list of supported data feeds. Does MC now support both the data feed from Transact and trading via their brokerage?

I currently use MC 6.0.1 with several custom indicators only for charting (I prefer to use a different platform for trading orders). Do I have to switch to 6.0.2 if I do NOT send any trade orders via MC? Because of the custom indicators I would rather not switch unless I have to. I am not interested...

Any idea about the expected timing of the Transact API completion?

Do you plan to support the Transact data feed anytime soon?

When do you expect to release the 64 bit version of MC?

Thanks Mike. Just did the same with my MC. Will post here if my memory message problem persists.

For all Win7 64 bit user !!! The affected registry_entry is stored at : HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\TSSUPPORT\MULTICHARTS\MEMORYMONITOR. Hope this helps. Doubleklick on the entries and change from 'Hexadecimal' to 'Decimal' and change it. I tried 1995 as a value and stressed MC with imp...

tcat wrote: FogChaser2011 wrote: Quote: tcat wrote: 2) One thing that annoyed me with version 6 and is still there in the beta release is the "Your PC is running out of memory" The key mentioned in your response is not present in my registry. I am certain of this, checked and verified several times...

tcat wrote: 2) One thing that annoyed me with version 6 and is still there in the beta release is the "Your PC is running out of memory" window (not to be confused with the memory warning pop-up). The issue I have with this window is that nothing can be done but to kill MC if you want to get rid of...

Please understand that T&S is not a optional feature but a must have functionality for discretionary (or what you call manual) trading. It is a must have tool and you should have prioritized it much higher a long time ago. Things like trading off the charts are nice to have but it doesn't matter how...

I just posted on this in a different thread and then noticed this discussion. Time & Sales has been requested a number of times in the past, and the persistent reluctance of the MC developers/management to implement this essential feature is rather odd and certainly doesn't increase MC's chances of ...

Slow to load data in active markets, sometimes to the point of becoming practically useless. tsserver sometimes fails to terminate upon MC shutdown, generates memory overflow messages, and keeps invoking eSignal data manager. I have to manually terminate the process from task manager. Very disruptiv...