Closed GoogleCodeExporter closed 8 years ago
Thanks, we'll look into it!
Original comment by erwin.coumans
on 17 Sep 2009 at 9:07
Adding my vote for this patch. I have a scenario where I need to generate convex
decompositions for procedurally generated geometry, but there is generally at
least a
10:1 ratio of instances of the shapes (with different scale/position/rotate) vs.
unique shapes. This would allow me to only store vertices for the unique
geometry.
Original comment by jhurlima...@gmail.com
on 28 Apr 2010 at 7:44
Actually, I just realized my scenario requires non-uniform scaling along the
three
axes so this particular solution wouldn't work. Could be useful for other
scenarios
though.
Original comment by jhurlima...@gmail.com
on 28 Apr 2010 at 3:50
@jhurliman
So your child shapes are mainly btConvexHullShape?
We could make it easier to share such shape (its vertices) using different
non-uniform
scaling. Would that help you?
Original comment by erwin.coumans
on 28 Apr 2010 at 5:05
@erwin I'm using convex decomposition, so all of my child shapes are
btConvexHullShape.
Being able to share the vertex data for the convex decompositions across
different
shapes each with non-uniform scaling is exactly what I'm looking for.
Original comment by jhurlima...@gmail.com
on 14 May 2010 at 7:55
The btConvexPointCloudShape allows to share vertex data, each with different
non-uniform scaling.
Original comment by erwin.coumans
on 7 Apr 2011 at 6:33
We are now closing old issues that are not going to be fixed anymore. Our focus
is not on Bullet 3.x at http://github.com/erwincoumans/bullet3
As mentioned, the btConvexPointCloudShape allows to share vertex data, each
with different non-uniform scaling.
Thanks for the old contribution!
Original comment by erwin.coumans
on 11 Sep 2013 at 12:11
Original issue reported on code.google.com by
ol...@arcor.de
on 11 Sep 2009 at 10:02Attachments: