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)
my guess is that MC can't decide if they can allow themselves to be greedy with MC.NET or to play tactical game, kill NT7, and get NT7 users first. Their decision on price policy will be game changer that's for sure. Wise player would look into perspective not immediate short term gain... Shortly we will see, will see...
Can you help answer these questions from other members on NexusFi?
NT pros:
- discretionary trading:
* beautiful charting capabilities, candle outline coloring from scripts, regions, etc
* configurable ATM order entry strategies with multiple targets, BE, trailing;
- .NET scripting, but has API, etc. shortcomings;
- availability of data feeds in demo mode (however buying live license locks you in to one data feed provider only! You can't have other feeds even if you are NOT sending live order to them unless you pay for multibroker license or switch to demo. Nonsense beyond words.)
NT cons:
- absolutely crappy (unstable and slow) app architecture and almost everything else from data storage (esp. when working with different data sources for the same instrument to backtesting.
- no independent MC "QuoteManager" like app to manage multiple data sources/feeds;
- single app architecture - i.e. backtesting or data import can crash your discretionary charts and strategies, everything, workspace won't restore on restart;
- no hist. bid/ask and CDelta ability, no per tick, "inside bar" backtesting;
- no tabbed workspace management, no window managment to arrange windows, charts cannot be tabbed or selectively linked by TF interval, account or instrument. See MBT Desktop Pro how it should be done.
- constant instability (crashes if left for long runs) and inconsistency with results while developing/backtesting;
- unsuitable for automated trading because of the way it handles reconnects, errors and API internals;
- too lengthy release cycle - 1 version in 3 years, always lagging behind requests;
- but most importantly - poor NT management's attitude and ignorance to listen to the needs or reports of it's users, pretending "your case is isolated, nobody else is having/need it". If you report bug - I recommend to send screenshots.
In the light of this MC main core and architecture are light years away, although I don't especially like bulky MC's charts and config dialogs. NT's grid style indicator configs are more convenient and provide more flexibility. Winner is Multicharts anyway.
Just read on the MultiCharts blog that MC.net will support GDI+ drawing on the chart. The example they showed was a DOM running embedded within the chart with the capability to add trade buttons.
Is anyone here included in the beta? If so, would you be willing to post some code examples of MC .NET? I don't meet the requirements for the beta (experienced .NET programmer) but I'd love to see some code examples. Anyone willing to copy-paste something?
I 2nd that request. And if Volume Profile is on .NET, or if such has been created already, a screen shot of that would be nice to see too... MC, using EL / PL, seems not to be the best environment for market profiles...
The closed beta for MC .NET has started. I assume I'm not the only one here who got the email. And the email says to keep everything confidential until the public beta. I'm going to respect that; I really like TS Support and Multicharts so I don't want to screw up that relationship.
What I will say is the same as what others are saying -- it's essentially the same application from a user perspective until you click on the "PowerLanguage" editor, which is now sporting .NET instead of Easy Language. And you can use any editor to edit the indicators / signals / functions, from notepad to visual studio 2010. The latter providing far better help and support for classes and other things .NET. The compiling is all done within MC, you can't do it in visual studio.
