Radius > 0 may or may not add a side, or add 2 sides, depending on other parameters. Taper > 0 may add 1 but could add 2 unless one or both tapers are 1.0. It's all very complex with lots of interactions. We could probably get together sometime and hash it all out but I probably wont have time for a while. One could also probably make the prim with PrimMesher and count the number of sides, but PrimMesher occasionally adds an extra side (well actually fails to delete an extra side) so may not be a perfect solution, and would also be somewhat inefficient way of doing it.
On Tue, Mar 25, 2014 at 11:40 PM, Oren Hurvitz <[email protected]> wrote: > Yikes! How can I know these things in order to fix GetNumberOfSides()? > > If shape.pathTaperX>0 or shape.pathTaperY>0 then +1 side? But I think this > doesn't actually happen unless Radius is also >0. I really don't understand > how these parameters interact. > > Maybe we should just drop GetNumberOfSides() altogether. Every place that > currently uses this function should simply check all 32 possible sides, and > Bob's your uncle. > > > > -- > View this message in context: > http://opensim-dev.2196679.n2.nabble.com/How-many-sides-does-a-tapered-torus-have-tp7579043p7579059.html > Sent from the opensim-dev mailing list archive at Nabble.com. > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev >
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
