VectorStyler
    • Categories
    • Unread
    • Recent
    • Tags
    • Popular
    • Register
    • Login

    Scaled object copies by 75% are bigger instead smaller when using Randomness.

    Scheduled Pinned Locked Moved Questions and Support
    11 Posts 4 Posters 2.5k Views 3 Watching
    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.
    • S Offline
      Subpath
      last edited by

      When I scale an object by 75%, in this case a circle, I expect the
      copies to be smaller than the original.

      However, this isn't the case when I use the random function. To
      my surprise, some copies are even larger.

      It would be nice if it worked as expected.

      0_1761909872268_scaled copies.png

      Win 11
      CPU: AMD Ryzen 5 9600X, 6-core.
      GPU: Nvidia Geforce RTX 5070.

      VectorStylerV 1 Reply Last reply Reply Quote 1
      • VectorStylerV Offline
        VectorStyler @Subpath
        last edited by

        @Subpath Randomization selects a +/- scaling around100% in this case.
        I will check if this is possible to change.

        S 1 Reply Last reply Reply Quote 1
        • S Offline
          Subpath @VectorStyler
          last edited by Subpath

          @VectorStyler said in Scaled object copies by 75% are bigger instead smaller when using Randomness.:

          @Subpath Randomization selects a +/- scaling around100% in this case.
          I will check if this is possible to change.

          As I already mentioned, I see no reason for this as a user.
          I would expect copies below 75% or at most exactly 75%.
          Anything else doesn't make sense to me and isnt useful.

          In my case, the circle should maintain a fixed size and not increase
          in size. But inside it, it could contain several smaller circles of
          random size.

          Win 11
          CPU: AMD Ryzen 5 9600X, 6-core.
          GPU: Nvidia Geforce RTX 5070.

          VectorStylerV 1 Reply Last reply Reply Quote 1
          • VectorStylerV Offline
            VectorStyler @Subpath
            last edited by

            @Subpath said in Scaled object copies by 75% are bigger instead smaller when using Randomness.:

            I would expect copies below 75% or at most exactly 75%.

            This is a bit of a problem. What happens if the user sets 200% ?

            S 1 Reply Last reply Reply Quote 1
            • E Offline
              EricP
              last edited by

              @VectorStyler I wanted to raise a feature request on this and the randomization in transform panel.

              I also have frequent need for asymetric randomization, meaning that if I select 75% scaling, I would want the objects to be scaled randomly between 75% and 100%. If I choose 200%, I expect objects to grow from 100% to 200%.

              Same goes for x, y offset where the randomization gives same results in positive or negative offset. That's not always desirable when you want to shift copies to one side randomly to create a trail

              There can also be a need for scaling symetrically around 100% (the +/- scaling), which is another use case.

              With only one slider, it is not easy to accomodate both needs. Maybe you need 2 sliders (min, max), or better, a checkbox to choose the mode to use

              It would be for all transform parameters, not just scale.
              Also, a reset button for the transform panel would be welcome as there are a lot of parameters
              0_1761928189645_68b854b3-2ab8-4b03-b250-1cf6bc5bee9d-image.png

              1 Reply Last reply Reply Quote 1
              • S Offline
                Subpath @VectorStyler
                last edited by Subpath

                @VectorStyler said in Scaled object copies by 75% are bigger instead smaller when using Randomness.:

                @Subpath said in Scaled object copies by 75% are bigger instead smaller when using Randomness.:

                I would expect copies below 75% or at most exactly 75%.

                This is a bit of a problem. What happens if the user sets 200% ?

                I think I understand the problem. If I'm correct, you mean that, for
                example, at 200%, the Randomize function should consider both
                smaller and larger sizes.

                So, the Randomize function should always consider all options?
                Which, of course, also has its merits, as such cases are possible.

                Perhaps a switch in the Transform panel may be possible to toggle
                between the following states:

                One state would generate all sizes when Randomized.

                The other state would generate only smaller sizes for anything
                below 100% and only larger random values ​​for anything above
                100%.

                As an example Paragraphic always generate smaller copies when
                scaling down and larger copies when scaling up.
                Here a picture

                0_1761928917376_Paragraphic-random scaling.png

                Win 11
                CPU: AMD Ryzen 5 9600X, 6-core.
                GPU: Nvidia Geforce RTX 5070.

                VectorStylerV 1 Reply Last reply Reply Quote 1
                • VectorStylerV Offline
                  VectorStyler @Subpath
                  last edited by

                  @Subpath I will think of a solution for this.

                  1 Reply Last reply Reply Quote 1
                  • F Offline
                    fde101 Global Moderator
                    last edited by

                    Paragraphic's repeat transform is not scaling randomly. When you specify that scale a value less than 1 will give you smaller circles each time, while a value greater than 1 will give you larger ones each time.

                    You need to explicitly tell Paragraphic to use randomness, and when you do, it allows you to specify a seed and a min/max range within which to randomly modify the values it is being applied to:

                    0_1761996997530_Screenshot 2025-11-01 at 07.35.01.png

                    1 Reply Last reply Reply Quote 1
                    • S Offline
                      Subpath
                      last edited by Subpath

                      @fde101

                      The point was simply to demonstrate the principle of paragraphic scaling, and in my example, I only mentioned how paragraphic scaling works, not that it was randomly scaled.

                      You can, of course, also generate copies randomly by using the "Randomize 2D" input node. Here too, the size of the original object will not be exceeded as long as you keep the Value Range below or at a maximum of 1.

                      If you want to like to have random values ​​within a larger range,
                      then you can also enter values ​​greater than 1.

                      0_1762007775565_Random Value.png

                      Win 11
                      CPU: AMD Ryzen 5 9600X, 6-core.
                      GPU: Nvidia Geforce RTX 5070.

                      1 Reply Last reply Reply Quote 0
                      • E Offline
                        EricP
                        last edited by

                        @VectorStyler was this changed in a recent release ?

                        The transform panel randomize now works as expected (eg scaling up or scaling down randomly, instead of both at the same time). I must have missed it in the release notes.
                        0_1763658849752_e32ce69a-2405-43fd-835a-91e7d9fbbb08-image.png

                        VectorStylerV 1 Reply Last reply Reply Quote 2
                        • VectorStylerV Offline
                          VectorStyler @EricP
                          last edited by

                          @EricP said in Scaled object copies by 75% are bigger instead smaller when using Randomness.:

                          was this changed in a recent release ?

                          Yes, there were changes here.

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