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)
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
StockSharp is currently being refactored so I'm haulting investigating until it is complete. Initially, there appears to be a lot of improvements in the way historical data is handled.
Hi Jason, I am currently looking to get this to work as well. How did you rectify the Actipro Licensing issue? Thought there was an issue with the Licenses.licx file but am not sure how to fix it.
Ok lets start to discuss there (instead of skype). I think BM forum is most suitable place for now.
Finished refactoring on last weekend. Just a few words about what actually was changed. S# had a thread-pool model based on some complex system. Now it is cutting out of the scope and may be configuralble.
S# is not an equalent of some popular systems like NT or MC (maybe changed in a future). First of all it is set of connectors that can be build on own tradying systems. At the second - it is a set of graphical components that also boost dev of own system. So Studio is not a major product. S#.API - is a major. S#.Data - is a second. S#.Studio - is a third.
So for now stablity of Studio I think was decreased from 60 to 40 % stability. Main tasks for Studio - is make it stability. There is a lot of compomnents that works fine in S#.API but absolutelly no works in Studio. Refactoring has one of target to get some stability with threading issues. Now there are still 2 major tasks: create a proper warm up strategies and create a joining historical data with a real-time.
Please help (all who was received instruction from me) to new one colloborators with build of sln. Including license issues.
a) StockSharp is open source
b) There are no premium services, no fee based options, and no money changes hands with customers
These both need to be true in order for you (as the vendor) to discuss your product on futures.io (formerly BMT). Otherwise, it is considered self-promotion which we do not allow.
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
I tried over the weekend to track down where the list of connectors gets populated and still can't figure it out. FIX is no longer in the drop down list after the most recent changes.
@stocksharp Thanks for jumping in here. I think this platform has a ton of potential and hopefully we can get more nexusfi.com (formerly BMT) developers digging through the source.
Jason i think bug in combo box population... For now FIX is useless for american trading cause FIX has a poor standard restrictions and should to have dialectic.
Studio at the first launch create a connection to our demo trading server. Server side works on FIX protocol.
Broker: NT Brokerage, Kinetick, IQFeed, Interactive Brokers
Trading: ES
Posts: 159 since Dec 2014
Thanks Given: 40
Thanks Received: 166
I knew it was a bug but finding it has proven difficult. I'm still learning how the APP is implemented in hydra and studio. My main objective is to get real time and historical data piped in then work on finding any other bugs. Getting the data in seems to be the biggest hurdle so far.
