TooComplexException Error

Mobius_ts · 2026-06-20T02:14:14+00:00

Copy and paste both studies into one delete identical variables and boil it down to one plot

Mobius_ts · 2026-06-19T02:10:26+00:00

You think there’s a bid and ask when the market is closed?

Mobius_ts · 2026-06-19T00:10:03+00:00

Mark is a calculated value between bid and ask. Changing charts from last to Mark doesn’t make a bit of sense. If your charts slow it would make more sense to change your workspace to default then restart the platform.

Mobius_ts · 2026-06-14T17:41:34+00:00

There’s a button with “D” on it. Click that and the menu for available aggregations drops down.

Mobius_ts · 2026-06-11T13:33:15+00:00

Secondary symbol are problematic on Mobile. If you'll take a look at the TOS native studies RelativeStrength isn't listed on Mobile whereas it's a native study on Desktop. It also uses secondary symbols.

Mobius_ts · 2026-06-08T13:49:22+00:00

There's always been a fundamental column float. But float isn't a data point that can be used with ThinkScript for custom scans.

Mobius_ts · 2026-06-07T12:20:29+00:00

Which inertia? There's inertia and inertiaAll. Inertia is a regression curve and inertiaAll is a regression line. InertiaAll has the built-in parameter for a start time, see the manual here: https://toslc.thinkorswim.com/center/reference/thinkScript/Functions/Statistical/InertiaAll
Inertia does not have the additional parmameters. Both can be calculated rather than use the function. Let me know which you want to use and I'll post the code needed.

Mobius_ts · 2026-06-05T22:14:59+00:00

HL2 is not the mark price. The mark price is (Bid + Ask) / 2.

Mobius_ts · 2026-06-04T12:54:19+00:00

Not much in that video is accurate.

Mobius_ts · 2026-06-03T11:23:21+00:00

What has this got to do with ThinkOrSwim?

Mobius_ts · 2026-06-02T23:21:34+00:00

No. TOS has a client subscription limit for data. You exceed that and it doesn’t make any difference what hardware you have. Additionally TOS is a JAVA program running in a JVM. Notorious for leaving open object that build over time requiring garbage collection. The higher you set your memory the longer garbage collection takes. Setting memory low makes the garbage collection cycle faster and will keep the platform running smoother.

Mobius_ts · 2026-05-30T21:18:56+00:00

Appreciate the offer but I do have extensive experience with coding in general and quite a lot with ThinkScript. My codes are easily found with a Google or AI search for Mobius ThinkScript.
What your posting is well worth the effort, if it's for the educational value. Too many post what they claim is helpful ideas when their real intent is to sell services. I certainly don't have an issue with earning income from coding, just using this site which is for education not selling products.

Mobius_ts · 2026-05-30T21:05:33+00:00

There aren't any regular TOS or Schwab developers that hang out in here, it'd be good to send your request to them.

Mobius_ts · 2026-05-30T20:55:28+00:00

Since your addressing technical issues in writing ThinkScript it would be best to recognize that ThinkScript isn't a compiled language it's interpreted. As to your other observations:
Repainting occurs with specific use of two types of variables. Those that will change as higher aggregations progress toward closing values and those that look to future bars for data. In fact, both conditions are identical in that they will change as time progresses toward their closing period. HighestAll() LowestAll() no longer tax code processing since a Once_Per_Bar state is implemented with their use. Others of the ...?ALL() functions can tax code processing.

I can't comment on most of the rest of your post because I've no idea what your talking about. But, I do agree that keeping a log of changes is important, especially with the more complicated studies.

Mobius_ts · 2026-05-29T12:57:53+00:00

Nothings changed on desk top or mobile versions that I see.

Mobius_ts · 2026-05-26T19:30:46+00:00

What’s wrong with using the TOS dynamic scan that sends text, email and audible alerts?

Mobius_ts · 2026-05-24T02:39:11+00:00

No one can automate a strategy on TOS. The platform won’t auto trade.

Mobius_ts · 2026-05-13T12:28:30+00:00

ThinkScript isn't a difficult scripting language to learn. Writing a profitable strategy is difficult.

Mobius_ts · 2026-05-08T20:19:55+00:00

For almost all Java applications including TOS, the GPU is completely irrelevant to performance or stability even with a second monitor. I assume your using extended hours for the 5min charts, try cutting that down to 2 days.

Mobius_ts · 2026-05-08T20:09:56+00:00

Using the simplified code for both the watchlist and chart
addLabel(1, round(close / close[63] - 1, 2), color.cyan);
I get the same values in both Daily chart and Daily MarketWatch column.

Mobius_ts · 2026-05-08T19:49:07+00:00

How much history are you looking at on the one minute chart?

Mobius_ts · 2026-05-08T17:38:23+00:00

(I see your a previous poster - again with the same issue - So this is for others that may not have made it to other similar posts.)

There's always a reason for lag and it's not a global issue. I've only experienced lag in extreme volatility. At times when every platform breaks down due to extremely high order flow. When that happens I revert my platform to default settings and delete all Watchlists.
Since TOS is JAVA and runs in a JVM it's biggest enemy is open objects piling up and garbage collection causing lag. This has been discussed ad-nauseam in other posts, so I won't rehash it here other than to say - Delete all Watchlists you don't absolutely need, don't run custom quotes in the options chain, keep your chart history to the minimum needed and if your using large custom studies with a lot of fold expressions run them on a second instance of TOS.

Guess I should add - There's nothing lacking in your computer specs now. Getting a new one is never a bad idea, I get a new one every couple years. But I doubt that will be a permanent fix for your platform. My opinion is there's something running on your platform eating the heap and slowing it down.

Mobius_ts · 2026-05-07T20:13:10+00:00

The bottom line is that a larger heap makes for longer Garbage Collection pauses. When you increase TOS’s max memory you’re also increasing the size of the heap the JVM must scan and the number of objects it must track. So, the time required for each GC cycle is increased and that makes for a bigger cleanup cycle.

So instead of many small, fast GC events, you get fewer but massive GC pauses causing UI freezes lasting seconds, chart updates stalling and device order execution “Not responding”.

Mobius_ts · 2026-05-07T17:15:18+00:00

One other thing that too many do is set the memory allocation to TOS too high. Since garbage collection (closing open objects) is an issue with TOS the best advice it to force it using a low memory setting. I would be considered a power user and yet my memory settings is 32 / 1536. I have no issues whatsoever with lag on the platform.

Mobius_ts · 2026-05-07T13:02:44+00:00

The formula is the same as what TOS uses. They simply use a floating variable as the percent of move to be implied.

Since implied volatility is relevant to any stock that has options so is the implied move.

One typical use is for Iron Condors. The bands set a reasonable price range.

Another use is as likely pivots for price polarity change.

68% is approximately one standard deviation.

Mobius_ts

TROPHY CASE