[AI framework test video]

Thanks, I'm really happy with how it's turned out so far. We'll see if the model extends to the rest of the more important actions and if I can clean up the code enough to put it in the workshop (one of my goals is to make everything I create reusable for others).

[Widget Progress]

Will there be a rich text multi line control of some kind? Thinking of a developer console or chat log with different colored text.

[Leadwerks Summer Games Tournament 2016]

My mind is exploding with ideas.

[More Drawing Features]

This is going to be great for my UI needs, really glad it's coming!

[A few more screenshots, working doors]

After Josh's suggestion, I am currently using a stack structure in Lua to keep track of "outer" worlds, which I then pop off and reactivate to exit an area. I think what I might do to keep video memory use constant and reduce interior load times is to place a bunch of the interior assets in an off-map area of the main map, so their resources are loaded on startup and then stay in memory. I'm okay with loading a few assets when moving into interiors if they are unique to that "tree" of maps, if that makes sense, since they will only be loaded/unloaded the first time you enter each area.

 

The biggest issue I'm running into now is that with exterior and interior assets I'm already pushing 950MB of video memory. Definitely going to need an extreme optimization pass. Or more like passes.

[Idea Fell Apart]

Can't widgetA:GetPosition() and widgetA:GetHeight() just divide their result by the scale factor? Any input is multiplied by scale, any output is divided by it.