• Isadora
  • Get it
  • Forum
  • Help
  • ADD-ONS
  • Newsletter
  • Impressum
  • Dsgvo
  • Impressum
Forum
    • Categories
    • Recent
    • Popular
    • Tags
    • Register
    • Login

    Mapper quad selection heierarchy

    Feature Requests
    3
    4
    1.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • FredF
      Fred
      last edited by

      Lots of posts on the mapper these last few days as I am trying to make use of it in a fast repeatable workflow. Again, I am not sure if this a design feature, so if I can get some feedback then I will submit a bug report or feature request appropriately.

      I am having trouble understanding the selection logic for overlapping points on the mapper. 
      I am using the snapping and have quads that share vertexes. I feel like I should click in the centre of the quad and then that quad becomes the focus, ie I click in the quad in the top left corner and if I go for any of the points of that quad that are shared with any other quad I will be moving the points form the top left as I click inside it last.
      However there seems to be another logic, most often the points I drag that share vertexes are not from the last quad I clicked into. But I am looking for the logic. 
      Also on a few rare occasions in the output mapper I have gone to move one of the points that share vertexes and it moves the point of two quads at once. I tried shift click quads to reproduce this behaviour but cannot make it work. In some circumstances this could be great, I am not sure how it happened or how to reproduce it. 
      So it would be great to know what is built in logic (and maybe why) and what is features from these experiences.
      Fred

      http://www.fredrodrigues.net/
      https://github.com/fred-dev
      OSX 10.15.15 MBP 2019 16" 2.3 GHz 8-Core i9, Radeon Pro 5500M 8 GB, 32g RAM
      Windows 10 7700K, GTX 1080ti, 32g RAM, 2tb raided SSD
      Windows 10 Threadripper 3960x 64g ram, 1tb NVME, rtx 2080ti + rtx2070 super

      1 Reply Last reply Reply Quote 0
      • DusXD
        DusX Tech Staff
        last edited by

        Fred. Not a solution or explanation but maybe helpful to your current work. Try making use of the layer solo option. Once solo is active for a layer there will be no conflict selecting points.

        Troikatronix Technical Support

        • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
        • Isadora Add-ons: https://troikatronix.com/add-ons/
        • My Add-ons: https://troikatronix.com/add-ons/?u=dusx

        Running: Win 11 64bit, i7, M.2 PCIe SSD's, 32gb DDR4, nVidia GTX 4070 | located in Ontario Canada.

        1 Reply Last reply Reply Quote 0
        • FredF
          Fred
          last edited by

          Yes, that was how I got around it, lots of extra clicking away from the task at hand.

          http://www.fredrodrigues.net/
          https://github.com/fred-dev
          OSX 10.15.15 MBP 2019 16" 2.3 GHz 8-Core i9, Radeon Pro 5500M 8 GB, 32g RAM
          Windows 10 7700K, GTX 1080ti, 32g RAM, 2tb raided SSD
          Windows 10 Threadripper 3960x 64g ram, 1tb NVME, rtx 2080ti + rtx2070 super

          1 Reply Last reply Reply Quote 0
          • D
            DillTheKraut
            last edited by

            This is something I get into often too. I think, at least the editing of points should be restricted to the splice/layer that is actually marked/active.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post