Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
(i) Possibility to change the space between candles
Already in Project Management under reference MC-320: MultiCharts Project Management - Issue MC-320 - Changing candle / bar width independently of spacing For me, this is quite an issue, because I am working on the discretionary side, so I have to be comfortable with the appearance of the bars. I like a lot NinjaTrader and TradeStation possible displays. What a pity that the space between bars could not be changed (yet) under MultiCharts.
(ii) Possibility to multiply the prices of an instrument by a given multiplier
Already in Project Management under reference MC-773: MultiCharts Project Management - Issue MC-773 - price multiplier for symbol mapping (eSignal and IB) to allow trading
This issue prevents from trading some instruments with some data feed and brokers. Let's take an example. The prices of Cotton @ ICU (NYBOT) are 100 times higher in eSignal (typically: 86.61, CT #F) than Interactive Brokers (typically: 0.8661, CT H2). So it is impossible to reasonably trade this instrument with MultiCharts using IB when reading prices from eSignal. The solution could be to apply a custom price multiplier to eSignal data.
The above being said, I think that MultiCharts remains a great tool!
Nicolas
Can you help answer these questions from other members on NexusFi?
MultiCharts is C# behind the scenes, their PowerLanguage EasyLanguage is an interpreter to C#. If you look at FXCM Strategy Trader, it is C# for scripting --- and while FXCM owns that trading platform, it is essentially a MultiCharts fork/OEM.
EasyLanguage is an asset. But would be nice to be able to directly use C# as well without DLL's. I am not sure what their decision process is or reason to not offer this, but I am sure they have some
When using easylanguage id like to see an option to setprofittarget and setstoploss in ticks and not just dollar amounts. Ill like the interface to be quick when loading charts and not slow like it is currently. Id also like to have alerts enabled when using strategies and not just for indicators. If they can do this...then all the tradestation clients would buy multicharts and leave tradestation.
You can pretty easily handle the conversion. I've posted some code in Battle of the Bots that I use in my strategies that just sets a TickSize and TickValue for every strategy as a var, and you can easily then set a stop/target in ticks and just carry it forward to a dollar amount in the function.
With regards to slow charts, I just want to say that has not at all been my experience. Charts load instantly. So it must be something else, either hardware, historical provider, indicators, etc.
cumulatative delta volume indicators like Investor/RT
in general: volume studies like Investor/RT
Market Profile
in the order and position window the _realized_ PnL should be shown as well
TradeStation 9 compatibility
more on the bug side (either in MC or in my setup): if I trade the ESH2 in the DOM using IB and chart @ES# from IQFeed I do not see my orders on the chart
possibility to group indicators and studies (hierarchical). a flat list is confusing..
yes, but somehow it does not work.. might be a problem with how I have set things up. I still have to prepare screenshots and a detailed description of what is (in my opinion) happening and send it to them. Just hadn't had the time yet.
I tried looking in the battle of the bots forum and did and advanced search for all your articles. Could not find the code. Please tell me which post # has the correct coding for the stoploss and tp for ticksize.
Most of you are probably aware of the popular book "Fooled by Randomness", by Taleb. His other work includes "The Black Swan: The Impact of the Highly Improbable".