I’m just finishing up a couple things related to my personal project over the weekend and I have finals this week, but then I’ll try to tackle the up-convert on load, and a couple other minor things I want to add pretty quick then I guess we can start there! I kind of want to improve the serialization in general as currently it will only handle sections made via the old PMC style API. At this point it’s been used by quite a few people and appears solid (I did find a memory leak since V1 that I have since fixed). Currently it’s a feature complete version of the PMC (except those utilities and things in the BP function library)… It’s definitely major changes, I didn’t go into this trying to keep much from the PMC. I just tried to mimic it’s interface and functions, but structurally it’s similar, but a bit more complex. I’ll let you know when I’m ready, probably be 2-3 weeks would be my guess.
I remember the settings you where talking about in the pmc question I asked on the AH where you mentioned exposing the cooker config options, what else where you thinking about? I’d be more than willing to try to do whatever changes I need to do within whatever idea you/Epic has and submit them back if it helps to get it done quicker as I know that’s just one of a list of things you/Epic are trying to do. I’ll probably dig into collision for real Monday, so I’ll have a better idea after that but…
From my preliminary look a couple weeks back I figured to attempt to make the cooker callable from alternate threads and just let the PMC/RMC store a copy of the result and let the current path that happens when you invalidate the mesh use an extended version of the IInterface_CollisionDataProvider and return the cooked data instead of the raw mesh. That lets me offload the cooker entirely to a different thread, but it doesn’t take advantage of some of what Ales Borovicka was saying about being able to bypass the serialization that’s currently done. It would however let the RMC/PMC have almost direct control over the cooker and its configuration and let it pull it out of the GT. The serialization might still add some unnecessary time/work, but that at least gets the primary work moved and looked to be relatively simple way to do it compared to some of the alternatives. That’s all based off what I remember from a few weeks back, and I haven’t dug into it super deeply yet to see exactly how all parts fit together. That also didn’t assume that it would ever be used by more than just me, but if I’m going to do it and it’s reasonable to give that back since I’m sure others can use it then I’m more than willing to go a different route.