Thanks Igor for the insight!It seems the "Seconds" timeframe is not supported anymore. Still see the same UI bugs discovered in 7b1.
cheers.
I see seconds and milliseconds alright.It seems the "Seconds" timeframe is not supported anymore. Still see the same UI bugs discovered in 7b1.
cheers.
I see seconds and milliseconds alright.
Hi Igor! I’m able to see seconds and milliseconds intervals from the Bar size selector in the Toolbar area as well on may Mac!Odd. Settings->Chart->Bar Size Selector->Add Bar Size - I see no Seconds interval type in the dropdown menu. Where do you see that?
Hi Vlad!Did the new "Add Study" toolbar button disappear for anyone else (with Favorites etc)? The only way for me rn is to go through menu Study. No toolbar button, no context menu
GAi, thank you!Hi Vlad!
I’m not sure if you’re referring to this one, but I’m able to add it back to my toolbar area from: Settings-ToolBar-Toolbar- Top (under the Toolbar selector)
You’re very welcome Vlad! I’m glad I was able to help.GAi, thank you!
Yes that's it! Main toolbar in Beta2 certainly looks more like v6 than like what we saw in the demo (edit: or perhaps it was overriden during the conversion of v6 workspace from a backup). Also, while looking at this, I just realized, my Toolbar 2 only shows on secondary desktops, but not on the main console. Is this as designed?
Oof - Thanks for the heads up on this! Did you pass this along to MW support? Really hoping they can iron out all the bugs on this.Did some more testing of rithmic connection, multiple accounts and copy trader. My findings:
1. Rithmic webAPI unstable - quote feed freezes up during volatility (first ~15 min of RTH today). Reproduced on live ironbeam account as well as different props. Workaround - use Rithmic Gateway connection for quote feed (or other provider).
2. There can only be one Rithmic Gateway connection type per workspace, i.e. others need to be Rithmic webAPI (at least I couldn't make it work, getting some "OS error"). Topstep has their own farm, I assume it also uses webAPI as it didn't cause any conflicts
3. If you choose broker-specific connection type (e.g. "Ironbeam - Rithmic"), it chooses webAPI. To switch to legacy Rithmic Gateway, select instead generic "rithmic gateway" - it will work just fine with the credentials.
4. WebAPI is finicky:
4.1 worst case scenario - for one of my accounts, positions were not updating at all. I.e. limit was filled and disappeared, but position did not appear.
4.2 when 4.1 happened, the account balance also did not update at all - i.e. both cash and balance were empty. Was fixed by reshuffling accounts (removing and adding back in different order). So to avoid 4.1, at least make sure the balances show up, and then watch to orders to make sure you don't get phantom positions
4.3 even after balances started showing up, they wouldn't correctly reflect account pnl - balance would always change with cash balance after a trade
Caution - even if you use Rithmic Gateway or other provider for your quote feed, not sure if actual trade execution over other accounts using webAPI will suffer during the high-volatility hickups, didn't want to risk testing. Maybe will try with micros next time
Sure I did! Hoping for a wendys gift card from them as a token of appreciationOof - Thanks for the heads up on this! Did you pass this along to MW support? Really hoping they can iron out all the bugs on this.
Thanks for sharing Vlad! I’m glad to hear that the features that you most rely on have been resolved in Beta3.Just wanted to note that I fully switched to v7 now. The third update at a glance fixed the remaining annoyances - charts open up quickly, I no longer need to readjust DOM and T&S columns' widths every time I restart the app. Will see how performance is when the volume comes in tomorrow, but overall great turnaround on bug fixes from the dev team. Now let's hope they can get to work on our feature requests)