Doug Hayman

Sorry, stupid question, but on news windows there is a column which is sometimes clear, sometimes red, sometimes green. What does the Green or Red signify? Thanks in advance.

Not sure if this is intended functionality or a bug. Just to add some context: Depending on whether there is a Trending vs Range bound market, I like to use OTA vs. OTOCA conditional trade types on the DOM. The initial MT config values are used initially for each conditional trade type which is fine. However, due to market dynamics during trading day, I may want to switch between these 2 conditional trade types (and may want to alter config values for each trade type at any given time). I notice that when I toggle between the 2 during a session, the current config values of the session are not persistent for each trade type, and revert to MT default config values. As an example: 1) I bypass MT config values during a session for OTA type trade and click OK; 2) Later I switch to OTOCA and modify config values from the initial MT defaults; 3) Later I switch back to OTA trade type and the bypassed config values from Step # 1 are not preserved; they revert to MT default config values. Is this intended functionality or a bug?

Thanks. One thing to add, it's only' when I hit the "OK" button coming out of the OTOCA config screen (regardless of whether changes are made or not). If I hit "Cancel" from within the OTOCA config screen, the problem does not occur.

I am running latest Beta. I am set for Conditional Order Auto -> OTOCA, so that orders will be executed via Limit Orders (my default order type). When I go into OTOCA config on the DOM to either change or inspect OTOCA actions, and click on OK, the default order type, goes from "Auto" to "Market", thus changing my order type from "Limit" to "Market. Am I doing something wrong to cause this?

Hi guys, Trading MES futures on IB with 5 minutes bar/volume chart. Please see pic below. There were between 3k-5K contracts traded during the 5 minute period where the volume chart shows a spike. It was displaying fine, but I shutdown MT and restarted, and upon re-start of MT, the current volume bar that was active shows this large spike volume bar, which is incorrect. I tried backfilling and also tried spike removal on this volume chart, all to no avail. I also tried removing/re-adding the Volume indicator, again this didn't help. Also, when I mouse-over this erroneous volume spike, it does not display the volume amount, whereas all surrounding volume bars (that are scaled to this big volume bar display-wise) do indicate the volume amount during a mouse-over in a rectangle box. Additionally, on the OHLCV display, the erroneous bar indicates a Volume for that 5-minute period of the total contract volume of the day. Here's what is looked like. I'll send log file over as well.

Ok Mike, great, and thanks!

Yes, an enhancement to provide an audio alert and/or visual alert (maybe blinking) when a countdown threshold during bar formation is reached, would be nice.

Yes, correct! I can live with switching symbol during live trading in the interim then. Thanks in advance for looking into it.

