I can’t say for sure – I’ve heard multiple people say frame pacing is better, and I’m happy to hear that, because that’s a big goal for us, but we’ve done a number of things to try to make our within frame work more predictable and efficient, and we can’t say what has made a different. My thinking was that we’d fix _all_ of this kind of stuff that was mandatory to port to Vulkan, switch to the Vulkan driver, and then re-profile.

Right now, even if we do things right (and us doing things wrong _is_ a real source of problems, especially in 11.26), the GL driver can still hose us, and we sometimes see that in traces. It didn’t seem worth it to spend a lot of time going in with Instruments and Vtune just to discover that the GL driver still defers work and then does it “just in time”.

Is this why frame pacing improved so drastically in 11.30b1? When the beta released, everyone was arguing over framerate but what I noticed immediately was that the sim was playable down to 15-20fps. Assuming it’s not placebo, great work.

It is not yet multi-core. There is almost no change in the pattern of multi-core dispatch in 11.30 compared to 11.26.

A calendar? You mean the thing I use to separate my spaghetti from the boiling water when it’s done? I’m not sure how that helps me with my SSL certs, but I do have three of ’em. I’ll try waving one at my computer next year. 🙂

I hope above-mentioned off-screen rendering is already capitalizing on a pool multi-cores (or at least multi-threads)

There’s this thing called a calendar. You may have heard of it, and you can even get them on your phone these days. Here’s the trick… when you renew your cert, put an entry in the calendar 1 year from now minus a couple of weeks, saying something like “Don’t forget to renew the web certs AGAIN!”. Works a treat. Ask me how I know…

With favours thrown in by Mr. Murphy, the cert expired on a weekend. Of course it did… I mean – when else could it possibly expire on? 😉

We’re working on it!

I’m sorry, but we aren’t going to do a dev guide to art controls. The whole point of art controls is that they don’t “Cost” us (in terms of development time from coders, artists, doc, testing) the way a real SDK does because we don’t do the entire document/sample/compatibility process. So writing a guide is both in the same bucket as providing compatibility (spending on dev time on a non-SDK) and it also sends a very wrong message to people – “hey, come use this thing, we want you to base your add-ons on it.”

You should get your SSL certificate renewed.