Menu

Bug (I think) Report: Polysoup when scaling

Supreeth
2008-01-15
2013-04-19
  • Supreeth

    Supreeth - 2008-01-15

    Hello Geoffrey,

    I noticed an instance of my polygons going bonkers, but i'm not sure if this is a Bug. I was trying go back to check my steps in the history and edited the first step, the last step in the model got souped.

    BEFORE
    [URL=http://img155.imageshack.us/my.php?image=originalga4.jpg][IMG]http://img155.imageshack.us/img155/2885/originalga4.th.jpg[/IMG][/URL]

    http://img155.imageshack.us/img155/2885/originalga4.jpg

    AFTER

    [URL=http://img259.imageshack.us/my.php?image=soupedqc9.jpg][IMG]http://img259.imageshack.us/img259/4637/soupedqc9.th.jpg[/IMG][/URL]

    http://img259.imageshack.us/img259/4637/soupedqc9.jpg
    ---------------------------------------------------------------
    Download the souped gpx files here...
    http://www.ixmod.com/3d/bugs/soup.zip
    ---------------------------------------------------------------

    STEP RECONSTRUCTION

    1. Load elephant_original.gpx
    2. Select Object
    3. Switch off background images
    4. Go to first step in history
    5. Select the mesh component 'object' and scale the overall object down (about 60%)
    6. Go to any of the later stages in the model...
    7. Polysouping occurs.

    Why should this happen? I did not change the number of vertices or components. Just the overall size of the object. Should'nt it recognise the scaling change?

     
    • Supreeth

      Supreeth - 2008-01-15

      Hello Geoffrey,
      I Just tried it with other scaling sizes (I thought maybe it's a fixed size or position), but It happens even when I reduce the original cube even a little bit.

      warm regards
      George Supreeth

      P.S: Now a lot more visitors at Painless3d. Thank you.

       
    • Geoffrey French

      Geoffrey French - 2008-01-30

      Hi George,

      Sorry to take so long to reply.
      I have been extremely busy lately.

      This is not a bug in the program.
      gSculpt does not work like other procedural programs, such as Houdini, which select a component by its index.
      gSculpt records the position on the screen where you clicked to select the component, along with the viewport info.
      This means that if you modify one of the early entries in the plan (such as your scale) then entries further down will try to select
      components which are not in a different place (as a result of the modification). As a result the wrong component will be selected.
      Poly-souping will result.

      There is no way around this.
      It would initially appear that gSculpts' procedural plan would 'solve all your modifying problems', but this is not the case; there is
      provably no perfect solution!!!

      Regards

      Geoff

       

Log in to post a comment.