Karl Hillesland

Internally, we've been using vera++ with some custom rules. Spaces inside parenthesis - I don't know that we have a standard there. We do have a rule that checks for...

There's basically two shader flows, but both assume you'd manage shader code through the engine, rather than us managing them within the library. In other words, we'd expect you'd put...

The design philosophy was to allow maximum flexibility, which means passing in as much info as possible, even if not used. It also means these functions do quite a bit....

This is good. We'll try to move in this direction, although I can't give you an ETA yet.

Sorry about that. Bit of a miscommunication there.

We'd like to fix things like that, and make the library easier to integrate for production use. This is just one of many things that could change. Knowing you've worked...

Good feedback. 1,2 and 4 I had mostly guessed (and argued the same fairly early on). 3, I hadn't. for 3 - Is the issue that there's a .tfx file...

As I understand it, it was a hastily done hack to try multiple objects.

Wow! That's fantastic! (I confess I didn't actually try it yet, but it looks like you've done the right things to make it work - and that's no small undertaking)....

That's great! I'd suggest prioritizing "shortcut" in 3.1 over the skinning.