Jerry, Just executed this morning and sent log file after first starting MT. I'm aware of how AUTO mode can be a Limit or Stop order depending on price execution; that is not the issue here. Not sure if your Log file is cumulative for the day or not, but please LOOK AT 2ND LOG FILE that I sent you, since this contains the "Flatten" action (forgot to do this before sending 1st log file). So, here's what I did. 1) I hovered over a Sell price which was displaying "LMT 1" correctly. Market price is below this hovered price; 2) Market price rises above the hovered Sell price. Still displays "LMT 1", when in actuality it is really a "SELL STP 1" at this point; 3) I execute the Sell trade. Trade fires off as a LIMIT trade (which is fine for me since I want this trade to fire at this price). 4) IB executes fine, and creates the pending Buy Stop Leg fine. Your transactions screen (see picture below) looks fine with Limit Order executed and 1 Buy Stop order pending. 5) However, note that 2 Buy Stop Orders (at the same price) appear on the DOM (incorrect). When I subsequently flatten, 1 STOP still appears on the DOM (and I can't get rid of it unless I restart MT). However, MT Transactions screen and IB back-end don't know anything about this rogue Stop order. It is a DOM issue only.

OK, I did find a bug today playing in Paper Mode on IB using the DOM. Trading 1 contract of MES. Trading OTA AUTO. On a Short, when I hover cursor in Sell column (but don't click to execute OTA Limit Order) where hovered price is above current market price, MT correctly displays "LMT 1" for this potential trade. While continuing to hold cursor over that price, the Market price subsequently increases (overtakes) this pending hovered Limit Order price. While the market price is above this hovered cursored LMT price, I click to execute the order and the Limit order is executed since the price is below current market price. However, in this scenario, MT creates "2" OTA Stop Orders on the DOM (which is incorrect), while in effect, only one Stop order is sent to off to IB (which is correct). If I Flatten or cancel Stop Order, the one correct Stop Order is correctly canceled in IB back-end and on MT, but one rogue MT Stop Order remains on the DOM (there are no Stop Orders on the IB back-end at this point), which cannot be canceled or removed from the DOM without restarting MT. Analogously, on the Buy Side, the same issue occurs, and is readily repeatable. Not sure, but I'm guessing that other conditional types may exhibit the same behavior. I'm sending a log file over to you if this helps at all.

Thanks for the reminder on this - I didn't realize that I initially was attempting to execute order prior to 9:30 ET - definitely an IB issue. Just entered an MES trade prior to 9:30 AM ET this morning and again the price runs through the Stop order. However, IB accepts the Stop order part of the trade. On MT, I tried Both Day and Day+Ext TIF, and both behave like this. In the past, at least for ES, IB would generate an error msg about not being able to accept a Stop Order outside of regular market hours, but for some reason for MES, they accept it, but don't execute it. I'll contact them about this. Thanks again for pointing this out.

Yes, the Stop Market Order made it to IB and was active. I cannot re-create this again; all working well. Do you think this was an IB hiccup?

P.S. More info, I have been alternating between OTOCA and OTA orders. I just re-started MT, and now OTA Stop Legs are functioning correctly. The log file I sent captured the state when things were not working as stated above. I'll post more, if I can figure out what sequence of trade events caused this.

Running the Latest Beta Build. Trading IB, MES micro futures on the DOM, using conditional OTA orders (Auto). On either Buy or Sell side, Limit OTA executes fine. Conditional Stop order is created properly once Limit order executes (verified on IB back-end). Subsequently, on both the Buy and Sell Side, the Stop Market order is run through price-wise without executing. I'm sending you log file accordingly.

ok. What’s your ETA on the API?

Jerry, is my suggestion really “managing an order”? I’m not suggesting that this implementation would be easy, but only order requirement would be understanding the open position size for determining QTY % at each level. Basically, in my example, it would require firing off 4 Limit Orders and 4 Stop orders to broker. After that the user would manually manage these open orders via MT. OCA, OTOCA, etc have been excellent enhancements to MT. But “scaling out” of trades is cumbersome, esp in faster-moving markets. If you can suggest easy ways to accomplish this that I may be missing, please let me know. Thanks again.

Along the lines of Patrick Master's Risk/Reward question/request above, would it make sense to add a pre-defined MT order type (call it RR) that facilitated scaling out of positions, since most brokers don't support this natively? Maybe up to 4 levels of pre-defined Limits and Stops legs could be defined, requiring QTY % (applied to current instrument position size) AND either % or points for price level (consistent with your current implementation). Example: I use either a LIMIT order OR a LIMIT OTOCA order to buy 4 future contracts. If OTOCA is used, I cancel the 2 corollary leg orders created when I feel comfortable to do so. I select RR trade type and based on the Leg settings and the price of execution of this trade, up to 4 Limit Orders and up to 4 Stop Market orders are automatically (that is, individually) created, with size of each proportionate to the QTY % for each Leg stipulated above. Using the DOM, it would be 2 keystrokes max: one to cancel the OTOCA order legs (if this order type were used), and one to create the RR order. Does this make any sense to do?

OK thanks.

P.S. on prior post, I realize that I can cancel current order and re-enter order on DOM (2 keystrokes), which isn't horrible. Not sure if you maintain order context in MT, after submitted to broker.

Hey guys, Quick question - assuming that I'm dealing with Limit OTOCA orders on the DOM, and I enter an order with a Limit Price with corollary Profit and Stop Legs, and trade is not filled yet. Is there a way (shortcut-wise), that I can move the Limit price on the DOM, and have the associated Profit/Stop prices adjust up or down by the same amounts, so that I don't have to manually adjust the Profit/Stop prices with secondary mouse actions? Thanks in advance

For anyone that has similar issues to the above, I added an exception in my McAfee Real-Time Scanner, to prevent "MT.EXE", the Medved Trader application, from being checked by the Real-Time scanner, on invocation. Initial loading of MT application is back to normal.

Must be my environment then. I'm using the McAfee version that is provided free by my ISP (Cablevision/Altice). I just disabled both real-time scanning and firewall, and MT starts right up, as it always did. So yeah, I need to look at McAfee rules to see what's up. Thanks for pointing me in the right direction. Even with startup delay, with all enabled, everything works normally.

Hey guys, Any significance or reason as to why the new Beta takes upwards of 45 seconds to load (where first splash screen appears) after invoking it? The program runs fine thereafter, I have plenty of disk space, memory, and processor speed. The only change on my end has been a Windows 10 Pro update of my NVidia drivers, but I haven't seen startup lag on any other applications. Anyone else seeing this?

I didn't even consider placing an OTOCA with a position already open, but I understand the dilemma. Thanks for considering. All in all, the conditional trades was a big want of mine, and I'm appreciative of its addition to the platform.

OK, I re-created problem. Here are steps that got me there with latest and greatest Beta: Using DOM to trade @MESU19 futures: - View LIMIT OTA from Menu -> Stop set at -2 points (accurately grabs my Settings Point value of Bracket High Points of 4, Bracket Low Points of 2) - Menu jump to Limit OTOCA. Executed Limit OTOCA Buy order with Profit Limit -4, Stop Market +2 (accurately grabs my Settings Point values); - Canceled resultant OTOCA Limit/Stop Legs; - Flattened Position; - All good at this point so far with Limit OTOCA Limit/Stop still at -4/+2; - Menu jump to Limit/OTA, and Stop now changed to +4 (from +2); - Menu jump back to Limit/OTOCA and Limit/Stop points now changed to -2/+4; in other words, Limit and Stop prices are now reversed from Settings values. Confirmed graphically by placing cursor in DOM for either Buy or Sell Limit trade. Can you recreate this on your end?