That sounds like a fun issue and a neat project. Is it drone/iot related or larger commercial vehicles? Do you have a link to any public stuff? I don’t want to jack the topic, but I’ve been trying to find a “simple” fluid dynamics simulator for novel drone configurations for this idea I have. But I just don’t have the time to devote full resources to it right now.
Anyway, my code is TypeScript with only my custom libs: helper-gib, ts-gib, core-gib being the main ones. At first I was pasting in the entire codebases which would get me to about 700K. You can check out the code, but these are not websites nor widgets. It is a unique approach to DLT that looks more like a generalized git than anything else. The ability for the model to grasp nuances was what got me. But I had to learn through trial and error how to decompose problems and how to get the model used to my coding style.
Is this an issue with the context window or the complexity of the domain space? I have found that if I try to get the model to do too much at once (that complexity threshold you mention) OR if I try to override what the model really wants to do, then that is the time it gets “frustrated” and can start acting erratically. The 2.0 Pro model in my case was a straight example of just switching to the model and giving the exact same prompt that I would give the 2.0 Flash and it would spit out gibberish. I tested this in multiple different chats at multiple different context sizes and gave feedback here on this forum.
So like you say, mileage may definitely vary (a little logical fun there). But for me it was so shocking that the large context window actually worked so well which is why I responded here. Also that it was a learning process on understanding the capabilities of the models, that I was thinking to convey to @Jowo and whoever else might benefit. I have definitely been frustrated at times, but overall working through this has been beneficial for me. Great product.