Couple of missing billboard functions.

[mkultra333]

Two obvious functions I wanted from billboards that seem to be missing.

First up, there's no pBillboardset->SetMaterial(pMaterial) function. Minor issue, I used SetMaterialName instead, but SetMaterial would have been handier.

Secondly, there's pBillboard->setRotation(Radian) but no pBillboard->setFlip(U_andor_V). No way around this one that I can see, and from an art point of view flips are just as important as rotations. Lack of flips has halved the variation I can get from my animated explosion texture.

One other thing, currently rotation rotates UVs, so unless you're doing 90 degree rotations you have leave lots of headroom around your particles, virtually halving their resolution, or else the corners will rotate onto parts of the texture they shouldn't touch, causing visual glitches. I don't know if it's possible, but it'd be neat if there were a second rotation method that left the UVs intact and rotated the billboard vertices instead. I expect there'd be a speed penalty, but if it wasn't too high I'd be willing to pay it in some circumstances (such as with my explosion animation.)

I'll survive without these, but thought I'd mention them.

[FlorianGeorge]

yes, I just ran into the missing void BillBoardSet::setMaterial (const MaterialPtr &material) as well, would make sense to make it coherent with other similar objects, like SubEntities

[spookyboo]

Use setBillboardRotationType to either rotate uv or vertices.

[masterfalcon]

Don't forget to enter bugs for feature requests too!

[ImpalerWrG]

Bump on requesting SetMaterial(pMaterial), I'll see to getting it on your official feature request system. *Looks for feature request system* Come on already, this one is really quite obvious and I'm now going to have to create a whole system of name generating and string passing to do what I need as I'm using procedurally generated textures and materials. String arguments are for kiddie programs with 3 textures anyways, pointers are how real programs operate and should take precedent if only one is going to be available.

[Jabberwocky]

Probably your best bet is to code the change yourself (ogre is open source), then submit a patch with your change to get it accepted into a future ogre release.

[masterfalcon]

Yeah, you could either submit a patch or a bug. List the reproducibility as "Feature". http://www.ogre3d.org/mantis/

[FlorianGeorge]

Added it to Mantis: http://www.ogre3d.org/mantis/view.php?id=365

Category doesn't have a "Feature Request" option, so I selected "Core Library Bugs".
Reproducibility doesn't have the option "Feature", so I selected "always".
Feel free to add the missing options to the combo boxes and/or edit the entry as you see fit, was my first submission.

[betajaen]

If you put "[Papercut]" in there somewhere it is more likely to be noticed.

[FlorianGeorge]

uploaded a patch (or two) a few weeks ago