Dashed Line Spacing Does Nothing

Avatar
  • updated

Here I have created a dashed line:

Image 799

However, the spacing of the line stays consistent with 1 meter no matter what number I change the spacing option to.I believe this to be a bug, unless I am completely overlooking something.

Love the asset so far by the way.

Reporting a bug? please specify Unity version:
2022.3.11f1
Reporting a bug? please specify Shapes version:
4.3.1
Reporting a bug? please specify Render Pipeline:
URP
Avatar
Freya Holmér creator

that's odd - are you running the latest version?

if I make a line with the exact same settings it works fine. Does it have a parent object with some weird scale?

also make sure you don't have a line accidentally duplicated in the same location hiding the changes you make to the one you selected

Worst case you can always try a clean reinstall

Avatar
Harper Rhett

I appreciate the swift response!

I am running the latest version. I bought and imported the asset a few days ago. It has a parent object but the scale has not been altered (1, 1, 1). There is only one line, when I disable the game object it disappears.

The size seems to be locked too... Anyway, I tested it in a new project and it worked fine, so I removed and re-added the line to the game object and now I can adjust the size and spacing as intended. I suppose I should have tried that initially.


Perhaps these values were locked in a cached state somehow?

Avatar
Freya Holmér creator
Quote from Harper Rhett

I appreciate the swift response!

I am running the latest version. I bought and imported the asset a few days ago. It has a parent object but the scale has not been altered (1, 1, 1). There is only one line, when I disable the game object it disappears.

The size seems to be locked too... Anyway, I tested it in a new project and it worked fine, so I removed and re-added the line to the game object and now I can adjust the size and spacing as intended. I suppose I should have tried that initially.


Perhaps these values were locked in a cached state somehow?

huh, strange! glad it works now at least