java3d
  1. java3d
  2. JAVA3D-294

IndexedGeometry shouldn't consider vertex not reference by index in computeBound

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3.2
    • Fix Version/s: 1.6.0
    • Component/s: j3d-core
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      294

      Description

      Note : This bug is transfered from BugTraq : BugId 4720938

      Currently all vertices pass in IndexedGeometryArray
      are taken into account in computeBoundingBox()

      We should only consider vertices actually reference
      by index array.

      ------------------------------
      Date: Thu, 25 Jul 2002 09:45:08 -0600
      From: White Morph

      Hi,

      I have 2 polygons, each uses GeometryInfo to generate its indexedGeometryArray.
      A BranchGroup is created to add both Shape3D objects into it. There are some
      problems: (please see my code attached, you can try)

      1. if I just add either of the 2 Shape3D objects into the BranchGroup, the
      bounding center is just the same as I add all of them into the group, so I
      guess the Java3D class calculate the bounding center using all of the vertices
      instead of only the vertices the Geometry object refers to.

      2. when I just add one of the polygons into the group, the picking for this
      polygon is correct, but if I add both of them into the group, the picking for
      the first one is not correct, the second one is correct.

      3. Even when I just add one polygon into the group, if I use
      PickCanvas.setShape(PickPoint, startPoint) before I use pickAllSorted(). I got a
      Runtime exception: java.lang.RuntimeException: PointArray0

      Could you please try my code? Did I have sth wrong or else? Thank you very much!

      white

        Activity

        Hide
        kcr added a comment -

        Set priority to P4: fix desired for 1.5.0 (not a show-stopper or regression)

        Show
        kcr added a comment - Set priority to P4: fix desired for 1.5.0 (not a show-stopper or regression)
        Hide
        kcr added a comment -

        P3 bug for 1.5.1 release.

        Show
        kcr added a comment - P3 bug for 1.5.1 release.
        Hide
        kcr added a comment -

        Lower to P4. Fix desired for 1.5.1, but not a show-stopper.

        Show
        kcr added a comment - Lower to P4. Fix desired for 1.5.1, but not a show-stopper.
        Hide
        jada added a comment -

        This is too risky to fix for beta release without a prior stable build.
        Set target milestone to 1.6 and up priority to P3.

        Show
        jada added a comment - This is too risky to fix for beta release without a prior stable build. Set target milestone to 1.6 and up priority to P3.
        Hide
        kcr added a comment -

        Mark issue as unassigned.

        Show
        kcr added a comment - Mark issue as unassigned.

          People

          • Assignee:
            java3d-issues
            Reporter:
            jada
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: