Steve2![]() Elite ![]() ![]() ![]() ![]() ![]() Posts: 750 Joined: 10/11/2012 Location: Annapolis, MD ![]() | Trey, If you want to report this, I would suggest posting to the Technical Support Forum or email Barry. Steve M, You are correct that Buying Power should not scale trade size, it just leverages how much money there is to trade with (i.e., should cause OV to be able to make a smaller or larger number of concurrent trades). The bug is that the OV code DOES appear to be using Buying Power to determine acceptable trade sizes rather than using the account value. Here is what I have observed. Assume that your allocations are set so trade size is about 50% of account value. You can't do this exactly due to share rounding but most generated trades come close. OV will always round shares down so sometimes the allocation is slightly smaller than 50%. Assume that your account equity is $100K and "Allow trade settings to reduce trade size" is OFF. If Buying Power is set at 100% then trade filtering appears to work correctly and up to two concurrent trades are taken at a time. If Buying Power is set at 150% then trade filtering appears to work correctly and up to three concurrent trades are taken at a time. But if Buying Power is set to say 95% then OV incorrectly filters out any trade whose allocation is larger than 47.5% (50% of the Buying Power when it should be using 50% of the account value). The correct behavior with a trade size of 50% and Buying Power set to 95% is that OV should take only one trade (at 50% allocation) at a time. The net result of this bug, when using 50% trade allocations is that you see a dramatic reduction in the number of trades taken if Buying Power is set below 100% with typically all trades filtered out when Buying Power is set below 95%. Steve |